Hello,
One of my sensors disappeared, then reappeared, but it lost its name in my Zigbee2MQTT integration.
Here are the two devices affected.
Is there a way to merge them, or do I need to delete one of the two and start over in Gladys?
Thank you
Hi @Prof_Techno,
are both of them reporting data?
Merging them — I’ve never heard of that…
Since they have the same addresses 0x88…, I would say Gladys will recognize them as identical but not being a dev, I don’t know exactly how elements are identified in Gladys, so that’s to be confirmed.
Did the « new » sensor appear in Gladys? If so, then it’s a new sensor and what I said earlier is wrong 
And which version of z2m are you on?
You delete the old one and rename the new one with the old name.
1 Like
Hello,
Thanks for your replies!
@_Will_71: your solution worked, thanks!
@mutmut: I’m on Zigbee2MQTT version [2.4.0]. The old sensor (with the correct name) no longer reported anything to Gladys, while the new one (not yet renamed) works, but I’m not yet certain of its behavior.
Problem: Zigbee sensor disappeared then reappeared without a name
Context:
A Zigbee sensor disappeared from the Zigbee2MQTT integration, then reappeared automatically, but without its original name. Result: two devices appear in the interface — one correctly named but inactive, the other active but unnamed.
Consequences:
- The original sensor no longer reports any data to Gladys.
- The new, unrenamed sensor works but is not yet properly integrated.
Question asked:
Can the two devices be merged, or does everything need to be redone from scratch in Gladys?
Solution adopted
It is not possible to merge the two instances automatically.
The solution is to delete the old sensor (the one that no longer reports data), then rename the sensor in Zigbee2MQTT.
This procedure restores a clean and functional configuration without conflicts from duplicates.
What needs to be understood is why the sensor disappeared and reappeared in zigbee2mqtt. With all the tinkering I’ve been doing for several years, I’ve never been faced with this problem… weird nonetheless
After a few days of reflection — and above all a flash of clarity — I think I have found an explanation:
the Zigbee relay to which the sensor was connected was disabled for 48 hours. It is therefore possible that the disappearance and subsequent reappearance of the sensor, as well as the loss of its name, are linked to that prolonged outage.
In the midst of it I didn’t notice that two other sensors had disappeared because they had been cut off for more than 48 hours.
I find it a shame that they disappear from MQTT
To add an extra piece of information, Gladys identifies the device solely by its name.
In your case, if the old name was « detecteur_ouverture_fenetre_marine »:
If you simply rename the new sensor from « 0x88… » to « detecteur_ouverture_fenetre_marine », it will be reattached to the same existing sensor in Gladys.
In case of a loss on the Zigbee2mqtt side, generally there is nothing to do on the Gladys side; you
1 Like