diff --git a/content/components/time/_index.md b/content/components/time/_index.md index 0c29b2a083..1699ad7728 100644 --- a/content/components/time/_index.md +++ b/content/components/time/_index.md @@ -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 >}} diff --git a/content/components/time/sntp.md b/content/components/time/sntp.md index d73deafa8e..e643cbdc88 100644 --- a/content/components/time/sntp.md +++ b/content/components/time/sntp.md @@ -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.