"Internal" time wrong

check out this

1 Like

Hello Everybody!
Looks like I have a similar issue with time settings. I think you are all running in circles not finding the correct issue.
I say this because:
I am running home assistant supervised in an esxi VM. Installed using 3.13 vmdk image.
Since I installed it a few days ago, I have had a lot of problems, by losing access to the server. I saw it was losing its ip address.
So after reading a lot of topics, I found that the timestamps in supervisor logs are of by 3 hours.
This time delay will F*** up the dhcp renewal from my router (pfsense vm) and after the minimum lease time of 2 hours, the home assistant machine loses its IP and I have to power cycle it. Simple reset will not solve the issue.

Now, I would like to ask you if there is any way to correct this issue. It is driving me crazy, and until now I did not manage to find a way to set the supervisor time/timezone.

Thank you,
And here is my original topic on this forum: Hassio on esxi losing IP address - HA supervised
And here is the issue on Github: https://github.com/home-assistant/operating-system/issues/684

1 Like

Similar problem here??

{{ now() }}
{{ now().astimezone() }}
{{ utcnow().astimezone() }}
{{ now().now() }}
{{ now().today() }}
{{ now().utcnow() }}
{{ utcnow() }}
{{ now().tzinfo }}
{{ now().astimezone().tzinfo }}
{{ utcnow().tzinfo }}

2022-11-12 15:12:40.501943+00:00
2022-11-12 09:12:40.501943-06:00
2022-11-12 09:12:40.501943-06:00
2022-11-12 09:12:40.501943
2022-11-12 09:12:40.502947
2022-11-12 15:12:40.502946
2022-11-12 15:12:40.502946+00:00
UTC
Central Standard Time
UTC

System Health

Version core-2022.2.3
Installation Type Unknown
Development false
Supervisor false
Docker false
Virtual Environment false
Python Version 3.9.10
Operating System Family Windows
Operating System Version 8.1
CPU Architecture AMD64
Timezone America/Chicago

This automation is going off at 8AM UTC, not 8AM CDT:

  • id: ‘1651526240883’
    alias: Time - Fountain On
    description: Turn on the fountain
    trigger:
    • platform: time
      at: 08:00:00
      condition: []
      action:
    • type: turn_on
      device_id: e96adb89d8978094879aca474a5f009a
      entity_id: switch.on_off_outlet_45_c4_8f_bottom
      domain: switch
      mode: single

seems like something isn’t correct?