v0.6.3

Fixes a pairing annoyance for anyone upgrading from 0.5.x.

• Upgrading from 0.5.x no longer shows your own LocalSky as a new discovered device: discovery now recognizes entries created before instance-uuid identity and upgrades them in place
• Manually re-adding an already-configured instance updates the existing entry instead of creating a duplicate
• Entity ids are untouched in both cases

Requires Home Assistant 2024.11+ and LocalSky 0.2.0+.

v0.6.2

Internal modernization, no functional changes.

• State storage moved to Home Assistant's current entry.runtime_data pattern (typed config entry; platforms, diagnostics, and services no longer reach through hass.data)
• Test coverage expanded from config flow to entry lifecycle, coordinator internals (SSE parsing, reconnection, reauth triggers), and manifest-driven entities
• CI on current action releases (node24), validation badges and one-click install buttons in the README

Requires Home Assistant 2024.11+ and LocalSky 0.2.0+.

v0.6.1

Self-hosted brand icons (HA 2026.3 mechanism), hassfest-clean and fully translated error strings. Requires LocalSky 0.2.0+.

v0.6.0

API-token auth + reauth, zeroconf discovery, i18n (en/es/de/fr), full test suite. Requires LocalSky 0.2.0+.

v0.5.0 — HA sub-device grouping

Device parity: entities now group into HA sub-devices

LocalSky entities previously all landed flat under a single "LocalSky" device. As of 0.5.0 they are organized the way LocalSky's own Device view shows them, mirroring the Music Assistant style of cross-app device parity.

Under the top-level LocalSky hub, entities now group into sub-devices linked via via_device:

• LocalSky Tempest (weather station): air temp, humidity, wind, rain, UV, lightning, pressure, the weather entity, etc.
• LocalSky Irrigation (controller): per-zone planned/run sensors, soil moisture/bucket, valves, run switches, the verdict/reason sensors, and the watering knobs (min temp, max wind, rain skip).

Grouping is driven entirely by each entity's manifest snapshot field, so no configuration is needed. Update the integration and restart Home Assistant; existing entity IDs are preserved and simply re-parent under the new sub-devices.

Notes

• No breaking changes to entity IDs, state, or services.
• A "Forecast" sub-device label is reserved for future forecast-grouped entities; it only appears once such entities exist.