Patch release. Two small QoL fixes (lightning popup distance now respects HA's unit_system; broken Blitzortung-integration link in the docs corrected) and the per-user state framework lands on main as dormant infrastructure for v3.7.
No breaking changes. Drop-in patch over 3.6.4. HACS users with auto-update will see this as a routine update.
Fixed
Lightning strike distance now uses HA's preferred length unit (#176)
The popup that opens when you click a lightning strike was always showing distance in "km" regardless of HA's unit_system setting. Imperial users had to mentally convert.
Now reads hass.config.unit_system.length and formats as "45 km" or "28 mi" accordingly — same signal already used by the Leaflet scale control and range rings. Wildfire / NWS-alert popups don't display distances, so this only affects the lightning popup.
Broken Blitzortung-integration link in docs (#177)
🙏 Thanks to @mweinelt for catching this. The README, configuration docs, overlays docs, and lightning-feature-design all linked the Blitzortung integration as home-assistant.io/integrations/blitzortung/ — a 404, because there's no native HA Blitzortung integration. The actual integration is the third-party HACS one at github.com/mrk-its/homeassistant-blitzortung. All four references corrected.
While fixing it, audited every URL in shipped docs (118 unique URLs) and confirmed this was the only real broken link.
Internal
- Per-user state framework added on
main(#175). Newsrc/viewer-state.tswraps HA's frontend storage WebSocket API to support v3.7's per-user runtime customisation features (layer visibility panel, playback speed override). Dormant in this release — no consumer wired up yet, no behaviour change. Documented indocs/viewer-state-api.mdfor contributors.
Upgrade notes
No config changes. Drop-in patch over 3.6.4.
Full Changelog: v3.6.4...v3.6.5