Weather pages
- Fixed the weather forecast pages failing to load, and the Blueprint automation stopping with a template error, when the weather provider's forecast had no low temperature for a day. The lowest temperature of the day is now used instead (#671).
- Forecast values that are not numbers (for example
unknownfrom some weather providers) are now skipped instead of stopping the page from loading (#672). - The minimum temperature of a day now also considers forecast periods without a low temperature, such as hourly periods or the night period of twice-daily forecasts. Before, it was taken only from the periods that had one, which could show a minimum higher than the forecast.
Performance
- The weather pages now use far fewer templates, bringing the Blueprint below 1,024 distinct templates, the size of Home Assistant's template cache. This reduces the load on Home Assistant, especially with several panels. Nothing changes on the panel (#669).
Development
- Pull requests changing the Blueprint are now checked by equivalence tests, which compare what the panel receives before and after the change (#670).
What's Changed
Other Changes
- ci: Run the Blueprint equivalence tests on pull requests by @panel-easy-assistant[bot] in #670
- fix: Weather pages failing when a forecast day has no low temperature by @panel-easy-assistant[bot] in #671
- improve: Skip non-numeric weather forecast values by @panel-easy-assistant[bot] in #672
- improve: Render weather page variables as single templates by @panel-easy-assistant[bot] in #669
- fix: Weather pages failing on incomplete forecasts by @edwardtfn in #673
Full Changelog: v2026.11.11...v2026.11.12