Hi there,
I’m running HA 0.180.9 in a Docker on Synology.
As you can see in the screenshot, the log files show different timezones.
The correct time is in the log file, the container is wrong and two hours behind.
I’ve tried many docker starts like these:
sudo docker run -id --name=home-assistant --restart=always -v /etc/TZ:/etc/timezone:ro -p 8123:8123 -e “TZ=Europe/Berlin” --net=host -v /volume1/docker/home-assistant:/config homeassistant/home-assistant:latest
sudo docker run -id --name=home-assistant --restart=always -v /etc/timezone:/etc/timezone:ro -p 8123:8123 -e “TZ=Europe/Berlin” --net=host -v /volume1/docker/home-assistant:/config homeassistant/home-assistant:latest
docker: Error response from daemon: Bind mount failed: ‘/etc/timezone’ does not exists.
All these starts have no effect. Still wrong. You could say it doesn’t matter here but the main problem is, that the data in the database is wrong, too.
I’m using MariaDB on Synology, but not I docker, I use the package. The Timezone in MariaDB is set to “System”.
Whenever I query for some data from HomeAssistant.states ´, I have to add the correct amount of hours compared to UTC-Time.
Really annoying.
Automations or trigger DO have the right time.
Any idea ?
Greetings,
Oliver