Skip to content

[sntp]: document change in behaviour for ESP8266 and ESP32 #5276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: next
Choose a base branch
from
+4 −4
Open

[sntp]: document change in behaviour for ESP8266 and ESP32 #5276

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/components/time/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,8 +239,8 @@ to an external hardware real time clock chip.
Components should trigger `on_time_sync` when they update the system clock. However, not all real time components
behave exactly the same. Components could e.g. decide to trigger only when a significant time change has been
observed, others could trigger whenever their time sync mechanism runs - even if that didn't effectively change
the system time. Some (such as SNTP) could even trigger when another real time component is responsible for the
change in time.
the system time. Some (such as SNTP in some cases) could even trigger when another real time component is
responsible for the change in time.

{{< /note >}}

Expand Down
4 changes: 2 additions & 2 deletions content/components/time/sntp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,8 @@ If your are using [Manual IPs](#wifi-manual_ip) make sure to configure a DNS Ser

{{< /note >}}
{{< warning >}}
Due to limitations of the SNTP implementation, this component will trigger `on_time_sync` only once when it detects that the
system clock has been set, even if the update was not done by the SNTP implementation!
Due to limitations of the SNTP implementation, on platforms other than ESP8266 and ESP32 this component will trigger `on_time_sync`
only once when it detects that the system clock has been set, even if the update was not done by the SNTP implementation!
This must be taken into consideration when SNTP is used together with other real time components, where another time source could
update the time before SNTP synchronizes.

Expand Down