Closed Pabsilon closed 9 months ago
I've been investigating further and I think my issue is not related to entity controller, as using plain 'turn_on' then 'turn_off' calls on the controlled device results in the same problem.
In case someone runs into something similar, it was due to have transition in my calls. For some reason, the hue bulbs in zigbee2mqtt didn't like it.
Hi! First of all, great job with the integration, it works wonderfully well. I've encountered an issue when using scripts.
Description
I have an entity controller for motion controlled lights in my kitchen. These lights are hue, and as such, are dimmable. In general, I use a single script for toggling the lights (omitting some logic, in its base, it's 'if lights are on turn off, else turn on' . This script is used as trigger_on_activate on entity controller, and it's used when pressing the kitchen wall switch. But, for trigger_on_deactivate, I have a different script that adds a longer transition time to turn off the light (Just a turn on service call with brightness 0 and transition 15) so whoever is in the kitchen has a heads up that notion lights are turning off.
My issue is that whenever lights are turned on by EC, and I turn them off manually with the wall switch, the trigger_on_deactivate script is also called, usually resulting in the lights not turning off (they actually dim halfway through, and I think that's an issue for another place)
So, basically, if EC is active and I call the EC trigger_on_activate script again (which is a toggle and changes the observable entity's state), both my script AND the trigger_on_deactivate script are run more or less at the some time.
Configuration
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
This is how the component should work:
Actual Behaviour
This is what actually happened:
Logs
I will provide full logs tomorrow, as I can't restart my main instance at the moment.
Version