v1.0.0
Breaking
The Lovelace card now lives in its own repository, ha-beach-weather-card, and has to be installed separately (HACS → Dashboard → Beach Weather Card).
Up to 0.24.0 the card shipped inside this integration, which registered a Lovelace resource for it under /beach_weather_static/. Writing the user's shared lovelace_resources store from a config entry is not an integration's job — HACS does that as the package manager, visibly and with an uninstall path, which is where the card belongs.
Existing dashboards keep working unchanged: same custom:beach-weather-card type, same config format, same entity IDs. Only a custom background_image pointing at a /beach_weather_static/... URL has to be repointed.
The minimum Home Assistant version is now declared as 2024.12.0. The previously declared 2024.1.0 was never accurate: lovelace.const.LOVELACE_DATA only exists from 2025.2, the resource_mode attribute read in 0.24.0 only from 2026.2, StaticPathConfig from 2024.7, and the implicit OptionsFlow.config_entry from 2024.12. Dropping the card removed the first two constraints, so the real floor is now the options-flow one.
Upgrading
- Update this integration
- Install Beach Weather Card from HACS → Dashboard
- Reload the browser
Added
- A one-time cleanup on start removes the Lovelace resource earlier versions registered under
/beach_weather_static/. Without it, updating would leave a resource pointing at a path nothing serves any more, which Lovelace retries on every dashboard render. Nothing else in the resource store is touched, and the integration never writes to it again
Changed
- The download no longer carries the card and its seven photos — about 1.8 MB less
- Diagnostics also redact the location name and its slug, and redact the raw coordinator payload (which echoes the requested coordinates) rather than passing it through unfiltered
Fixed
- README: HTTP 503 backs off for 30 seconds, not the 5 minutes documented — the value has been 30s since 0.22.1 but only the changelog said so