From c6d4929a53869d3bd71ffb3e9a7a52c25c069c5f Mon Sep 17 00:00:00 2001
From: Edward Firmo <94725493+edwardtfn@users.noreply.github.com>
Date: Mon, 8 Apr 2024 16:01:47 +0200
Subject: [PATCH] Make timezone customization obsolete

Helps with #2024
---
 docs/customization.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/customization.md b/docs/customization.md
index 8b308af..e663f7c 100644
--- a/docs/customization.md
+++ b/docs/customization.md
@@ -276,7 +276,6 @@ ESPHome takes it's time from Home Assistant, however you can configure it to use
 time:
   - id: !extend time_provider
     platform: sntp
-    timezone: Europe/Stockholm
     servers:
       - !secret mysntpserver
       - 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
 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.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.
 You can easily force a timezone by adding this to your ESPHome settings: