Oh well, it’s reverted, I tested the issue is no longer present, and Gladys v4.2.3 is being built 
It’s also my fault, I should have put this version through the normal testing cycle via the docker dev tag, wait for feedback, then release. I wanted to share the Zigbee2mqtt changes with as many people as possible, my bad 
Edit: it’s live
Thank you for that even if it wasn’t very conclusive haha
hello @cicoub13!
I have a question about Xiaomi products.
I tried with these products:
I have a problem when I try to pair the products with Gladys, it seems not to find them.
Do you have any idea?
I have this key:
Hello 
Both should be managed by Gladys (I have the door opening detector and I confirm 
)
Have you:
Feel free to analyze the logs (from Gladys and the gladys-z2m-zigbee2mqtt container)?
I noticed yesterday that I had no temperature history… For example, my opening detectors also display the temperature and if I ask gladys what the temperature is in the living room, she tells me she hasn’t recorded anything in the last 12 hours? Any ideas @cicoub13?
The service is active and it has found my IKEA bulbs
Yes, every time I want to start a new inclusion, I reactivate it
Yes, I unpaired them from the gateway (I heard ashishatong ) and nothing on the z2m side.
I tried to do it again after removing the battery and it was the same.
Yes, I even tried on :8080 to click on touchlink => scan
Regarding the logs, I have this on :8080
Info Start Touchlink scan
Info Finished Touchlink scan
Info MQTT publish: topic 'zigbee2mqtt/bridge/response/touchlink/scan', payload '{"data":{"found":[]},"status":"ok","transaction":"rt2xv-6"}'
Is proximity necessary? One of my bulbs is in the same stone as two of my sensors and my vibration sensor is next to the antenna x)
Isn’t there a conflict with the Xiaomi gateway? Have you tried unplugging it?
I think TouchLink is only for certain devices
I’ll check that right away!
Oh (gif I feel stupid )
I’m discovering this at the same time
This allows two Zigbee devices not on the same network to communicate with each other
It didn’t change anything 
This is a bug with Gladys, not the service. I invite you to create an issue on GitHub (I think there is a bug in temperature-sensor.command.js), I will complete it with my analysis.
No, but it prevents errors caused by interference from waves.
I invite you to read the Zigbee2Mqtt FAQ here Zigbee2MQTT, specifically this section
Make sure that any other Zigbee networks/hubs are powered down. When you e.g. want to pair an IKEA bulb which was first paired to the IKEA gateway make sure to power down the IKEA gateway. If that doesn’t help also try powering down all devices that are connected to the IKEA hub.
I don’t understand, I want to pair a Xiaomi device and I just tested it with @VonOx, stopping the gateway didn’t change anything ^^’
However, being very close for pairing really helps a lot, I had to re-pair everything at my place (switch to zzh! ) well, total horror, the interview didn’t work, etc. However, being just next to the dongle, no problem.
I have the same d’ongle as Spencer, without the antenna. I have 2 aqara opening sensors, one 5 meters and the other 3 meters from gladys. The pi with the d’ongle is even in a closet and I didn’t need to move them close for the d’ongle to find them 
As long as your device is not associated with the Zigbee network, no log will appear in Gladys or in MQTT.
I give you some advice and links to try to solve your problem:
with a list of devices
with a device map (you can see here that my Philips bulb and my plug act as routers)
The log you need to look for is this one:
I’m still having a problem with my sensors
I’ll start with this one, the vibration sensor is clearly not well identified:
Here are the features detected on Gladys side:
Here’s what I have on z2M side:
For the door sensors, we are missing some interesting information:
On Gladys side
On z2m side
If you need logs, I can provide them
Otherwise, here is my current network:
Thanks again to all of you
How did that happen? Did I forget a step ^^?
Update: After a delete and an update, I have the battery back! However, the issue with the vibration sensor persists ^^
