Even after Instant On to disable the 500ms multi-tap hysteresis and also setting the Switch Delay Time (parameter 13) to zero, there is still a delay of several hundred milliseconds before the switch action gets invoked.
To compare, I have a Wifi switch of an another brand right next to the White series, and a HomeKit automation set to turn a smart bulb on or off whenever that switch changes state. The smart bulb turns on or off nearly immediately when reacting to the wifi switch state change.
Setting an action to run to turn the smart bulb on or off from any of the White series config button, paddle up, or paddle down single taps (again, with Instant On enabled) running the action from the Inovelli is delayed by probably ~400ms. It’s equally slow if instead of using a button action I set an automation to run when the White switch turns on or off.
I was hoping to use the White switch with a smart bulb in smart bulb mode, but will just return it if it’s really that slow to react. If I tell HomeKit to turn on the (non-smart) bulb wired to the White switch, that does run near immediately, so the delays seem to be asymmetric: White switch->HomePod is slow, HomePod->White Switch is fast (and Wifi swich->HomePod is fast, HomePod->Wifi switch is fast).
Has anybody else found HomeKit actions to be delayed like this, and maybe a remedy?
Just adding that I’ve noticed this as well. The instant-on/delay options only seem to apply only to local power control and not to the multi-tap scene controls.
Either that or maybe it’s just that sending a Matter signal from the switch is much slower than receving a signal from the hub? I’m not sure how to debug when the signal is sent from the switch vs. when the hub gets it.
This does seem to be an issue with the switch; most likely is a firmware defect given the performance for inbound Matter messages doesn’t suffer like outbound ones do.
Hopefully somebody at Inovelli will see this and look into the issue; their support have been trying blame the latency on “the cloud” which isn’t involved here at all:
Lance
• 2d ago
Thanks for reaching out. The white switches run through the cloud and require automations be used and this may be part of the lag.
I pointed out that there is no cloud here, but they’re not hearing it…
Lance
• 7h ago
I understood it that you had automations created through Home Kit, if this is the case it does go through Apples Servers.
That simply isn’t how HomeKit works. There are no “Apple Servers” – the entire ecosystem is local by design and automations continue to work without any internet connectivity at all. That’s a somewhat baffling disconnect coming from Inovelli here, since HomeKit is one of the most common Matter-enabled ecosystems with all recent HomePods and the like having built-in transceivers.