Hi everyone,
I’ve just released v4.12.2, a small update that fixes a bug for docker-compose users — the container ID is now correctly retrieved, which allows using integrations that launch containers with docker-compose, like the Zigbee2mqtt integration, for example!
This fix is the first contribution (#1648) from a Spanish user, whom we thank for their first contribution 
The full CHANGELOG is available here .
How to update?
If you installed Gladys with the official Raspberry Pi OS image, your instances will update automatically in the coming hours. This can take up to 24h, don’t panic.
If you installed Gladys with Docker, make sure you are using Watchtower (See the documentation )
3 Likes
Great, I had actually encountered the same bug at the same time as him. Thanks for the fix!
1 Like
hello @pierre-gilles ,
quick question, could this bug be the cause of my Node-RED container restarting every 3 hours for the past week or two?
since installing Gladys 4.12.2 this morning, the Node-RED container seems to be working correctly again?
I don’t really see much of a connection between the two, so no, I don’t think so.
It’s probably a coincidence, or the fact that updating Gladys and restarting the container freed something (RAM?) that allowed Node-RED to restart
Without more info about the cause of the crash on the Node-RED side, it’s hard to say 
hello it’s not really a crash,
but for about 2 weeks (and from memory an update of the eclipse-mosquitto container, MQTT) I had the Node-RED container that was running but restarted every 3 hours!
I didn’t worry too much about it because it restarted by itself and the loss of communication via MQTT with Gladys for my weather data was only 3-4 minutes