Use NTP as primary time source and connection handler as fallback #324
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some user reported a wrong behaviour of the scheduler widget due to wrong time. After some investigations we discovered that the time readed from connection handler was wrong.
https://forum.arduino.cc/t/arduino-cloud-scheduler-responding-to-utc-time-instead-of-local-time/992909/21
The issue needs some more investigation to understand if the root cause is a wrong time injected from the provider or some bug in the MKRNB library, but it looks a good idea to change the priority of the time sources and use NTP as first choice and the connection handler as fallback.