Fix: allow clock sync to correct time drift after sleep #1326
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ESP32's internal RTC drifts during light sleep due to the 150kHz RC oscillator. When the device clock runs ahead, the previous logic rejected correct time from mobile because "clock cannot go backwards". This prevented fixing drifted clocks. Removed the forward-only restriction from both `clock sync` and `time` commands to allow syncing to the correct time regardless of direction.
|
I have tried similar approach before with "clock fsync". However, when I login into the repeater, the Status still shows old time for Last Login. Have you managed to figure out / fix it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ESP32's internal RTC drifts during light sleep due to the 150kHz RC oscillator. When the device clock runs ahead, the previous logic rejected correct time from mobile because "clock cannot go backwards". This prevented fixing drifted clocks.
Removed the forward-only restriction from both
clock syncandtimecommands to allow syncing to the correct time regardless of direction.