2026.5.1 #453
Hankanman
announced in
Announcements
2026.5.1
#453
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
✨ New: Diagnostics Export (#447)
Home Assistant's standard Download diagnostics is now wired up for the integration - one click captures a complete JSON snapshot of priors, weights, evidence, decay state, learned correlations, occupied-intervals cache freshness, and cached health issues without enabling DEBUG logging.
Open the integration card in Settings → Devices & Services, click the ⋮ menu, and choose Download diagnostics. The export is grouped into
integration(versions, config schema, area count),areas(per-areacurrent/prior/config/entities/healthsubsections), anddatabase(row counts and per-area cache validity). Each entity row includesanalysis_error,correlation_strength,evidence,previous_evidence,last_updated, and full decay state - every field a triager would otherwise have to ask for.This is the right thing to attach when opening a "why does occupancy look wrong?" issue. See the new Diagnostics docs for the full field map and what questions the dump can answer.
✨ New: Pipeline Health Checks (#448)
The same hourly health monitor that flags stuck/offline sensors now also flags calculation pipeline problems per area, surfaced in Settings → System → Repairs under their own
pipeline_health_*translation key family.Each repair has a tailored "What to do" section, and all four auto-resolve when the next analysis cycle finds the underlying state has recovered.
✨ New: "Reset Learning" UI Button (#451)
Resetting a single area's learned history no longer requires calling the
area_occupancy.purge_area_historyservice from Developer Tools. Open Configure → Manage Areas → <area> → Reset Learning, confirm, and the area's intervals, priors, correlations, and aggregates are wiped while the area config and sensor selection stay intact. The next analysis cycle starts re-learning from current recorder data.Same destructive behaviour as the YAML service - same trade-offs.
Performance
run_correlation_analysispreviously walked every (area, entity) pair serially, so the analysis step's wall-clock time scaled with the sum of per-area work. Per-area calls now run viaasyncio.gather(..., return_exceptions=True), dropping the wall-clock to roughlymax(per-area)while keeping per-entity loops within an area serial (preserves error semantics, doesn't saturate the executor pool). One area's failure no longer aborts the others.Fixes
Docs
purge_area_historyservice plus the equivalent UI flow.Issues Resolved
A big thank you to those who have chosen to sponsor my work!
You can sponsor me here
What's Changed
New Contributors
Full Changelog: 2026.4.1...2026.5.1
This discussion was created from the release 2026.5.1.
Beta Was this translation helpful? Give feedback.
All reactions