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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
2.0.0 is a major overhaul/rewrite of the integration with many different improvements. While this release has been thoroughly tested it's always possible that I missed something, so please open an issue if you see any unexpected behavior.
Breaking changes:
Home Assistant will create a repair for the wind direction sensor (The mean type of 'Home Wind Direction - Degrees' (sensor.home_wind_direction_degrees) changed from 'Arithmetic' to 'Circular') - please choose the option to delete/clear the old data (old data was not calculated correctly).
Fake data is no longer used when the API does not provide a value - because of this some sensors may occasionally be unknown/None. Automations, scripts, and templates that expect these values to always be numeric may need to be updated.
Changelog:
Significant code clean-up and modernization, including:
Vastly improved error handling
Deduplicated and simplified several parts of the codebase
Migrated from the old ways of doing things to the modern ways of doing those things (e.g. switch from hass.data[DOMAIN] to entry.runtime_data, switch to Home Assistant's native translation handling, etc.)
Added several constants and adopted those constants throughout the codebase
Fixed a bug where it wasn't possible to use a latitude or longitude of 0
Fixed a bug where icon code 0 (Tornado) would be replaced by icon code 44 (Not Available)
Fixed a bug that caused unnecessary disk I/O on every refresh
When the integration is removed its temporary files in storage will now be cleaned up
The forecast details sensor now automatically enables itself when extra attributes are selected
Fixed a bug where reconfiguring a location from an entity to latitude/longitude would continue to use the entity's location
Fixed a bug where reconfiguring an integration entry that had been renamed would create duplicate entities and reset the entry's name
Updated the wind direction sensor to use Home Assistant's wind_direction device class and measurement_angle state class
IMPORTANT: This change will create a repair in Home Assistant (The mean type of 'Home Wind Direction - Degrees' (sensor.home_wind_direction_degrees) changed from 'Arithmetic' to 'Circular') - please choose the option to delete/clear the old data (old data was not calculated correctly).
Fixed a bug where location names that differed only by case (capital vs. lowercase) or punctuation would collide and cause errors
Fixed a bug where location names containing special characters (such as /) would fail to save cached temperature data to storage
If a tracked location entity temporarily loses its coordinates, the integration will now fall back to the last known coordinates
Excluded the Forecast Details sensor's extra attributes from the Home Assistant recorder to prevent database bloat
Added twice-daily forecasts to the weather entity
Stopped presenting fake data when Weather.com does not provide a value - these values will now be unknown/None instead:
IMPORTANT: Automations, scripts, and templates that expect these values to always be numeric may need to be updated
The wind gust sensor and the weather entity's wind gust speed no longer fall back to the current wind speed when there are no gusts
Various sensors (including precipitation, snowfall, and forecast details) no longer report 0 when Weather.com does not provide a value
Significant CI improvements, including a full test suite and type checking