Make timezone customization obsolete

Helps with #2024
This commit is contained in:
Edward Firmo
2024-04-08 16:01:47 +02:00
parent ca7dcd92a9
commit c6d4929a53

View File

@@ -276,7 +276,6 @@ ESPHome takes it's time from Home Assistant, however you can configure it to use
time: time:
- id: !extend time_provider - id: !extend time_provider
platform: sntp platform: sntp
timezone: Europe/Stockholm
servers: servers:
- !secret mysntpserver - !secret mysntpserver
- europe.pool.ntp.org - europe.pool.ntp.org
@@ -343,6 +342,7 @@ You can find more ideas around this on [#955](https://github.com/Blackymas/NSPan
### Enforce time zone ### Enforce time zone
Until v3.4 (including), the time was coming from Home Assistant with it's timezone, so the Blueprint was sending the info with no transformation, to the panel. Until v3.4 (including), the time was coming from Home Assistant with it's timezone, so the Blueprint was sending the info with no transformation, to the panel.
From v4.0, the time reference still coming from HA (or optionally from a time server), but is calculated in ESPHome, which will try to detect the timezone from the server. From v4.0, the time reference still coming from HA (or optionally from a time server), but is calculated in ESPHome, which will try to detect the timezone from the server.
From v4.3.3 or later, the time still calculated on ESPHome side, however, you can select the timezone on the Blueprint, making this customization obsolete.
If your system is not showing the time in the correct timezone, it's probabily ESPHome not succeeding on finding your time zone. If your system is not showing the time in the correct timezone, it's probabily ESPHome not succeeding on finding your time zone.
You can easily force a timezone by adding this to your ESPHome settings: You can easily force a timezone by adding this to your ESPHome settings: