Hello,
I don’t know if it’s a bug, but on my setup the Zigbee discovery constantly rediscovers all my devices whether I have enabled the « Hide already added devices » button or not.
Here’s the animated capture.

Thanks and have a great long weekend.
Hello,
I don’t know if it’s a bug, but on my setup the Zigbee discovery constantly rediscovers all my devices whether I have enabled the « Hide already added devices » button or not.
Here’s the animated capture.

Thanks and have a great long weekend.
It’s great that you brought this up! I ran into a problem yesterday.
J’ai appairé un nouvel appareil et me suis rendu compte que j’avais une longue liste d’appareils à « mettre à jour ».
Par curiosité j’ai cliqué sur un des appareils… Ça a tourné en boucle tellement longtemps que j’ai redémarré mon container Gladys ![]()
On my end there are no crashes, but they keep reappearing all the time. It’s a bit annoying.
The devices shown here are devices that have differences between the functionalities present in Gladys, and the functionalities coming from Zigbee2mqtt.
On my system, I only have 2 devices in this list (despite more than 30 Zigbee devices):
The first is rightly there because it’s an old button I no longer use and that is not in Gladys.
The second is an Aqara motion sensor that causes issues because it has a dual functionality « Decimal brightness (Luminosité décimale) », and since the fix it appears forever in this tab; this was reported recently in a bug report ( Zigbee2mqtt: Aqara motion sensor with double feature still showing in discovery like an update is available · Issue #2060 · GladysAssistant/Gladys · GitHub )
Can you tell me which devices appear?
You need to go case by case and see why these devices are not similar between Gladys and Zigbee2mqtt — nothing serious in any case, it doesn’t impair usage ![]()
That, however, is more serious — I’d like you to create a separate topic with all the information so I can see what’s wrong ![]()
3 messages were split into a new topic: Zigbee2mqtt: Gladys instance locks up after a device update
Thank you for your reply.
So there is the Aqara motion sensor and the Legrand pilot-wire outlet
Ok, I’m aware of that bug.
I don’t really see what’s wrong with that one — would you be able to extract the JSON sent by Zigbee2mqtt on MQTT for that device?
I doubt you’ll be able to find that remotely, don’t worry it’s not urgent — enjoy your vacation!
You’ll send it to me when you get back.
Yes, I think I need to be able to access MQTT Explorer
I fixed the bug for the Aqara, it might fix the bug for the other one (not sure):
it will be included in the next Gladys release