The changes to the ZAMG integration should be listed as breaking changes, for
a) some of the monitored_conditions are not recognized anymore
Invalid config for [sensor.zamg]: value must be one of ['dewpoint', 'dewpoint_average', 'humidity', 'precipitation', 'pressure', 'pressure_sealevel', 'snow', 'sun_last_10min', 'temperature', 'temperature_average', 'wind_bearing', 'wind_max_bearing', 'wind_max_speed', 'wind_speed'] @ data['monitored_conditions'][7]. Got 'sun_last_hour'. (See ?, line ?).
b) some of the entity_ids changed (most likely because the friendly names of the sensor family (the “suffix” for all monitored conditions) cannot be overridden anymore)
For example:
- platform: zamg
station_id: 11389
name: St. Pölten/Landhaus # The name fetched from the Server is "ST.POELTEN LANDHAUS"
...
resulted in entity_ids of sensor.st_polten_landhaus_*, instead of sensor.st_poelten_landhaus_* (o→oe).
The dashboard now throws this massive chain of capital letters at you: “ST.POELTEN LANDHAUS dewpoint”, as one example.
And last but not least: For the first time while using this integration (on several HA instances and for more than a year now) I observe a lot of failed data fetches, resulting in unknown sensor states – is it blocked due to too many requests? (I fetch data from 2 stations)
Some log examples:
Logger: homeassistant.components.zamg
Source: helpers/update_coordinator.py:151
Integration: Zentralanstalt für Meteorologie und Geodynamik (ZAMG) (documentation, issues)
First occurred: 11:40:29 (2 occurrences)
Last logged: 11:51:03
Timeout fetching zamg data
Logger: homeassistant.components.zamg
Source: helpers/update_coordinator.py:151
Integration: Zentralanstalt für Meteorologie und Geodynamik (ZAMG) (documentation, issues)
First occurred: 10:15:12 (5 occurrences)
Last logged: 11:45:52
Timeout fetching zamg data
Error requesting zamg data: Cannot connect to host dataset.api.hub.zamg.ac.at:443 ssl:default [Connect call failed ('138.22.160.100', 443)]
