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.

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

Conversation

kaechele
Copy link

Description:

Clarify new behaviour of SNTP on_time_sync for ESP8266 and ESP32.

Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable):

Checklist:

  • I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
    or

  • I am merging into current because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.

  • Link added in /components/index.rst when creating new documents for new components or cookbook.

New Component Images

If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.

To generate a component image:

  1. Comment on this pull request with the following command, replacing COMPONENT_NAME with your component name in UPPER_CASE format with underscores (e.g., BME280, SHT3X, DALLAS_TEMP):

    @esphomebot generate image COMPONENT_NAME
    
  2. The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.

  3. Extract the SVG file and place it in the images/ folder of this repository.

  4. Use the image in your component's index table entry in /components/index.rst.

Example: For a component called "DHT22 Temperature Sensor", use:

@esphomebot generate image DHT22

@Copilot Copilot AI review requested due to automatic review settings August 23, 2025 03:57
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR documents a change in behavior for the SNTP component's on_time_sync trigger, specifically clarifying that the limitation where the trigger fires only once when the system clock is set now applies only to platforms other than ESP8266 and ESP32.

  • Updated warning message in SNTP documentation to specify platform-specific behavior
  • Adjusted general time component documentation to reflect the conditional nature of SNTP's behavior

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
content/components/time/sntp.md Updated warning to specify that the on_time_sync limitation applies only to non-ESP8266/ESP32 platforms
content/components/time/_index.md Modified note to clarify that SNTP's behavior of triggering when other components change time is conditional

Copy link

netlify bot commented Aug 23, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit 314da33
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/68a93c37d156be0007ee7d7d
😎 Deploy Preview https://deploy-preview-5276--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant