Ace0

Asked the same question a year ago and it's partially answered by: Which I suppose seems reasonable if once stabilized the internet requirement becomes an opt in (to update IR decoders) rather than a requirement. Though I guess what I don't quite understand is how this is any different than Flirc which also decodes IR from remotes (to translate to e.g. keyboard keys) and to my knowledge Flirc App doesn't require an internet connection to work and uses the traditional update hardware firmware and check for app updates model to pull down updated logic. Worst case, since Skip1s App allows modifying the JSON files used I'm assuming that recording IR with something like Flirc or perhaps Skip1s with debug logging enabled would be sufficient to capture IR signals which could be looked up online. E.g. here's the hex for an Insignia remote: IR Codes for Insignia TV Remote NS-RC4NA-14 – Steve Zazeski.

@jason can we get two things? a) A pinned changelog thread. No one has time to read the entire forum to stay abreast of everything. Personally, I'd like to know when firmware key repeats actually work (the app already claims this functionality) b) A (pinned or easily discoverable) page that lists how to force firmware updates. I'd like some confidence that if I flash bad firmware, there's a way to recover without ending up with an actual bricked device. I realize it's challenging with limited resources but I think these would be minbar for customers to comfortably update and collaboratively iterate on versions without risk or too much of their own time investment.

Thanks, so it looks like it still relies on Harmony servers still being active. I've read some things about using HomeAssistant and doing some sort of proxy which intercepts the traffic from the device and re-routes it to a local server, but that seemed like a whole bunch of hassle to setup and maintain.

@firedog I'm interested in this as well. Could you post what instructions you found? What I don't understand is how we would program the Harmony remote to emit specific IR codes once they nix the Harmoney servers since it's all their own login code, rather than 3rd party IDP.

Some bugs I found while setting up the remote: Button repeat works from the SkipApp test button menu, but not when pressing the button on the remote - firmware update needed? Seems like the software is doing the repeat but the firmware doesn't handle it yet Bug where if you use the Management menu to reset remote buttons, the JSON ends up with empty "controls" and "colorModeMapping" arrays. You can then no longer use the mapping section of the wizard (throws an exception). Only way to fix was to recreate everything or to edit the JSON by hand to restore these arrays and reimport the config file For a button action, the help says you can modify the Duration and Delay, but the menu only shows a Repeat slider. Is this a TODO or just a doc issue? Can repro the bug where tab key for naming the Record device model field doesn't actually move to the text box, but it just highlights some parent element so you need to use the mouse here to click in the text box Hit a weird bug after going through IR recording where afterwards in the Button Panel a key was mapped to two buttons - the one it was assigned to and a "+" button. But there's no plus button on the remote. It also showed an unassigned key, but it was actually assigned to a button. Removing this assignment made another key show as unassigned (so now it showed two unassigned keys). Looked like some off by one bug, but I don't have repro steps since I can't reproduce at will, but just noting in case it helps for code review for the recording functionality added v0.9.993.9235 and updated to latest firmware The only thing affecting me is I would like the ability to do key repeats (for use in Apple TV to mimic holding down the menu key to go to the home screen). Rest of this I have workarounds for but just reporting for use in stabilization.

Why are servers required to record IR codes? Shouldn't the app just bundle the information it needs here and cache any updated information it downloads? Part of the value proposition is being not another Harmony debacle: No Cloud Reliance Some companies end up going out of business taking with them your remote. Don't worry, our remotes are designed to outlive our company and will always be designed to work without an active internet connection.

Regarding app platform, I'm not sure if dependencies you're using are ready yet but if so you should probably move from UWP, which has restricted access to APIs (and no available APIs for some areas) to WinAppSDK, which allows calls to both WinRT APIs and the full win32 API surface (in other words it's not sandboxed, and you can declare the integrity level it runs at in your manifest). For react native support for WinAppSDK, see here for their latest status: New vs. Old Architecture · React Native for Windows + macOS. I haven't tried this, no experience with react, but just putting a link out in case it's useful. In the meantime, for access to HID APIs from UWP, see c# - Can I Use Windows Hid API Calls in UWP (HidD_GetPreparsedData)? - Stack Overflow, which uses a workaround of calling into a native component in the msix bundle from the UWP app. Don't have experience with the library recommend though (it's OSS MIT). Not sure if the Logitech/Steam issues are a solved problem at this point, but if not, might be worth considering. Note, for another data point, I'm not able to get the remote to connect on Win11 (no steam, but Logitech keyboard), though in my case I believe it may be a USB power related issue. Computer has USB3 and using an adapter for USB-C. Remote prior to plugging in can light up, but once plugged in, no device manager changes, but then the remote lights do not work, even after unplugging - need to pull the batteries to get back to a working state. Not blocked on that though, I'm using MacOS instead. Feedback for the MacOS app though is that not having scroll bars in the Button Panel is an accessibility issue. 2 finger trackbar scroll on MacBooks is fairly fragile (there's long threads about it, and none of the workarounds worked), so this required plugging in a mouse with a scroll wheel to be able to program the remote. Scroll bars may look worse, but you can likely auto-hide them for a clean UI, with improved accessibility.