Hello,
I don’t know when the problem started, but I noticed that even when I click ‹ Update › for the following devices, they return to the same state:


Do you have the same problem?
I’m using an external Z2M (Zigbee2MQTT) running 2.7.2
Hello,
I don’t know when the problem started, but I noticed that even when I click ‹ Update › for the following devices, they return to the same state:


Do you have the same problem?
I’m using an external Z2M (Zigbee2MQTT) running 2.7.2
Same problem here.
Same problem as well
I can reproduce it as well!
Can someone create a GitHub issue to keep track of the bug? ![]()
Same for me, with the Z2M integrated into Gladys.
It’s done:
@pierre-gilles I was wondering what the consequences are of not updating devices in the Zigbee integration? Since you don’t say in a new release that this bug is fixed, I no longer click the ‹ update › buttons, but I don’t know if that’s the right thing to do or not…
This issue hasn’t been fixed yet, but it has no impact. It’s just a small visual glitch in the interface, with no consequences ![]()