If you have the SSH Add-on installed you can use it to issue a date command and see what time the operating system reports.
1:04 ahead also.
I need to add that when I did the core OS update, it did not come back up until I forced a reboot.
I just updated to os 7.4. Even after a restart, UTC time is now off by 5 hours.
I think I figured it out. It seems that Ooma blocks NTP connections 
You have it connected directly to the internet?
Because if it’s connected to a router, it’s the router that has the ability to close various ports.
Full disclosure: I don’t own an Ooma Telo and assumed it’s merely a VoIP adapter.
I’m running in docker and am using British Standard Time which is Europe/London both docker and the host are setup correctly but home assistant is showing one hour behind.
Go to Developer tools → Templates and enter
{{ now() }}
{{ utcnow() }}
That’ll confirm if the problem is that the host time is wrong.
Time’s correct in the results
2022-10-23 18:25:08.212735+01:00
2022-10-23 17:25:08.212752+00:00
Forgot to mention that it’s the logs that are an hour off for me and the times on sensor data such as last updated are also an hour behind as if they are all using utc (i can see that being used for the actual backend data values, but on the web interface i’d expect to see it in local timezone when looking at the device info)
The logs are in UTC
I am having the same issue. I just moved my server to a new mini pc as my last one gave up. My system time is correct. Bios time is correct. I am in the UK currently on DST (GMT+1). Time zone on the HA system is correct (GMT+0 London)
Any fixes for this?
HAOS - 10.3
2023.7.2
When system boots up, I can see there is message which says failed to syncronize the network time. See image…
Following reading through a lot of topics on this I attach another screen shot below. This shows sensor.time as unknown?
Could anyone help me with this issue? I have several time bound automations which are all being triggered an hour early. Also the automations on sunset and sun rise also triggers an hour early. Any help to sort this would be highly appreciated.
Everything in your screenshot shows that it’s all in working order. sensor.time is unkonwn because you most likely don’t have that sensor. All the other peices of information show that your TZ is set properly.
So what triggers are off by an hour?
Thank you very much Petro for your reply. Much appreciated.
Some examples of triggers off by an hour -
- Sunset is at around 9:30. But the automations for sunset triggers at 8:30 (eg. light comes on)
- Logs - instances happening now, shows “in 1 hour”. ie instead of the current time of 18:00. It will show 19:00
- Frigate snapshots and videos - Time stamps are 1 hour forward. If it happened at 18:00, it will show as 19:00
I hope this makes sense
I am guessing the {{ now() }} should show the current time? In my case it is actually 1 hour ahead.
{{ utcnow() }} is actually showing my actual current time.
Did you set elevation in general settings? Also, when you set it, did you make sure it’s set in meters not feet?
can you provide an example?
This will always be the case because frigate only uses UTC
If that’s showing 1 hour ahead you did something wrong. How are you running HAOS?
1 Like
This is my issue. As per my first message, I installed my HAOS on a mini pc and has been running fine for 4 months. No issues with time. Unfortunately the machine stopped working.
So, I now got another mini pc (much more powerful). I just removed the SSD from the previous machine and installed into the new one. Changes the boot sequence, enabled UEFI and disabled secure boot. To my surprise HA booted up normally and all worked fine. Only later I noticed that the time was off by 1 hour. I then checked the system time and Bios - They all showing the correct time.
I’d make a backup of everything (using the backup tool in HA). Wipe the harddrive and start with a fresh image of HA and restore the backup.
1 Like
I could do that. Obviously, I would like to try and avoid that. And why do you think it would fix the issue. If we are restoring from the back up, it will be the same as before right?