Skip to content
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

[BUG] Time drift with P2P enabled #5119

Open
DittelHome opened this issue Sep 4, 2024 · 3 comments
Open

[BUG] Time drift with P2P enabled #5119

DittelHome opened this issue Sep 4, 2024 · 3 comments

Comments

@DittelHome
Copy link

With P2P enabled, I get time drift. (at least 15 seconds)
NTP only works as expected.
Only disabling P2P fixes the problem.

Regards Klaus

@TD-er
Copy link
Member

TD-er commented Sep 4, 2024

Thanks for the issue. I had already included it in the todo for the next release: #5118
But it is good to also have an issue where others may also provide input and/or see what's going on.

@DittelHome
Copy link
Author

DittelHome commented Sep 4, 2024

Hi, I know about the deepsleep problem and the time drift, I wrote the thread in the forum.
It seems to be a general problem with p2p.
As soon as p2p is activated, the time becomes inaccurate, in comparsion with NTP!!
Of course p2p were already deactivated on Deepsleep devices...

@DittelHome
Copy link
Author

Maybe it helps ..
Today I discovered that an ESP gets the time from another via p2p and vice versa, even though NTP is activated on both. Both have an uptime of over thirty days.
As a result, both are 1 minute and 40 seconds behind, and the trend is increasing

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

No branches or pull requests

2 participants