I just paired a Nous E6 sensor that displays the temperature, humidity, and time (time is important because the sensor is in the bathroom and serves as a reference for my daughters…)
I successfully retrieve the data (temperature and humidity) in Gladys.
But the time displayed on the sensor is off by 2 hours (it says 4 PM when it’s actually 6 PM, for example)
How can I fix this issue?
I assume the sensor gets the time from Gladys.
If someone could help me, that would be really nice.
In the zigbee2mqtt integration in the configuration tab, there is a link that leads to the zigbee2mqtt interface. If you click on it, do you have access?
You should have a direct link in the Devices tab of the zigbee2mqtt integration, under your Nous E6.
There you will switch to the zigbee2mqtt interface and you will be able to see the features that exist in “Exposition” (if I am not mistaken).
getTimezoneOffset() = timezone of the Node process in the zigbee2mqtt container. Nothing else.
server/services/zigbee2mqtt/docker/gladys-z2m-zigbee2mqtt-container.json has no Env key, so no TZ. And the only bind is the data folder (installZ2mContainer.js:24): neither /etc/localtime nor /etc/timezone from the host are mounted. The koenkk/zigbee2mqtt (Alpine) image therefore starts in UTC.
Result: getTimezoneOffset() returns 0 → localTime === utcTime → the screen displays the time in UTC. In September (CEST = UTC+2) this gives exactly 16:00 instead of 18:00. In winter there will be a 1-hour difference — a good confirmation test.