Does anyone have any idea why a HomeKit automation tied to the doubleclick of the scene button doesn’t seem to work consistently? Like the automation starts to work it seems like, but then fails. Testing the automation from my phone seems to show that there isn’t anything wrong with the automation itself. See video…
Can’t tell from the video - what system is the automation on?
If HomeAssistant, see this guide for setting up an automation: Matter Devices ‐ Setting Up A Basic Automation Using Button Taps · jvmahon/HomeAssistant-Tools Wiki · GitHub
Oops forgot to mention that! It’s HomeKit. Updated.
Honestly the whole thing is a huge head scratcher, and I’m not sure if the issue is something in the switch, HomeKit, or an issue with my home network…
This is the automation in question:
The scene “Red Room” turns on 4 smart bulbs sets their hue to 0 deg, sets a brightness level, and closes the blinds. It also turns on the switch LED and also sets it to hue 0 deg. All the bulbs are Thread. None of the lights controlled are connected to the switch.
The scene “RR Off” turns off the 4 smart bulbs and the switch LED.
When all the lights are off, if I double click the button Red Room will activate (might be a bit slow sometimes and some of the times not all the bulbs may respond, but double clicking again will usually get everything thing to turn on)
However, when everything is on and red, if I double click the button, I will see the switch LED turn off briefly, and then turn on again after a few seconds. You can see this in the video above.
When it gets in this mood, no matter how many times you try the double click won’t work except to briefly turn off the switch led and have it turn on again.
However, 1 time out if 10, the double click will work to turn things off, if it hasn’t failed yet.
Playing back the automation from the HomeKit config screen on my phone works perfectly every time for all the bulbs, for either turning the scene on or off.
UPDATE: The issue doesn’t have to do with double-clicking, rather it has to do with Homekit’s interaction with the switch LED.
I’m still not sure if it’s an innovelli “bug” or a homekit bug, but so that others are aware:
It’s not really possible to use the LED status on the switches as a “dummy switch” during automations that also control the the LED status.
In my case I have a conditional statement in a homekit automation that checks if the LED is on, and Hue is 0, and if so, turn off some lights, including the LED. I was using the LED as a proxy to check if a scene was active. This does not work.
I made a homebridge dummy switch, and otherwise kept the automation logic exactly the same, and it works perfectly.
Given that it works with a virtual dummy switch but not the LED status light on the switch, I suspect the issue is on the inovelli side.
Renamed per request to mods