You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes#3296
The problem was that the fetch-methods threw errors when something went
wrong instead of calling `updateAvailable()`. `updateAvailable()` must
be called in order to schedule the next update.
I added some filtering for the hourly forecast that removes hours in the
past. If the API call fails we use the cached data, but we should only
display hours in the future.
Copy file name to clipboardexpand all lines: CHANGELOG.md
+2
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,7 @@ planned for 2025-04-01
21
21
-[core] Optimize systeminformation calls and output (#3689)
22
22
-[core] Add issue templates for feature requests and bug reports (#3695)
23
23
-[core] Adapt `start:x11:dev` script
24
+
-[weather/yr] The Yr weather provider now enforces a minimum `updateInterval` of 600 000 ms (10 minutes) to comply with the terms of service. If a lower value is set, it will be automatically increased to this minimum.
24
25
25
26
### Removed
26
27
@@ -36,6 +37,7 @@ planned for 2025-04-01
36
37
-[weather] Fix wrong weatherCondition name in openmeteo provider which lead to n/a icon (#3691)
37
38
-[core] Fix wrong port in log message when starting server only (#3696)
38
39
-[calendar] NewYork event processed on system in Central timezone shows wrong time #3701
40
+
-[weather/yr] The Yr weather provider is now able to recover from bad API resposes instead of freezing (#3296)
Log.error("The Yr weather provider requires local storage.");
24
24
thrownewError("Local storage not available");
25
25
}
26
+
if(this.config.updateInterval<600000){
27
+
Log.warn("The Yr weather provider requires a minimum update interval of 10 minutes (600 000 ms). The configuration has been adjusted to meet this requirement.");
0 commit comments