Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,737
  • Joined

  • Last visited

  • Days Won

    229

Everything posted by jason

  1. It can't be zero, that's impossible. Try zero, and then go to advanced, and go to device log. Here is what we are looking for: :e:6221 0,4915,4792,892,1579,893,1578,889,1582,893,741,918,1548,893,1579,892,1579,893,4374,864,769,888,746,866,767,919,719,888,741,892,741,893,1578,1727,1581,891,771,867,766,863 :e:24 0,4938,4792,837,1657,841,1631,841,1630,810,824,841,1630,863,1631,814,1657,836,4401,841,793,815,823,837,797,837,797,836,798,836,797,841,1657,1674,1631,837,797,841,794,815 The :e:24 stands for 24ms since the last pulse train. The :e:6221 stands for 6,221 seconds since the last pulse train ( button press). You want to get that 24ms up to 75, and you're good. Keep playing with the number, checking the Flirc gui, and keep me posted.
  2. looks better, but now you need to get the interkey delay in the harmony the same as the original. It should be 75ms, where as yours is reading 24ms.
  3. The log file does not match the flirc / kodi profile signals, you sure that's what you recorded in the device log?
  4. when you added the Flirc Kodi remote profile, did you format your device? You should have zero keys recorded. Otherwise, the existing keys will be used.
  5. sorry about that. I do have some general guidance for that remote: https://flirc.gitbooks.io/flirc-instructions/content/universal-remote-controls/inteset-remote-controls.html Very sorry for the frustration. Thanks for being patient.
  6. go to file->device log, enable logging. Click the 'up' button only once as if you want it to move once. Post the results of that file here.
  7. I think you need to go to troubleshooting, 'my device is sending too many signals' something like that. This is fixable, promise.
  8. okay, yawor was correct. I don't have a release for that version. I'll get to that. You can always override it as well with the following: wget https://packagecloud.io/install/repositories/Flirc/repo/script.deb.sh os=ubuntu dist=trusty ./script.deb.sh
  9. okay, I'll figure it out. Thanks for letting me know.
  10. Very strange, keep an eye on it and keep me posted.
  11. I can't make these public. I need to add some kind of identifying information to the binary. I'll PM you a copy.
  12. any chance you can try re-recording one of the keys?
  13. it's possible the upgrade would need you to re-record your keys. Any chance you can go to file->advanced, load embedded firmware. When the bootloader comes up, what version does it read?
  14. Okay, just click download now, install that. When you fire it up, you should get a session ID and password, private message me that information.
  15. I saw your email about the return. It’s just me. Please give me an opportunity to address this. https://www.teamviewer.us/ Basically allows us to share your screen so I can see what’s going on. Let me know. I’m working today.
  16. Can you add the profile-> Manufacturer: Flirc Device: Kodi No pairing needed, it's all built in. Can you give that a shot? Not sure what profile this is, but it looks invalid.
  17. What kind of remote is this? Are you holding your remote too close to flirc during recording?
  18. this definitely looks different. Can you go to File->Device Log. Enable logging. Press and hold a single key for a second. Save that and post that text file?
  19. Did you load this config from the old device? Can you do me a favor. Can you format the device, record another button. When you do it, press and hold the key as you record it.
×
×
  • Create New...