Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,737
  • Joined

  • Last visited

  • Days Won

    229

Everything posted by jason

  1. there are posts inside the case that should touch the pi's pcb's. They should have exposed metal in this area, which is connected to ground, which would ground the case. The pi community didn't do this, it's plays to their inexperience with hardware. the USB connectors from the pi should also be touching the exposed metal on the inside of the case. Perhaps this is not happening. Try getting some sand paper and sanding down the inside of the case that touches the USB. Perhaps some of the metal's paint is blocking conduction. You shocked the case, and that charge found it's way to a component, and the pi shut off due to either that component failing, or an over current protection. Most of the components are able to withstand ESD, however, it's not ideal if this happens a lot. Keep us posted.
  2. What profile are you using on your harmony for flirc? Can you do the same again, but only do it with one of the bottons on the remote? Nothing is strikingly obvious at the moment.
  3. maybe it's sending erroneous commands? Can you manage to hit the file->clear configuration?
  4. Thanks for letting me know. I am using a non public version of hidapi, as there are several bugs that have been addressed in my copy. Do the following; cd /Applications/Flirc.app/Contents/Resources install_name_tool -change /usr/local/lib/libhidapi.0.dylib /Applications/Flirc.app/Contents/Frameworks/libhidapi.0.dylib flirc_util For those without install_name_tool (mac developer plugins), updated flirc_util attached. I'll issue an update shortly. Sorry for the inconvenience. flirc_util
  5. I think working with kodi on a solution is better. LIRC support and documentation is garbage. I'm not in a position to try and solve this. I will probably at some point publish a USB interface descriptor and how data is sent up raw to the host for developers to make plugins and further integrate. But seriously, I created flirc out of my own frustration with LIRC.
  6. Get out of your activity, and select the FireTV device exclusively. If you see the buttons are there, then it's a matter of getting them into your activity. If they aren't there, we've got a problem with the harmony software, I really don't think that's the case. I have a 650 somewhere I can try and test this on.
  7. Kodi is considered a separate device. What you'll want to do is Add another device to your harmony. Manufacturer 'Flirc'. Device 'firetv' That will add all the specific firetv buttons. Kodi has a bunch more buttons, so it's worth it to keep them both. Let me know if that makes sense. See here for step/step instructions: https://flirc.gitbooks.io/flirc-instructions/content/universal-remote-controls/logitech-harmony-remote-controls/firetv.html
  8. On the screen, aren't there buttons for that profile?
  9. This was different than what this posting originally was. Llooks like this was a bug. I'm pushing an update. Should be posted in about 30 minutes. Infuriated about the bug. Im using hidapi, and am actually jumping on to be a maintainer. For some reason, the interface number for the USB device is showing up as -1, should be 0. Want to pull my hair out.
  10. I didn't see any flirc. You guys don't have the libusbk driver installed, do you? Any chance you guys can do a team viewer session?
  11. Can you post a log like the user did. Not to worry. I’ll get it working.
  12. https://flirc.tv/more/flirc-streacom-edition It's made for a streacom case, but will work with anything.. It's a flirc, with an extra cable that goes to the power switch header of the motherboard. Made to be mounted inside a case.
  13. shoot me a message, I'll send you the new model. Not worth the trouble debugging.
  14. No, that's not really possible. Unless you have a special motherboard that allows for this. The only flirc that can do that is the streacom edition.
  15. kodi supports a second function assigned to the same key flirc also supports this feature The two can conflict. Have you specifically recorded a long press with flirc?
  16. Only if the button you are using is recorded as a long press. Otherwise, because Kodi also supports long press, you can try increasing their long press hold time requirement.
  17. Unfortunately no, as it's one of the fundamental pieces of intellectual property that defines the device and it's great sensitivity across environments.
  18. This is doable. It's on my todo list to implement yawor's request this week.
  19. Someone mentioned the same problem and we couldn't figure it out. Finally, they mentioned turning of ADB debugging in settings which fixed it. Ironically, none of flirc functionality should work if ADB debugging is off, which is why I never suspected it. But maybe things are different on the later version of Amazons software. Can you let me know if that helps at all?
  20. so if you try and record buttons, it doesn't work?
  21. Download the latest GUI on the website, you should be prompted that there is an update. Macs are the only reliable machines at notifying of an available update. Let me know if that helps.
  22. Can you elaborate what this means: "It seems to be getting confused and not registering any keys properly... Other remotes that aren't connected to my TV work fine." Make sure you're on the latest firmware. We're on v4.4.2, and that has some fixes for sony remotes.
×
×
  • Create New...