Repository navigation
2026.10.2 #602
Hankanman
announced in
Announcements
2026.10.2
#602
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.
A big thank you to those who have chosen to sponsor my work!
You can sponsor me here
This release makes what Area Occupancy learns more trustworthy, and starts gathering the evidence for the next big step. There's no database rebuild.
🐛 Fixes
Rooms only learn from time they could actually see (#574)
Until now, every hour counted towards a room's learned habits, including hours when its motion sensor was offline (a flat battery, a Zigbee dropout, a sensor not yet paired). Those hours were learned as "empty", which pulled the room's learned likelihood of being occupied down after any outage. A TV reporting "off" also counted as watching the room, though it can't see that a room is empty.
Now:
Rooms whose motion sensors report continuously won't notice a difference. Rooms that had outages will learn a more accurate likelihood of being occupied.
A one-time repair also clips the last few overlapping sensor records left over from the 2026.9.4 sync issue.
🧪 Shadow mode: proving the maths before it changes your occupancy
Four features are now recording what they would do, without changing any reading. The goal is to prove each one against real homes before it's allowed to affect occupancy. You can see what they're recording in the diagnostics download (Settings → Devices & services → Area Occupancy Detection → ⋮ → Download diagnostics), under each area's
currentblock.When will they go live? The plan is for these to start affecting occupancy in 2026.11.1, once there is more than a month of data from a real install proving the maths holds up. Each one goes live only if its own evidence clears its bar. If the data says one isn't ready, it stays in shadow mode, and the release notes will say why. Nothing changes for you in the meantime.
Want to help? Away mode can only gather evidence if you set an Away mode entity (Configure → Global Settings): an
input_boolean,binary_sensororswitchthat's on while everyone is out, such as a "nobody home" template from yourzone.home, or a vacation toggle. Don't base it on Area Occupancy's own sensors. Diagnostics exports from homes running these are very welcome on the issues above.Upgrade check:
scripts/harness upgradefrom a lived-in 2026.8.1 base to this release reported 0 red flags and all 11 checks passed.Full Changelog: 2026.10.1...2026.10.2
This discussion was created from the release 2026.10.2.
All reactions