-
Notifications
You must be signed in to change notification settings - Fork 22
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
[feature] set the time without using NTP #36
Comments
Due to the use of NTP, I make my life easier. I don't need to care about the following two challenges of making clock with MCU:
For my first Wordclock, I used an RTC module with a battery to avoid time drift and keep the time during the power-off phases. For the second challenge, there exists an interesting post where they tried to keep the time without RTC on an ESP8266 with promising results: https://www.instructables.com/TESTED-Timekeeping-on-ESP8266-Arduino-Uno-WITHOUT-/ I would be happy to hear if you have any other ideas about how to implement this feature while solving the two challenges above. BR |
Ok, I understand your point. another question: what happens if the internet connection fails from time to time (not at the startup of the clock) ? |
If the internet connection fails (the NTP update is unsuccessful), the clock tries to connect to the NTP server for 5 minutes / 30 tries before it automatically restarts. -> This may not be the most clever fallback strategy, but it works out fine, given the expectation that the Wi-Fi network is more stable than the ESP. |
Just another thought: what about no internet access? If you're clock is build and you want to hang it in your garage (where there is no WiFi available)? |
It's the same issue; without internet access, the current version of the word clock will not work. So, the best option would be to add an RTC. |
Wouldn't it be nice to send te time yourself (with the app, or with buttons) so you are not using the NTP service?
The text was updated successfully, but these errors were encountered: