New to Remote Buddy and Flirc is a new feature for customizable wake support. Since most post processing is done through remote buddy, Flirc passes up the data as quickly as possible for the lowest latency and best experience on the market. The Flirc GUI will not interrupt Remote Buddy’s operation, and allows easy upgrades without the need to quit Remote Buddy. When the remote buddy interface is active, the HID interface is not, so only one interface is supported at a time. It’s been shipping for 9 months, and is already enabled on all existing and new devices. Alongside this interface sits the new remote buddy interface, and it’s been there since version v4.6.0 of the flirc firmware. The pairing interface, and the HID (keyboard/misc) interfaces. The normal ones you are already familiar with. How It Worksįlirc has a number of USB interfaces. Flirc and Remote Buddy work together in concert and with incredible integration and advanced features. But being the creators of each, gave us the unique opportunity to work on features together not found anywhere else. Remote Buddy 2.0 is built on an incredible architecture, with support for a number of receivers, and a number of remotes. It’s not only powerful, extensive, but it’s beautiful. Remote Buddy 2.0 is available for download, and packs a punch of features. While I give him the majority of the credit for the bigger piece of the collaboration, I am nevertheless honored to have worked with him. Felix, the creator of Remote Buddy, and I have been working for over a year on an extensive collaboration. In order to force the Chromebox to suspend, I originally tried to change the default behavior in the Keymap by creating my own /storage/.kody/userdata/keyampas/keymap.It’s with great excitement to finally announce a partnership that was years in the making. Once done, the Chromebox only wakes on that specific IR command, and nothing else. I then trained the Flirc by mapping that IR code to "Wake" in the Kodi controller. I eventually solved this by taking an old IR remote I had from a device I no longer had installed, and creating a new Harmony button I named "Resume" and learning that old remote IR command, and set up the Harmony Flirc/Kodi device with that same code to Power On. So even though there's a Flirc "Wake" event (on the Kodi or Full keyboard controller profiles), I had no corresponding Harmony function/button to map to it. However, there are "Power On" or "Resume" events in the Harmony Flirc/Kodi profile (Just PowerOff). And interestingly the ability to toggle that in the Flirc Advanced menu remained grayed out (not sure why). When I installed the Flirc GUI on a Windows box to program it, it upgraded the firmware on my Flirc, after which it no longer responded to any generic IR event it saw to wake up the Chromebox. so I'm posting here in hopes that it helps others (the other posts I could find on this are rather old), as well as to see if I just missed something obvious.įirstly, just plugging the Flirc in to my Chromebox running LibreElec, and setting it up as a Flirc/Kodi device in MyHarmony initially worked pretty seamlessly for control functions, however there were two issues: 1) Any IR command would resume the Chromebox if suspended, and 2) the PowerOff functionality brought up the Kodi power menu, wherein you had to navigate to a selection. So, I finally got all of this working, but seems like I had to jump through several hoops for what I assume would be somewhat default behavior everyone should want.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |