mchill

I tested it out, it works for me now. Thanks for the fix!

~crickets~ C'mon guys, this is a pretty major bug in your software. I'm not asking for a miraculous next day fix, but acknowledging it would be nice. (A public-facing issue tracker would be even cooler.) For what it's worth, I've worked around the delay problem, but it's pretty involved. I ended up: Pairing a Flirc USB receiver with a Raspberry Pi Writing a script to capture USB input and publish messages to an MQTT broker Creating Home Assistant automations with MQTT triggers that power on/off devices, change inputs, etc. So a single keycode from the Skip remote can trigger an automation that performs any number of actions. The nice part is that this allows for much more powerful and complex routines. For example, rather than a dumb 5 second delay after powering on my TV, I can wait for the TV state to change in Home Assistant. If you happen to have a Shield TV, you could skip the RPi and MQTT, and fire webhooks from the Button Mapper app instead. Although you'd still need to run Home Assistant somewhere. Also, if you have any IR-only media devices not connected to your network, you'd need an additional device like the Broadlink RM4 to control them with Home Assistant. My intention when buying this remote was to pair it with Home Assistant, so I was willing to deal with the workaround. But I understand it's a lot for the general audience to handle.

I just received my remote and noticed the same behavior. If I click "Test Actions" in the app, the macro runs correctly with the set delays. But after unplugging and pressing the button on the remote, each item in the macro is run without any noticeable delay. Probably related, changing the delay amount on any action doesn't enable the sync button. Changing anything else, including the repeat slider, does enable the sync button. I dug through the forum and saw issues with delay in the past, but it looks like they were fixed. Maybe this is a regression of an old bug.