Jump to content
Flirc Forums

All Activity

This stream auto-updates     

  1. Last week
  2. This has probably been covered many times before but I have looked and looked for the answer to this but I cannot find it. For quite a while my "Home" button was not working when using my Harmony One remote to control my FireTV. I have finally gotten around to try and fix it. I updated the firmware on the Flirc and download the FireTV device on my Harmony and all of the buttons including "Home" seem to be working except the "Back" button. Whenever I press this button on the Harmony, it seems to perform ""Pause" or "Select". Can someone please help or direct me to a post that covers this? Thanks, Ron
  3. Found a solution. For anyone who is interested: Use "Esc"-Button on full Keyboard für "Exit" and "Backspace" for "Back" (one step back in Menu). But I have a new problem: how to bind "Teletext"?
  4. I purchased my mother a FireTv and I need 2 simple codes which are not on the fireTv profile. All she does is use it to watch cable. The whole FireTv interface is too much for her to learn all at once. The TV is plugged in to hdmi1. I've set the TV up so it always goes directly to the last input it was on. So whenever she turns it on, it will always go to cable unless someone else left it on another input. Right now she has to use 2 remotes. Her "universal" remote for cable and the firetv remote to turn the stupid thing on and off, and to adjust the volume. So I just need 3 codes. The 2 most import are volume up and down. Nice to have would be the following more complex codes: One to turn the tv on and off[I don't care if it is actually off or in "sleep" mode. It just needs to make the screen turn OFF.] Really nice to have would be a macro command to make it switch to the primary hdmi input.
  5. PittsburghRed

    Flirc with Fire TV Gen3 and Ethernet adapter

    I solved the issue. It is indeed to do with having 2 OTG devices. If you want to have a wired ethernet and a flirc you need to use a hub like this: https://www.amazon.com/gp/product/B00LLUEJXW/ref=ppx_yo_dt_b_asin_title_o03__o00_s01?ie=UTF8&psc=1 simply pop in the hub to the OTG cable above and add the flirc and use the ethernet adapter in the hub both work just fine. hope this helps somebody.
  6. PittsburghRed

    reCaptcha

    I concur the my company name thing is plain stupid
  7. Markus

    Wrong FW version in latest Linux x86_64 GUI?

    Hi , have the same problem as @SteLin. I also tried the 64-bit generic tar file without success. The upgrade tool will not install any firmware >= 4.1. It offers me only the already installed version 3.9.0. I'm desperate. Here my settings: flirc_util version 3.20.4 [3.20.4] Firmware Detected Version: v3.9.0 SKU: flirc-se Hash: 0xE31E4C1A Settings: sleep detection: Enabled noise canceler: Disabled inter-key delay: 7 seq. modifiers: Enabled variant: Unknown builtin profiles: Enable Memory Info: keys recorded: 0 keys remaining: 169 memory used: 0% product sku: flirc-se No Keys Found
  8. I picked up a flirc as it was the only USB IR transceiver available online in my area and I wanted to do some experiments with home automation on a handful of devices that use infrared remotes, specifically LED lighting and an air conditioner. I've had great success with the lights and was able to reverse engineer the remote and write scripts to control them with the flirc. The air conditioner is a different story. Air conditioner remotes send huge packets with all of the current settings for the device. Unfortunately, this means the signal sent by my remote is more than 100 edges and flirc stops early and returns an error - I can't see the whole packet to reverse engineer it! Additionally, from my testing, it seems the firmware limits transmitted packets to 100 edges as well, so even if I could figure out the format, I wouldn't be able to send it back to the air conditioner - no bueno. Is there any possibility of being able to receive, or at least print to the debug log, more than 100 edges? Same for improving the transmit command to support longer packets? 100 seems like a very arbitrary choice, rather than something that was specifically called for based on available RAM on the device.
  9. Earlier
  10. PittsburghRed

    Flirc with Fire TV Gen3 and Ethernet adapter

    So here is the use case: 1. Want to control a Fire TV remotely connected to a slingbox. 2. All good so far, setup device on slingbox as Samsung DVD programmed remote and can control Fire TV thru the skinned remote on the slingbox, used the Amazon OTG cable: https://www.amazon.com/gp/product/B07F6K81XM/ref=ppx_yo_dt_b_asin_title_o05__o00_s00?ie=UTF8&psc=1 3. Here is the issue I am using the Amazon Ethernet adapter to use wired ethernet, but this won't work at the moment can only use wi-fi? Do not get option in network settings to use wired connection, tried full reset still no go? Is it because it "sees" the ethernet adapter as an OTG as well and turns that one off? Any help greatly appreciated.
  11. ---> note: I reference a couple of posts from different threads here which are related to my suggestion: KenJs: Any insight as to when this will be available? I bought the device after seeing that it had a transmitter, so its a bit disappointing not to be able to use the transmitter... yawor: unfortunately there's no timeline yet on when that feature will be implemented. There's still no consensus on how the blaster will be accessible to the OS and apps/scripts. http://forum.flirc.tv/index.php?/topic/2386-sending-ir-commands-through-script/&do=findComment&comment=13437 Let me give you an example use case, and explain how I think the IR blaster should be supported : In the FLIRC configurator app, create a new tab or mode switch gadget that enables scripting the IR blaster. When the user flips the switch: FLIRC configurator says: "press the key that you want to script on your primary remote" press the Power key on your primary remote (the one that you use to control your media center PC) FLIRC configurator says: "On any remote, press the key(s) that you want FLIRC to broadcast" press Power button on your TV remote press Power button on your Sound Bar remote select END RECORDING in the FLIRC configurator app Result: When you press the power button on your media center remote, FLIRC will hear this and broadcast the IR codes to turn on the TV and sound bar. Now you only need one remote to control your media center (instead of three.) You dont even need a media center PC if you just plug FLIRC into a USB power supply on (or near) the TV. So FLIRC now appeals to a much wider audience: I could program a FLIRC device and give it to the client. There is no need to buy a big scripting remote that will intimidate them with its cost & complexity. If my clients have a remote control which they know and love, and they do not want to replace it, FLIRC can add the extra functionality which it needs to support power switching on multiple devices. (In most cases, that is all my clients want.) yawor: There's no built-in automation for transmitting. The Flirc's main focus is still on controlling the PC (or other USB Host hardware) to which the Flirc is connected. This means that you can't configure the IR signal to be automatically transmitted by the Flirc itself in response to a different IR signal. http://forum.flirc.tv/index.php?/topic/2786-control-tv-volume-wflirc/&tab=comments#comment-15412 ---> I think it is time to implement this feature, since it would resolve 95% of my clients complaints, and significantly expand the number of applications where FLIRC could be useful. yawor: The IR control is prone to interference if more than one IR transmitter is sending control signals at the same time. http://forum.flirc.tv/index.php?/topic/2786-control-tv-volume-wflirc/&tab=comments#comment-15412 In the scenario which I just described, where the essential TV/Sound Bar/Kodi functions that you would use on a daily basis are all integrated into one remote, interference from other remotes should not be an issue. The IR transmitter in FLIRC could also be programmed to wait about 1/4 or 1/2 second after the last IR reception before broadcasting an IR macro. Also bear in mind that it takes about 5 or 10 seconds for the TV to boot. So the user wont typically be mashing any other keys on his IR remote while he waits for an HDMI signal to appear on the screen. For this reason, I really think that broadcasting IR power commands will work just fine in most applications, and it solves the most common complaint that I get as a home automation consultant. ---> Even if your media center PC is on a shelf below the TV, and the TV cannot see the FLIRC IR broadcast, you could use an IR repeater to expand FLIRC's broadcast coverage. For example: BlastIR 8 Best Remote Extenders You can even buy an IR extender that piggybacks IR signals on the HDMI cable, so both components of the extender can be placed within your media cabinet where they are less likely to be disturbed by family or pets. https://sewelldirect.com/sewell-dual-band-injectir-ir-over-hdmi-for-remote-controls
  12. Flirc V2 with an old RCA remote. I can click a key and map a button fine but it rarely registers. I get this in the log output. Fri Feb 8 2019 00:46:20 <3>ir_finished(63): too many edges :e:1291 0,4114,3862,475,1000,101,2349,497,1975,261,152,98,1919,334,1137,333,2139,526,931,153,136,217,1925,243,136,131,1920,299,136,67,952,67,136,170,1060,458,1976,497,1975,295,136,67,952,33,84,321,978,278,145,57,1125,307,1972,548,940,475,1980,453,1018,479,974,244,135,132,1924,67,135,278,1949,489,982,476,9571,346,325,50,553,67,135,265,291,320,222,197,186,162,290,110,4176,260,1369,67,136,106,1949,329,2139,548,1924,243 Any ideas? EDIT: Tried a newer remote but still RCA. Same issue.
  13. Thanks a lot for this really good solution
  14. The Back Command works as Exit. If I press it, the whole menu closes. I need the correct Back command to go one step back in the menu, not closing it. Can anyone help?
  15. Hi, I had problems with Flirc in the past, but managed to get it to work with this remote. Now Kodi 18 came out and I updated my Libreelec to version 9. Some buttons started to misbehave so after a few years of reliable use, I plugged the Flirc into my Windows 7 PC and tried to reprogram it. The prompted firmware update failed at first, I had to restart the program, it then resumed the upgrade and was, apparently, successful. I continued to try and program the remote, but for some reason, after the first assigned action to any key, every button on the remote now does the same action, no matter where it is placed. When I try to remap another key, it says it is already assigned. Sometimes, seemingly at random, it will let me bind another key. Neither distance to the remote, nor the angle seem to matter. I vaguely remember reading up on previous problems that I should record it at roughly the distance I want to use it, which I did. But I also tried going really, really close, same result. I had relatively fresh batteries in there when I first tried to record it, then put new ones in, nothing changed. The PC is the same (as in, the exact same Windows installation, I merely updated the software), the remote is the same, the Flirc device is the same, only the version of the software and firmware changed. I also tried to clear the configuration. PS: As for the firmware upgrade, it was apparently successful, but I still tried to resolve the issue of having to close and open the program back up to make it succeed, without luck. The support site said to go into device manager and see if the Flirc device is installed properly, it's not, not even listed. I tried to make it search for new hardware, nothing came up. I installed the *.inf files manually (add legacy hardware), it adds the device with the yellow ! on it, nothing changes though. I tried to force a firmware upgrade on an Ubuntu box, went without issue, but the exact same problem occurs when trying to record buttons. PPS: Another remote, which I do not plan on using, seems to work, except for a few keys, though this may be the fault of the remote. Thanks.
  16. I just got a flirc 2. Using it on a PI 3 running Kodi 18. I have successfully mapped buttons that are working in Raspbian Pixel desktop. They also seem to work in Kodi—except ENTER. Nothing I map to ENTER in the FLIRC GUI will send an ENTER command to Kodi correctly. it is crazy because I can see ENTER working fine in a terminal window. I open a command prompt, press my enter key on my remote, FLIRC receives this and lo and behold, I see the command prompt go to a new line. By that account it seems to work. So I launch Kodi and my other nav buttons work, but ENTER does not. Yet, I know Kodi is ready for ENTER because I have a physical keyboard connected for testing and I can press enter on it and it works in Kodi. i have tried disabling the built in profiles in the GUI, I have remapped other remote buttons to enter, tried it on the full keyboard module, I even tried loading the Kodi key mapper add-on to attempt a workaround, but even this does not work. I can map the button press with Kodi key mapper (it registers receiving it) but it does not work when I try to use it. I am stuck. What is going on with the ENTER key in Kodi 18 on the Pi? This is useless if I cannot get ENTER to work. Other than that, it is really cool! <EDIT> Well, I think I may have solved my own problem here. The IR command I was issuing for the ENTER key was getting sent as a 3x repeat. FLIRC must have been recording this in some odd manner and when issuing the ENTER, it would sometimes rapid-fire a string of them, four in a row for example. Changing the IR repeat to 1, re-recording/learning the command seems to have fixed the problem. At least I am able to generate ENTER commands in Kodi now. I have some reconfiguring as a decide how to orient IR blasters etc, but I think my issue was the multiple sends, the recorded result, and further multiplying the effect when re-sending the command once learned (Kodi was often getting a contextual menu "c" command instead of enter, but BASH would show four enters in a row most cases).
  17. Threats to your business’ cyber security are also in a constant state of change and evolution. With each year it seems that one business or another has been brought to its knees by malware, security breaches and data theft. Just as legitimate software developers are constantly at work devising and refining efficient digital solutions, so are their criminal counterparts. Fortunately, for every digital malcontent trying to compromise the networks of legitimate businesses, there’s a cyber security engineer hard at work on pre-empting their malicious attacks. Nevertheless, it is important for business owners to make themselves knowledgeable about the issue of cyber security and the tools at their disposal as we head into a new year.
  18. mecedo

    Numeric keypad

    It's been over a year when I reported this issue. Any chances to fix it in the next few years?
  19. Hello, I've a Fire TV Stick 4K with the latest version of FLIRC (the black one) and a Logitech Harmony Remote. I've added the FLIRC profile for Fire TV to my Harmony Remote and I've loaded the predefined FLIRC Fire TV profile in the FLIRC application. So far so good, all standard buttons work as expected. Now I would like to add a macro (containing several standard Fire TV button presses) to one of the unused keys of my Harmony Remote. Therefore I've added another "dummy" device to my Fire TV activity in the logitech software and I've assigned one of this device's buttons to an unused button of my Harmony Remote. Now I want to assign a sequence of standard Fire TV button presses (UP, DOWN, OK and so on) to the mentioned new button. But I don't know how I can define such a macro. I've already read the chapter in the FLIRC help - but to be honest, I do not understand how I should continue here. Can anyone help me?
  20. ImmortalRat

    Adding support for Nvidia Shield TV

    Just to reiterate, my understanding is that currently there is no way to initiate Voice Search using the current version of flirc_util (3.20.4) and flirc firmware (4.4.2 in Flirc 2.0). There are conflicting reports of what HID commands need to be issued for that to work. One article mentioned Windows key (0x65 on the keyboard), but that didn't work. Earlier in this thread it was mentioned that Shield uses command 0x221 from HID Consumer Table, but as expected, `flirc_util record_api 0 545` did not work as well. If anybody is wondering why you would want to click the Voice Search button on a remote without the mic, the answer is that this is not really a real issue - Shield TV supports generic USB mics, and you can also put the Shield Controller somewhere next to you (it has a mic; I have not confirmed if it's on all the time, but something is draining the battery like crazy). Also, if you are wondering why not just say "Hey Google" (current Shield TV firmware supports this as Experimental/Beta feature), my personal answer is that in this case at least a pair of Home Minis and multiple google pixels all wake up and try to help with the request, and while phones and Home Minis don't duplicate an attempt and record something like "responded on another device", they do not really communicate the same way to the Shield, so typically 2 devices (including Shield) simultaneously responds with drastically different results from different parts of the room and start acting as voice input to each other and then apologizing for not getting what I want to do. :) It's very fun to hear, but impossible to use. @jason Let me know if I am saying something wrong, and also if the functionality becomes possible at some point, would it be possible to make a reply here since this thread comes up in search a lot. It would be greatly appreciated, same all all the great work of your team!
  21. Hi altogether I have a Flirc Generation 1 and I would like to update the firmware and change the mapping. I downloaded the latest version of the UI for macOS: v3.20.4 When the Flirc is connected to the mac the UI gives me: Firmware Version Unsupported You have a newer firmware version than this software supports please check the website for a newer version of this software That sounds weird, the firmware on the Flirc stick is from 2013! How to fix this? Thanks!
  22. Laurence

    Wrong FW version in latest Linux x86_64 GUI?

    For your reference: The working version that I installed was the 64 bit generic tar file. I did not use the apt install script.
  23. SteLin

    Wrong FW version in latest Linux x86_64 GUI?

    Have the same problems Running Flirc GUI version 3.20.4 on Linux 64bit (Mint 19) first generation of Flirc. trying upgrade (File->Advanced->Force FW Upgrade) it says that my current FW version is 3.9.0 and that the latest firmware version is 3.9.00 The log says ERROR. Firmware upgrade required. (fw >= 4.1.0.) How to upgrade to 4.1.0 first ?? flirc_util settings gives this myname@system:~$ flirc_util settings flirc_util version 3.20.4 [3.20.4] Firmware Detected Version: v3.9.0 SKU: flirc Hash: 0xE31E4C1A Settings: sleep detection: Enabled noise canceler: Disabled inter-key delay: 5 seq. modifiers: Disabled [E] lib/libflirc/bootloader/bl_2.0.c fl_ver2_product_type(526): unknown or unsupported variant: 144 variant: Unknown builtin profiles: Enable Memory Info: keys recorded: 0 keys remaining: 169 memory used: 0% product sku: flirc No Keys Found
  24. Hifihedgehog

    Delete me

    Problem resolved. Please delete me.
  25. Gerdei

    Linux Mint + Flirc SE

    Hi everybody! I use Linux Mint and Flirc SE. I sucessed turn off the computer with keyboard combination and command line. Is it possible turn on the computer? When I turn off the HTPC, the blue led is lighting. So it get power. Any ideas?
  26. BevHoward

    No Pause/Break key in GUI yet?

    Brain's beginning to wake up... The page at https://en.wikipedia.org/wiki/Break_key has alternate keystrokes for the break key. fwiw, MSKey.exe which is part of Microsoft's Intellitype software is also a valuable tool for tracking these types of issues. I assume this will allow programming a pause/break key using Flirc's "Full Keyboard" Beverly Howard
  27. Which KVM and model? Beverly Howard
  1. Load more activity
×