Note that my current system is:
- Use my phone (wifi) to hit an actiontiles button.
- This flicks a virtual switch
- Webcore piston triggered by any change in the virtual switch, which then…
- …sends an autoremote message to the old s6 handset, which is…
- …intercepted by tasker, which then uses the anymote plugin to send the appropriate IR signal.
All in all, this takes 2-3 seconds, which is way faster than i’d expect. Note also that the delay is substantially increased if I use a virtual push button switch (cloud based) as opposed to the (local) standard virtual switch. Does sound a little long-winded, but it works and it’s surprisingly fast enough.
out of curiosity, I tried cutting out the virtual switch altogether, replacing the actiontiles button with a URL link directly to webcore. Now we’re looking at 1-2 secs. I’m sure this could be even faster if I was using 5G wifi instead, or if I could add an IR blaster to a hardwired android box.
Righto… the switchbot. Couple of q’s. =)
In practice, are the delays too great to make it ‘comfortable’ to use as a replacement real remote? I don’t want to hit ‘vol up’ and need to wait 6-10 secs for an actual response. See above.
My current system is solid, but it’s annoying to set up. Feels massively over-engineered. Also I’m finding it difficult to find exact matches for certain functions of my complicated home theatre using the amymote suggested remotes. The switchbot mentions a learning mode - can I use this to duplicate ANY button press from my existing remote by point and shoot?