Closed antifuchs closed 1 year ago
Oh wait, it looks like the switch I just tried with on the -dev branch does in fact update immediately when operated locally. I'm going to continue investigating this tomorrow; today I'm too tired to make sense of things.
Confirmed now: The current dev version correctly identifies on/off and dimmer state. I guess I'll be running this for a bit.
What happened?
I run zigbee2mqtt with a network of Inovelli Blue 2-1 switches. They've been behaving pretty well but lately, I am running into a problem: Turning the switch on at the paddle doesn't update the on/off state in zigbee2mqtt, and when dimming at the paddle, the level doesn't update either. A status of "off" in z2m remains off for hours while the lights are on.
When I hit "refresh" next to the relevant "exposes" value, the state immediately gets refreshed to the correct value.
Operating the switches remotely via the zigbee2mqtt dashboard does work, and status is updated properly and immediately.
No matter if I turn it on remotely or locally, I also get power reporting from the switch, which reflects plausible power readings.
Downstream consumers of that state (home-assistant mainly) do not get the correct status, as you would expect.
What did you expect to happen?
I'd expect turning on the switch to reflect in zigbee2mqtt as soon as the switch is turned on at the paddle.
How to reproduce it (minimal and precise)
Zigbee2MQTT version
1.28.2, commit: 360a777
Also tried with the dev branch:
1.28.2-dev commit: 9289a26
Adapter firmware version
20220219
Adapter
zzh!
Debug log