Jump to content
Flirc Forums

jason

Administrators
  • Posts

    3,698
  • Joined

  • Last visited

  • Days Won

    223

Everything posted by jason

  1. Critical - Learning requires both remotes to be facing each other and about 1 inch apart. Further detail here along with video: https://forum.flirc.tv/index.php?/topic/13442-skipapp-099556989-with-ir-learning/ Changelog New Firmware - Many bug fixes, should replay now GUI - Many bug fixes GUI - Admin Panel - New IR Learning Tab for Debug (see below) GUI - Windows Grid Size Fix GUI - Fix Learned Automapping GUI - Fix some hover statuses GUI - Admin Panel - Remote Log Tab Improvement This is helpful if we start debugging protocols. The top window is the raw capture, and the GUI assembles the timing from this array into the easily to read timing seen below it. This will also improve over time. This format is not useful if you want to create your own JSON file, but we'll get to that eventually. I'm mainly interested in finding out if you are now able to learn and reply codes. I still need to add support for several protocols. Please, let me know how it goes. You need to be using the included firmware in order to do any recording. The version embedded is v4.13.3 You should be prompted for the firmware upgrade. If you are not prompted, please don't post here, and PM me. We need to do some hardware revision compatibility testing first. I have not fully tested for power consumption changes on the remote. Please use the latest versions here
  2. I added a bunch of roku buttons some time ago. I could not find one specific for plex though.
  3. There is alpha software posted in the beta forums. https://forum.flirc.tv/index.php?/forum/102-beta-feedback/ Before playing with it, wait until tomorrow. I'll start a new thread with new beta software to try. The software / firmware has many bugs that we have since fixed.
  4. @Oliver Kötter @shining Linux issues you are seeing are universal, this alpha has nothing to do with linux. Start a new thread, and we can work on stuff there. Sorry if the other links are not working. Gonna fix tomorrow. @shining Appreciate you trying to record and replay, that's really the only thing I care about. Found a ton of bugs, both firmware and the GUI, going to post a new version tomorrow to play with. I'll lock this one and start a new one when it's ready.
  5. Unplug the batteries. And plug them in again while it’s disconnected. I’m looking into this.
  6. @shining @Uzi2 @asyba and everyone. Would like to hear some feedback on how things are going. I know there are some things that need to be fixed and improved. I want to make sure that the devices can be learned, and codes are transmitted correctly, this is the most important part. Maybe we need the ability to test during the wizard until things are more stable. I see on the server things have been hit or miss, although I'm not sure if it's because we need to make it more clear that the remotes need to face each other.
  7. This is a really good point and something I need to solve. I'm not quite sure how to do this, since on the other end, it'll be frustrating for other half of people. For example, if I got a new TV, I go back to the wizard and delete my old one and put the new one, I'd want it to remap all the buttons. We can prompt users? Or leave the ones that were manually mapped. I understand there are also an entirely different set of folks who just want to try a different device, so they swap one out and then all their custom mappings are messed up.
  8. Edited above, remember to make sure both remotes are facing eachother and about an inch apart. I see some codes, it's critical one is facing the other.
  9. Really good question, we're going to build something like that but we are limiting it to the basics right now.
  10. Try my other app. Needs some TLC. But it works. App Pad
  11. Newer Version Here Locking this thread now. **EDIT ** - Critical - Learning requires both remotes to be facing each other and about 1 inch apart. This was a significant amount of work, with a lot more to do. But now we need some testing and ask for patience while we work through what will be a fair number of bugs. The learning process depends on an external server. I did this for a few reasons. All my IR decoding libraries are in C, and while it's fairly easy to interface with React Native, I did not want to keep posting releases for every small change. I also don't want to ask everyone for logs. So I took my C library and created a small Rust server that accepts the raw timing from the remote and returns the codes the remote uses. I even built a frontend that visualizes the timing and results: http://ir.flirc.io I plan on making the user interface more useful over time. Here is how it works: CleanShot 2023-12-15 at 22.54.49.mp4 You need to be using the included firmware in order to do any recording. The version embedded is v4.13.2 You should be prompted for the firmware upgrade. If you are not prompted, please don't post here, and PM me. We need to do some hardware revision compatibility testing first. I have not fully tested for power consumption changes on the remote. Please use the latest versions here
  12. Excellent. I'll give it a go, thank you.
  13. interesting, any chance you can replicate the configuration for me and send that over?
  14. Thank you for this. I got all your messages but I have not had a chance to sit down this week. But this is helpful. Tells me buttons are recognized, but it’s stuck somewhere and ignoring them or it thinks it’s in a different mode. I’m going to add more logging to get to the bottom of it and send that to you shortly. I hope to do it tomorrow.
  15. I'll get these posted this week. Avfabul - Avstar Hdmi Splitter Switch.json
  16. Batteries get disconnected with USB present. I log a reboot on battery low fail. I’m going to add a ton of logging because it must be stuck somewhere, but you can’t remove the batteries or I lose the logs.
  17. Don't use rechargeable batteries, and follow the instructions I outlined. When it seems to be dead. Press and hold a button that is mapped to something. Do another, hook it up to the computer without disconnecting the batteries, and get the remote logs please.
  18. Alright, I'm not doing this anymore. I'm deleting new posts. I have sent a dozen remotes and only got one back. I have no idea if people are just wanting free remotes or what, but now I'm getting mad. I test every remote before I send it out and never came accross one that uses 100mA because that's what it would take to deplete a battery in one day. Every remote has gone to sleep correctly and is under 6uA.
  19. jason

    MECool remote ?

    @Turbine Okay try this Dune - Dune HD1.json
  20. jason

    MECool remote ?

    Yup. I'm out today, will fix it tomorrow or monday. Thanks @Benjamin Metzler for helping jump in.
  21. jason

    TV Source button?

    Sorry. Do you mean you can’t find the button in the device button list?
  22. jason

    MECool remote ?

    Theyll be the same. No need to retest. They are identical with different labels.
  23. jason

    MECool remote ?

    Thank you for doing that, I just worry this is going to be a brutal test. I removed the entries already in the previous config since we already know their assignment. There is no quick way to test these other than assigning them in the gui. Mecool - Mecool_KM6.json
  24. jason

    MECool remote ?

    I tried very hard to finish yesterday but couldn't find anything useful to help guide me on making more codes. I have to put together a tool and will have something end of next week. I normally work on the weekends, but my family needs some time with me.
  25. Please. I’m betting it’s not a battery issue and a firmware issue. I’ve been able to see in one of our rooms a state where it is stuck. Button presses don’t do anything and it looks dead. Hooking up to the computer I see that it never turned off and collected logs. I brought it to work and was going to do some electrical analysis and by the time I wanted to try again, it unstuck.
×
×
  • Create New...