Hi i think ive got the same issue with the build in motion light automation,
Home Assistant 2022.10.5
Supervisor 2022.10.1
I’m using frigate + zigbee aqara lamp. My supervised HA updates by itself to latest version.
It used to work before this.
Turning lamp manually works, so not zigbee issue
The automation only works for turning on after off. But not the other way around.
Frigate correctly display on/off state, so not frigate issue.
Is there any workaround or fix yet?
Hi, was there a fix for this? I’m having exactly the same issue with turning off hue lights from an automation (in my case, trigger from a smart light switch).
I’ve tried turning on the lights individually (no brightness settings), turning on all lights via a scene-but no matter what, turning them off results in some staying on (different ones each time).
Also the hue hub/app thinks they’re off and I have to toggle the lights in the hue app to turn them off.
@sgjonathan and @mcoughlin22
Is this the issue you’re having? This test was done with 3A Nue smart lights that claim to work in place of Philips Hue lights. I haven’t tested other lights that claim to work as Hue lights but I imagine the last thing I mentioned about the Fade to Off command being a problem for a lot of clones.
Was this issue ever solved or do you still have issues? I have a very similar issue that I cannot switch off lamps, even if HA reports them as off. It looks like it involves IKEA colortemp tunable bulbs together with my deconz conbee stick. See here: deCONZ - Official thread - #3467 by Robban and deCONZ - Official thread - #3470 by phsdv (same thread)
I first noticed this early 2023, bit it could have been there before. It is still an issue for me.
I had a very similar issue, though in my case it was applying specific light settings (brightness, color temp, etc). My hue lights were showing that they were in the new state both in HA and my Hue app, but the lights themselves were still in the old settings. I could only solve this by turning the lights off and on again. Similarly, this would only happen in automations, not when I updated brightness, etc. in HA. I went to trouble of replacing my SkyConnect with a Sonoff dongle and migrating from ZHA to zigbee2mqtt to try and fix this, but to no avail.
The problem ended up being that I had transition: 5000 applied because I thought it was in milliseconds, not seconds. So the lights were eagerly showing their new state, even though they still had an hour and a half left before they’d truly get there.
I don’t see a crazy long transition in OP’s config, but for others looking at this thread, check transition just in case.