Jump to content
Flirc Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


digitalb0y last won the day on January 8 2016

digitalb0y had the most liked content!


About digitalb0y

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

digitalb0y's Achievements


Newbie (1/14)



  1. I can certainly confirm this. I have many remotes in my house and the only IR one that doesn't work with flirc is a cheap Windows media center remote that came with its own receiver. It's not that the flirc doesn't work with the apps, it's that those types of remotes don't behave like standard IR remotes.
  2. Hi JMCSN, My apologies, I didn't have time to test on Friday night. The first thing I can think to try from the GUI is to completely clear your configuration and start over recording buttons (if you haven't tried that already). I remember seeing some discussion of rare cases when a configuration was corrupted and I believe this should blow it away so you can start over recording buttons. If it still doesn't show up, you might look into re-installing the device firmware. I notice you say the device shows up in device manager. Do you see it in there twice? It's possible this fix could be applicable to your situation: https://flirc.zendesk.com/hc/en-us/articles/201160137-Device-Disconnects-When-Pressing-Remote-Button If all that fails perhaps Jason has some other suggestions, but I'd say at that point you might as well use the contact form link from earlier in the thread anyway, since Jason will ultimately be the one responding to you if you're still having trouble, and he can tell you if any other variables can be tested/eliminated before hardware replacement. Feel free to come back here if you have other questions, though. I will do what I can to help when Jason's too busy. Good luck!
  3. Hi JMCSN, Sorry you haven't gotten a timely response here. Jason, the guy who single-handedly runs Flirc, is extremely busy and does all this in his spare time, but I've never seen him fail to make things right with someone. I had a Flirc unit replaced when it was determined that there was a hardware issue, and I've seen others get their issues resolved or faulty hardware replaced as well. Sometimes it can take a while, but you absolutely didn't buy your Flirc for nothing. Regarding what you've tried so far, does the Flirc GUI actually see that the unit is connected when you plug it in? Have you tried resetting the device, or perhaps interacting with it from the command line? I am not in front of my system so I can walk through it with you, but I will be tonight and can maybe give you some better suggestions later for troubleshooting steps you might take while you wait for Jason to respond. If worse comes to worst, and all signs point to hardware failure, check out this page. Specifically, there's a link there to a contact form you can fill out and Jason should get back to you as soon as he can. In the meantime, I'll take a look on my own system and respond here.
  4. Got it. It's a bit frustrating that the remote that's supposed to be the easiest, most advanced and universal remote out there actually makes it harder to do things a very basic multi-device remote will do in this particular case. Thanks for the explanation.
  5. Sorry you are having trouble... I don't have a Raspberry Pi to test, so I don't know how much I can do personally, but does the Flirc GUI and command line utility work on your system? Perhaps knowing whether those are working and it's only the XBMC plugin that's failing, or if other elements are also having trouble might make it easier for Jason to narrow down what's missing on your system that is already present on other Linux systems. The Flirc Add-on has been really reliable on my XBMC box, which is an Ubuntu 12.0.4 system. Also, what version of the Flirc software and firmware are you running? And can you pastebin an XBMC log that includes the Flirc Add-on failure? Do you see a failed script error message in XBMC or does it only refuse to connect to your Flirc and otherwise run without error? Thanks!
  6. I never respond when I see posts about Harmony profiles because I don't have one, but I guess I don't see what's stopping you from mapping any unmapped button on your Harmony to the ESC key using the full keyboard view in the Flirc GUI, or the flirc utility's record function from a command line. Does the Harmony not send IR codes on undefined buttons or something?
  7. The way long presses are treated depends largely on your remote, and a bit on the firmware you're using as well. I can tell you that on my remote, I had no need for the channel buttons when controlling my XBMC box, so I assigned them to PageUp/PageDown so I could quickly navigate large lists in XBMC like your describing. My remote doesn't send long keypress info on some buttons, so this is what has worked best of me.
  8. Good info, thanks! Perhaps there's a reason for me to look into a Harmony someday after all, eh?
  9. Flirc doesn't do press and hold (yet) with any remote, to my knowledge... am I wrong about this, Chris? I gave my father-in-law a direcTV remote and a flirc and it works great, but I don't remember being able to hold to continue scrolling, nor can I using any device profile on my URC RF-20. Using pageup/pagedown and home/end has been the best way I know to get through long lists. I seem to remember Jason saying he was working on this but the nature of IR signals makes it a little tough. If I'm wrong and someone has this working, I'd love to know how!
  10. That happened to me on the first Flirc I used, but programming it from the command line on a Linux system seemed to help (although in the end it did turn out that my first Flirc was faulty). I don't know if you've got a Linux box to test from or woud like to try testing from Windows command prompt, but it may help isolate the problem.
  11. But that's also the default behavior for the comma and period keys. Comma (,) skips back to the previous playlist item and period (.) skips to the next item.
  12. Never used the R50 but I second everything Chris! said. I have a URC RF20 and it does a great job with flirc on my XBMCbuntu box. If you're at all used to a command line and interacting with XBMCbuntu over ssh, I actually prefer to program my flirc from the CLI, but using the GUI on another system is a nice alternative as well. If you run into any trouble just post about it here and I'm sure we'll be able to get you sorted.
  13. I have a nasty habit of responding at work and not clicking send. Anyway, what I tried to answer you yesterday was that I don't think that's the issue. I'm pretty sure Macs understand the Printscreen key when you attach a keyboard that has one. I'll confirm this when I get home and can take the flirc off my linux box and attach it to my Mac. The problem is that the flirc GUI doesn't have a way to record the Printscreen key on Mac, ostensibly because Mac keyboards don't come with one, and I don't know how to program flirc from the CLI on Macs. Then again, I also don't know if greenep48 is using a Mac to begin with. The commands I listed above will work on Windows and Linux, but if he is on a Mac, I don't know what to tell him unless Jason can tell us how to run the equivalent command from a Mac terminal. I'm sure it's possible, but it's not in a default path for commands on my system, nor is it in the Flirc.app folder.
  14. Yeah, this is almost completely true. Again I can only speak for the RF-20, but not every single device code I put into it works as nicely as the one I ultimately stuck with (the AUX 001 code I mention above is generic and has worked better than other choices for several reasons). But yes, the great thing about Flirc is that it *almost* doesn't matter what remote (or in this case, device code) you use. It sees your button presses regardless of the code you choose, and assigns it to a key press. So like you say, just choose a code that doesn't control anything else in your setup and then see how Flirc responds. Also, I think it only fair to note, the issues I have with some profiles appear to be limitations of my remote and have nothing to do with Flirc not detecting or correctly interpreting my button presses. It's entirely possible that with your URC you will see none of the issues I have seen with some of the codes I can choose when I setup my remote, and that it truly won't matter which code you choose.
  15. Yeah, I have a URC remote and it works quite well with flirc. I can (but don't have to) use an Xbox profile on the URC to control my XBMC box. I choose not to though, because I use the Xbox 360 proflie to control my Xbox 360. I don't know how CCP works compared to the way you program a URC RF20, but for what it's worth. on the RF20 I use AUX 001 to control my XBMC box via flirc.
  • Create New...