Jump to content
Flirc Forums

All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. What is the NEC TV code set you use and is it complete, as in every MX-500 button (including the LCD buttons on both pages) generates a usable IR signal? On my MX-500 I had trouble finding a complete preprogrammed code set. Every one I tried of several from the DVR and other categories seemed to be missing at least one button (commonly, nothing on page 2), and/or produced IR codes that Flirc seemed to learn but did not respond to in actual use (Hours wasted before I realized this). I found that AUX 001 seems complete and am using that with Flirc, but would be good to know of others. But otherwise, I agree about the overall good experience with this remote and Flirc on Android TV. One minor con is that when holding the cursor pad down, letting go doesn't stop the cursor immediately; there's always a slight overrun. Holding the pad down when learning on Flirc v2 didn't help. I wonder if v1's ability to adjust timings would help here. I wish the Flirc firmware were more flexible in terms of combining long press and macros on the same button (and in being able to use record_api with either), and in generating HID and Android keycodes (I've written more on this elsewhere), but overall Flirc does exactly what it claims to do. I am hopeful that @jason will continue to implement new features in firmware. PS - Does your remote backlight work? Mine died years ago on both of mine.
  4. Last week
  5. Can I get a firmware downgrade link please?
  6. So apparently I am confused regarding the available Flric downloads. First off: https://flirc.tv/downloads has the "Latest Release Flirc Setup.exe [v3.22.4]" which downloads as Flirc.exe Then we have this page: https://flirc.tv/support/flirc-usb "Flirc Installer [v3.25.3]" which downloads as Flirc-Setup-3.25.3.exe Which download should I use? And why are both flagged as dangerous and blocked by Chrome? Many thanks!
  7. I would really appreciate if I get a response from the support team I would like to know if I'm the only one that is seeing this issue cuz if I am I am going to return the flirc cuz I'm still under warranty
  8. I'm encountering the same issue. I configured the samsung remote as a Universal Remote for use with a Roku (as suggested by Madiba), but the the directional and enter buttons won't pair. Any tips on other things to try? The logs only show periodic random garbage.
  9. I am trying to download the latest version of the software for Windows and both Firefox and Chrome are saying it is a virus. I have tried it on two separate machines and it is the same on both. Unsure what is going on since I have not had this problem before with downloads from your site.
  10. Excellent, you got it. Thanks for posting the follow-up, and let me know if I can do anything else to help or improve the app.
  11. Ya know, I think I figured this out. the Flirc is not programmable by us. It already has all the keyboard mappings that it supports. All we do is tell Flirc which button on our remote will "press" which key on the keyboad that flirc knows about. I thought this whole time that I was programming the flirc like I do with a learning remote. In case others are confused like me, if you want flirc to press HOME, click on HOME in the Flirc SW and then when it's ready to learn press that key on the remote. This will basically translate your keypress on the remote to a "keyboard" keypress that flirc will send to the device. I can't say that this was explained very well in the documentation or the marketing rah rah on the web site. Thank you for indulging me.
  12. Hello forum I bought a Flirc 2. Gen recently to use it with my OSMC (Kodi) on a Raspberry Pi 3 with the Logitech Harmony One Remote. Set up as described. But only a few buttons are actually working! Main buttons like navigation, play, stop works fine. But not even FF/Rewind or the step Fwd/Rew works as supposed. The "Power off" button just opens a window on which I have to scroll down to select the right comand and press ok again. The Harmony remote seems not to be able to shut down the device on this way in an activity, without a descrete "power off" comand. And there is not even a "Power on" button! So it's not possible to integrate the device in an automated actvitiy! Also missing is the ability to enter the detailed player controls (key "M" on a pc keyboard). I'm a little confused about that behaviour. How can I get to run it properly? Thanks for any help.
  13. I'm kinda getting lost in this, I think I'm working into circles. Can you please help me get back to basics. Do I have the harmony remote setup correctly? >> Media Center PC, Flirc, Kodi ? In the Flirc SW, I choose the kodi controller, does this save the kodi profile to the flirc? or am I missing another step? I would like to follow your advice and record the "space key" to the pause, but I have no idea how. I click on the pause key in the GUI and it wants to me to record. From where? where do I record a space from? Also from your comment about the keyboard controller, do you mean there is a way to tell the kodi controller to use the space bar press in the keyboard controller for the pause key? Or do you mean I should program the harmony to use the keyboard controller? Thanks
  14. You got your wish Being able to directly send Android keycodes is still not possible unless there is another undocumented method, but it is possible to invoke KEYCODE_SEARCH.
  15. The remote control is a Logitech Harmony One+. The problem is that the setup is very unreliable and I don't know if it is the Flirc, the remote control, Debian Buster or a combination. The remote control has worked without problem for several years together with Debian. But when Debian was upgraded from Stretch to Buster the drivers for my IR receiver stopped working. I then bought a Flirc. The problems are several: It sometimes output errors when using flirc_util as I have posted above. It sometimes deletes the recorded keys and I have to do the configuration again. It almost always don't respond to the first press on the remote control. It needs a second press on the same button. I noticed that last time the recorded keys were deleted I have managed to record multiple entries for the enter key. But even before that I had to press twice for the remote command to be recognized by the computer.
  16. What remote control are you using? There are no problems with the log. It’s working as it should. Does the remote respond?
  17. Here is the output from DEBUG=true flirc_util settings. Hope you can get some info out of it. flirc_debug.txt
  18. Mouse support would be great, I miss this most on FLIRC. Should be also, something like Soundgraph iMon had, App Launcher, and option to mapping buttons to programs with own profiles.
  19. I've used the same universal IR remote for years, and continue to use it with my 2017 Nvidia Shield TV via Flirc. The remote does not have a microphone, but it is still possible to use voice search. Mic: All Nvidia remotes and game controllers have microphones. I use a PlayStation 3 Eye USB webcam. It is available for $8 new at Amazon; I bought mine for $2 used from GameStop. Be aware of how Shield prefers Nvidia microphones. Remote: Android keycode 84, KEYCODE_SEARCH, triggers Shield's voice search. Flirc can't send this natively as far as I know, whether through its standard keyboard mapping or the hidden HID Consumer Table codes. Using flirc_util record_macro 128 0 I instead have Flirc trained to send the right Windows key, Android keycode META_RIGHT. The key itself isn't important; choose one that is redundant (the left Windows key does the same thing as the right, and this way I can trigger voice search when using a real keyboard) or unused. Two ways to convert this binding to KEYCODE_SEARCH on Shield: Button Mapper (on Play Store): Advanced | Custom keycode (ver 2) | 84 Keyboard/Button Mapper (on Play Store, but needs sideloading for Shield TV): Choose Action | Key Code | KEYCODE_SEARCH KEYCODE_SEARCH behaves differently depending on context. In voice search-aware apps (Example: YouTube), it searches within the app itself. In the Android TV launcher, and non voice search-aware apps (Example: Prime Video), it activates the general Google Assistant voice search.1 Nothing happens in some apps (Example: Reelgood). Optional: In Button Mapper I have the same key open Assistant when long pressed, to invoke Google Assistant voice search no matter where I am: Actions | Assistant, then More Options | disable Alternate assistant. I describe another method in the above-linked HID Consumer Codes discussion. 1 "Ok Google" does not work with non-Nvidia mics
  20. Flirc has a hidden method for sending HID Consumer (page 12) codes: flirc_util record_api x 102 where x is in decimal flirc_util record_api 2 x where x is in hexadecimal The first method is only documented in @yawor's forum post; the second is not documented anywhere except sort of in one comment by @jseymour. I tried every value for x from 0 to 0x29c (668 decimal), the highest listed in the HID documentation, to to see which ones cause Nvidia Shield TV to do things. Each is listed with the Android KEYCODE the resulting Flirc binding produced in Button Mapper. (The Flirc codes do not match Android keycodes' numbers.) Flirc code | Android keycode -----------|---------------- 48 | POWER1 50 | SLEEP1 52 | SLEEP1 54 | BUTTON_1 64 | MENU 65 | DPAD_CENTER 66 | DPAD_UP 67 | DPAD_DOWN 68 | DPAD_LEFT 69 | DPAD_RIGHT 70 | ESCAPE 71 | NUMPAD_ADD 72 | NUMPAD_SUBTRACT 101 | CAMERA 111 | BRIGHTNESS_UP 112 | BRIGHTNESS_DOWN 132 | ENTER 137 | TV (Live Channels app) 138 | EXPLORER 140 | CALL 154 | DVR (DVR functionality in Live Channels app) 156 | CHANNEL_UP 157 | CHANNEL_DOWN 176 | MEDIA_PLAY 177 | BREAK 178 | MEDIA_RECORD 179 | MEDIA_FAST_FORWARD 180 | MEDIA_REWIND 181 | MEDIA_NEXT 182 | MEDIA_PREVIOUS 183 | MEDIA_STOP 184 | MEDIA_EJECT 205 | MEDIA_PLAY_PAUSE 207 | VOICE_ASSIST1 (general Google Assistant voice search) 226 | VOLUME_MUTE 233 | VOLUME_UP 234 | VOLUME_DOWN 386 | BOOKMARK 387 | MUSIC 394 | ENVELOPE 397 | CONTACTS 398 | CALENDAR 402 | CALCULATOR 406 | EXPLORER 414 | POWER1 418 | APP_SWITCH1(Recents in Button Mapper) 539 | COPY 540 | CUT 541 | PASTE 545 | VOICE_ASSIST1 547 | HOME 548 | BACK 549 | FORWARD 550 | MEDIA_STOP 554 | BOOKMARK 563 | PAGE_UP 564 | PAGE_DOWN 1 Did not produce Android keycodes in Button Mapper. I identified the corresponding keycodes based on what they caused Shield to do. Other Flirc codes may not generate Android keycodes but still do things that I did not notice. I hope @jason will implement the ability to use flirc_util record_api in long press and/or macro, and perhaps other HID tables and/or true Android keycodes. The latter would obviate the need for apps like Button Mapper to convert HID codes to Android counterparts. Until then, what is this list useful for today? Many of the Flirc codes produce bindings already available for use via the GUI or command line utilities. My remote has separate Play and Pause buttons, and I do prefer to bind the former to MEDIA_PLAY (not in GUI or command line utilities) and the latter to MEDIA_PLAY_PAUSE (which is). Otherwise, unused keybindings can be used in Button Mapper, or Keyboard/Button Mapper, to open specified apps or other duties .
  21. OK, it should say what is the company that runs this web site or forum.
  22. I am trying to register in the forum. In the registration it asks what is my company and when I put in the company I worked for, it tells me it is not correct. WHAT GIVES? It doesn't know my company. What is this question doing in a registration?
  23. Earlier
  24. Sorry for reviving this old thread but this bug is not very fun. Also problem is not a QWERTY vs others it is about the keyboard layout and ui userfriendliness. I got a swedish QWERTY layout and mapping volume down in "Kodi" section works but when i press volume down on the remote the volume up key in the gui lights up. So there is no consistency between what remote button you just mapped with what actually lights up after the mapping is done. This plus the additional guessing on the "full keyboards" screen with what key actually will generate the "-" sign to map it right. Surely the GUI must be able to figure out the current keyboardlayout or allow user to pick from afew options or include the numpad section (full keyboard includes numpad...)
  25. Sorry for the delay. The flirc.ini needs to be in the same directrory as the executable. Here is a quick trick you can do: DEBUG=true flirc_util settings
  26. Today when the PC started I got no response whatsoever from any commands from the remote control and when I tried with flirc_util I got: flirc_util unit_test Flirc Okay htpc:~# flirc_util settings 3.25.3 FW Version: v4.9.3 SKU: Flirc 2.0 [dori] Branch: master Config: release Hash: 0xCB185BDE Settings: sleep detection: always enabled noise canceler: always enabled inter-key delay: N/A for current firmware variant: Flirc builtin profiles: NA Memory Info: NA product sku: Flirc 2.0 [dori] Recorded Keys: Index hash IK ID key ----- -------- --- -- ------------ Now the list of recorded keys was empty again.
  27. Any word on the new version? Will we be able to change the inter-character delay again? The old version worked perfectly and I would love to get rid of the double presses. I am using it with lirc and MythTV and, although it works pretty well, I have to be very careful to press quickly and deliberately. It improved when I disabled built in profiles, but still not acceptable.
  1. Load more activity
  • Create New...