-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[netatmo] Update time not synchronized with new weather data #16502
Comments
Observing your log, on this time window :
I can observe that there are some missing calls at 11:31, 12:02, 12,22. The RefreshCapability makes the assumption (shown here as 'could be false') that it is called without interruption, causing this drift. Two things: I'd like on input on (1) and will see how to address (2). I have another PR pending affecting RefreshCapability, so likely I will not work on this one until the other one is merged. |
I don't think that the calls are missing. They are slightly switching before and after new data is available. Newer logs:
I let the debug log on and trying to catch the situation like 2024-02-16 |
I have new logs. Shortly after restarting the thing (~2h) the update gets from a 5s data delay to > 10min data delay.
|
During testing of #16489 I noticed that apparently the refresh interval is "locked in" once calculated. Recent example with two weather stations:
|
After some hours or days the time when new weather data are requested are no longer shortly after netatmo offer new data.
Compare the update time with the received data timestamp:
Expected Behavior
timeline
D: This is when the API provides new data
R: This is when the binding fetches the data
Current Behavior
Current behavior after some hours/days:
Most of the time I get old data.
Possible Solution
In RefreshCapability.java, the dataValidity is never re-evaluated as soon as refreshConfigured is set to true.
It loses its validity over time. It should be re-evaluated regularly.
Your Environment
The text was updated successfully, but these errors were encountered: