2025.12.0 #271
Replies: 3 comments 14 replies
-
|
Simulator room selection drop down seems buggy, I can select the first two rooms in my 4 room list, but if i try to select 3 or 4, then it just returns back to whichever one i was on previously. |
Beta Was this translation helpful? Give feedback.
-
|
I ask about the version because only in a pre-release did it appear as a dropdown, it should be showing as a list in the final release and look something like this: 
I've done a bunch of testing and can't reproduce the issue, can i suggest force re downloading the 2025.12.0 version via hacs again and restarting HA, because it primarily sounds like something didn't get updated right. I'm going to release 2025.12.1 today with some minor fixes and updated docs with full screenshots of what to expect |
Beta Was this translation helpful? Give feedback.
-
|
I'm talking about the simulator, not the configuration dialog? |
Beta Was this translation helpful? Give feedback.
-
|
Ah that makes more sense! Sorry you did say simulator haha |
Beta Was this translation helpful? Give feedback.
-
|
I just tried it from a different PC/browser entirely just to make sure it wasn't my usual PC setup, and yeah, pasting in that block above, I cannot get the simulator to really do what it's supposed to, i think, the controls don't seem to work correctly. If I trim it down to individual rooms, then it does seem to work. I was hoping I could use it to tell me why my Wasp room doesn't seem to work correctly at all, but it doesn't look like it does Wasp mode. Maybe I can at least use it to figure out why no other room I've tried it with works well, either. I feel like I must be missing something about this, because the whole thing just does not work well at all for me, despite it seeming very simple to operate. |
Beta Was this translation helpful? Give feedback.
-
|
I will look into it, the simulator is a bonus and not as well tested. But you're trying to use it exactly what I built it for, to understand what's going on. I'll try your yaml and investigate |
Beta Was this translation helpful? Give feedback.
-
|
I had a rocky time upgrading to 2025.12.0, mostly because when I originally created my AOD devices I named each one with device name I wanted (eg I tried the migration a few times but could not understand why these HA areas were being created. The Now I understand the area mapping I will try a fresh migration but thought I should mention this potential migration pitfall. |
Beta Was this translation helpful? Give feedback.
-
|
That is on me, I had not pointed out the potential issues when migrating. This was critical info I apologise, should have been there, i have update this discussion adn the release notes to include the warning |
Beta Was this translation helpful? Give feedback.
-
|
Not a complaint, just a big comment. lol I didn't have any automations to break yet. I had created "several" dashboards with probability gauges, history graphs etc. etc. I loaded the update when it arrived and didn't have time to even look until tonight. My naming conventions also included many areas previous to update, but also included AOD in the name, and some were not actually even areas named. IE; Hallway AOD instead of South Hallway area. Easy enough to change though. The name where the gear now resides turned into Computer Room AOD, head scratch, change name to Home AOD etc. Assuming new All Areas is what I had already built, House Occupied AOD. Where the new one All Areas, gathers information from all other areas? Calculations changed considerably. Last version was being watched in a graph along with the other GUI Bayesian integration that sorta replaced YAML Bayesian by the other developer. AOD is kinda flat now in comparison to previous version. The Statical graph I have both often in, ran almost like mirror images. one higher, one lower in the graph, but my own timers almost matched exactly what I built easier with your previous version of AOD. What will require more adjustment is working out the time, weights etc. numbers to get AOD back in shape for my use. It's a tremendous amount of hard work you put in and in my opinion will save the Bayesian from HAOS deprecation down the road, your stars show it. AOD, I'll consider the previous version Beta, 🤣, lumps and bumps expected. Hopefully this new model stays as the last major breaking changes, 🤔😁 with only tweaks here and there to fix possible bugs. I fiddled with Bayesian in YAML for quite a while, now that was a trip. Kudos and Accolades for the hard work.💫⭐🌟 |
Beta Was this translation helpful? Give feedback.
-
|
Yep the migration was rough, I did a bunch of testing on mine but clearly I missed a bunch of stuff. Apologies for that. Yes this should be the last breaking change, the config structure changed as did the database schema, but its in a state where I can easily create smooth migrations moving forwards. The "All Areas" device is an average of all other areas at the moment, it seems there was a bug in the migration that meant how it got created or named got really confusing. I have over 1000 tests in the test suite and still stuff gets through!! Thank you for the kind words, yes a lot of work went in and its wonderful to hear its appreciated, even when it broke completely during migration 😒😁 I created a new discussion for dashboards as i'd love to see what you put together! i started by sharing mine: |
Beta Was this translation helpful? Give feedback.
-
|
I was wondering how this integration compares with the newly released https://www.home-assistant.io/blog/2025/12/03/release-202512/#purpose-specific-triggers-and-conditions |
Beta Was this translation helpful? Give feedback.
-
|
So when you are making an automation the article states:
The target of this integration is to understand what is currently happening in an area, so you can build automations off of it. It takes all the information of different entities and figures out what's going on. So you can ask,
What we are doing with AOD is much closer to machine learning, instead of a million if statements in automations. I'll add a doc or update, to your suggestion to clarify. But I hope that gives a bit of an idea. There are a couple features planned that will make this really powerful. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! Maybe something to add to the readme? I'm sure it will help many new users. |
Beta Was this translation helpful? Give feedback.
-
|
Updated the readme, hopefully that clears it up for new users 😊 |
Beta Was this translation helpful? Give feedback.
-
|
I had some doubts if I needed this integration. Those doubts just got obliterated. This integration should become part of HA Core. It's amazing. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The biggest release of the integration to date.
This version introduces a brand-new architecture for areas, a real statistical engine for numeric sensors, a redesigned configuration experience, and a fully interactive probability simulator to help users understand exactly how the system behaves.
Thank you again to everyone starring, sharing, and testing the project — the growth has been incredible since the last release we somehow have almost doubled our stars! This release reflects weeks of work driven directly by your feedback.
The following applies if you are upgrading from a version before 2025.12.0.
Warning
There is a lot of core changes, everything should migrate automatically, please read the below before updating. Submit an issue if you have problems.
Caution
If you have renamed entities and rely on them for automations, this update will break those automations, this is due to a change in how Unique IDs are generated for the entities to align with Home Assistant best practice.
Caution
When updating AOD will attempt to match existing configured AOD areas to real HA Areas, If you do not have Home Assistant Areas that match names of the AOD areas, new Home Assistant areas will be created for you to allow the migration to complete. You can correct the AOD areas following migration if need be reconfiguring AOD areas and assigning the correct HA Area
🎉 New & Updated Features
🎚️ Interactive Probability Simulator
A brand-new visual simulator is now available on the documentation site.
Try it out here
It allows you to flip your entities on and off to see the effect without having to run around you house to trigger things
You can now experiment with:
The simulator uses the real integration code and therefore behaves exactly like the real integration. I built it to help myself better visually see what is going on and i think it will be of great help to you guys too!
It's designed to help you understand why a room is being marked occupied or not - without needing to guess or dig through logs.
A huge step forward for transparency and ease of tuning.
Note
A server runs to allow the real code to be executed. You therefore send data to that server to process, Nothing is stored, just calculated and sent back. The data you send is from the
Run Analysisservice of the integration, you can inspect exactly what you are sending before you load the simulation.🌐 Multi-Area Architecture
The integration now supports multiple areas under a single configuration entry, each with its own sensors, priors, decay, and analysis.
This is a foundational redesign that enables future features like room-to-room influence, directional flows, and graph-based occupancy models.
📈 Real Numeric Sensor Intelligence
Numeric sensors are no longer static inputs — they now participate in real statistical analysis.
New analytic capabilities:
Supported inputs now include:
This dramatically improves detection accuracy in low-motion environments such as bedrooms, offices, and lounges.
⚙️ Redesigned Configuration Flow
The setup UI has been rebuilt from scratch:
The new flow is faster, clearer, and much easier to use.
🚪 Wasp-in-Box: Improved Accuracy & New Features
The Wasp in Box system now benefits from the new multi-area model and includes improved handling of:
The docs now include updated diagrams and examples aligned with the new architecture.
📊 Performance & Database Improvements
🔄 New Aggregation & Correlation Engine
The analysis pipeline has been restructured:
Combined with smarter session handling and async offloading, the integration now places considerably less load on Home Assistant.
🧠 Smarter Priors & Time Modelling
These improvements stabilise behaviour when data is sparse and eliminate spikes or drops due to edge-case timestamps.
🧹 Entity, Device & Migration Improvements
This release significantly reduces “mysterious states” or stale entries during updates.
🐞 Bug Fixes (Highlights)
A huge amount of stability work has gone into this version.
📄 What’s Changed
Full Changelog: 2025.11.2...2025.12.0
Beta Was this translation helpful? Give feedback.
All reactions