Fix frozen Yr weather-module (#3706)

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.
This commit is contained in:
Magnus
2025-01-27 22:41:51 +01:00
committed by GitHub
parent af77b7b628
commit d6f2e7165f
2 changed files with 23 additions and 4 deletions

View File

@@ -21,6 +21,7 @@ planned for 2025-04-01
- [core] Optimize systeminformation calls and output (#3689)
- [core] Add issue templates for feature requests and bug reports (#3695)
- [core] Adapt `start:x11:dev` script
- [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.
### Removed
@@ -36,6 +37,7 @@ planned for 2025-04-01
- [weather] Fix wrong weatherCondition name in openmeteo provider which lead to n/a icon (#3691)
- [core] Fix wrong port in log message when starting server only (#3696)
- [calendar] NewYork event processed on system in Central timezone shows wrong time #3701
- [weather/yr] The Yr weather provider is now able to recover from bad API resposes instead of freezing (#3296)
## [2.30.0] - 2025-01-01