I have two Zigbee LED light strips that, about 80% of the time will turn off in response to a “turn on” command. This happens when they are turned on by an automation, or when they are turned on from the device page. Restarting home assistant will fix the problem for a day or two, but it eventually comes back.
If I immediately turn them back on, they’ll always stay on, but after staying off for some period of time the issue will occur again.
How exactly are you turning it on? Turned off triggered by action Light: Turn on can only be caused by either an action call from the dev tools or by physically tapping an icon on the HA dashboard. You can tell that because it knows that “Alex” performed the action.
Are you maybe double tapping the icon? I also find it strange that it’s switching the light off with a Turn on action, almost like it’s receiving 2 turn on commands.
You’ll need to answer the above questions if you want to get to the bottom of this. Ideally if you’re using a dashboard card, show us its config in yaml (hit the pencil icon in HA dashboard > click edit on the card > “Show Code Editor” and paste it here)
I’m turning it on from the entity page, by pressing the power button seen in the attached screenshot. The behavior occurs whether the light is turned on from the device entry, from a card, or via an automation.
In this case though, there’s no YAML to share since the “light turn on” action isn’t occuring via any custom YAML. I’m just toggling it on in the device page.
The big problem for me is that there are no log entries for the extra action at all.
If HA had issued the action then there should be a log entry stating that.
If HA did not issue the action, then there should be an entry for the detected state change instead, but that is missing too.
This means HA did not issue the action and the device does not even report the state change.
No idea why there are two turn on actions, but there are still no turn off action and no toggle action.
There is however a turned off state change, which do not come from HA and I see now that the became unavailable state change is at the same time too. That last part was hidden by the picture bar for picture elements.
This still suggest an external action outside the HA ecosystem or a faulty device.