System time incorrect

Hello,
When I go to hass.io/system and then check the ‘system log’ the time is -2 hours off. Because of that my automations too are 2 hours off.

I run hass.io on Ubuntu. The host’s systemtime is correct.
Weird thing is that when I go to ‘developer options’/info, it does show the correct timezone and time.
I have set up my configuration.yaml time settings as follows:

homeassistant:
  name: Home
  elevation: 0
  unit_system: metric
  time_zone: Europe/Amsterdam

How do I correct hass.io’s time by +2?

I’ve read and tried the following, without succes:

rebooted host system entirely as well, no change

1 Like

my system log doesn’t account for daylight saving hour so is 1 hour out but all other instances of time are correct so my automations etc all work fine.

Have you got the time zone set correctly for your Ubuntu installation, to check if you have the correct time zone set, at the command prompt type:

datetimectl

the result should look somethig like this:

 timedatectl
               Local time: Thu 2019-04-11 15:15:42 PDT
           Universal time: Thu 2019-04-11 22:15:42 UTC
                 RTC time: Thu 2019-04-11 22:15:42
                Time zone: America/Vancouver (PDT, -0700)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no

If you don’t have the right time zone set use the following commands. to unlink the present time zone enter:

sudo unlink /etc/localtime

next type:

sudo ln -s /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime

Then type:

datetimectl

to check if the changes have been made correctly

the results are correct, so no need to change.
still, hass.io reads -2h off

                        Local time: Fri 2019-04-12 18:57:36 CEST
                    Universal time: Fri 2019-04-12 16:57:36 UTC
                          RTC time: Fri 2019-04-12 16:57:36
                         Time zone: Europe/Amsterdam (CEST, +0200)
         System clock synchronized: yes
  systemd-timesyncd.service active: yes
                    RTC in local TZ: no

I have the same problem with the system log and this also affects the data in Grafana (so probably also InfluxDB). The timezone is set correct.

However, my sunrise/sunset automatons do work correctly.

Correct, I should’ve specified my first post: just automations where I specified a time are 2 hours off. The ones based on sun events are fine

Same issue still in hassio 195 with HomeAssistant 0.104.0.
The hassio system log is on UTC, while all other logs are on the correct time.

homeassistant:
  time_zone: Europe/Berlin
timedatectl
               Local time: Thu 2020-01-16 11:50:27 CET
           Universal time: Thu 2020-01-16 10:50:27 UTC
                 RTC time: n/a
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
1 Like

Same here… what to do to solve? change UTC?

1 Like

Same here. It also gives UTC date on Node-Red.

2 Likes

Same here. Time zone setup to Europe/Paris but I have a 1 hour offset on automation (DST?)

My automation uses a sensor.time which send back the right time but the automation start 1 hour later than target

1 Like

Same problem for me.

Have you found a solution?

1 Like

Same here, anybody found something please ?

1 Like

Same here, anybody got the solution?

Same here! Any ideas?

System Time is UTC and it should be correct for wherever it is you are. The system syncs with NTP servers at boot.

If your HA logs are the correct time for your timezone, then you should be fine.

If all else fails (a reboot does not resolve it), then there is the chrony add-on which you can use.

2 Likes

@cogneato t is possible to define the the NTP server in the configuration?
Thanks,

Why ? Are you saying that ‘one’ of the time servers is wrong ?

@Mutt no I didn’t say that. I was thinking to use one of the locals NTPs anyway that will not fix the issue because the daylight savings are managed by the clients so ignore the question. Thanks.

Yes, you can configure them the using a USB stick labeled CONFIG, or you could specify a local NTP server in the chrony add-on.

For the first, you would format a USB stick with FAT32/EXT4/NTFS and name it CONFIG. Then you would create a timesyncd.conf file and put it on the USB. Then import it from the UI or reboot the host to have the import done. https://github.com/home-assistant/operating-system/blob/5cae40c39624b51f48c675c02c7a1ad74ba0c206/Documentation/configuration.md You remove the USB stick after the import.

1 Like