Magic Areas 3.0! A major revamp!
After a year from last release and months of hard beta testing (a HUGE thank you for the community that helped test and reported bugs ❤️), release 3.0 is finally out!
This new major version is BREAKING and you WILL have to reconfigure your areas even if you were in the 3.0 beta release! If you have a large setup, take some time, grab some coffee play some smooth jazz (or metal, depending on your mood) while upgrading.
There were significant changes to support UI configuration and some normalization of unique_ids which means you will have to delete all your Magic Areas and re-create them after upgrading. There was no way to avoid this and I apologize for the hassle!
I've tried to add extensive documentation to the Wiki. If you are having problems, hop onto our Discord server for help!
3.0 New features and notable changes
- Features no longer listen to entities. New IPC / event-based system lets features just listen to events instead and let the single binary sensor track all the relevant entities. This was the bulk of the 3.0 release which DRASTICALLY improved both speed and overall reliability. Huge shout out to @caphm who started all this.
- Secondary states were introduced. Make sure to head out to the wiki to read about the concepts.
- Light Group feature now creates a
switchentity (switch.area_light_control_$area-slug) that allows you to switch light control on/off on the fly, no longer having to work withPresence Holdto prevent light actions from happening. - All binary_sensor device classes are available for presence detection on the area configuration
- Config flow selectors! @jseidl (#212) The UI is MUCH nicer and less convoluted which makes configuring your Magic Areas way easier!
- Presence Hold Timeout (#58 ) @sti0 - You can now set a timeout for presence hold.
on_statesis no longer a free-text field because the workaround we had to do to support that is no longer working with config_flow. It's now a list of predefined values that the user can chose from. Let me know if you need other states that are not on the list.- Removed behavior where if you didn't had any group configured for the
occupiedstate, all lights would turn on. You can still replicate that by adding all light groups to theoccupiedstate.
All feature requests and questions were moved to GitHub Discussions. The issues area will be used for bug reports only.
Full list of changes
🚀 Features
- Event-based IPC @jseidl (#126) This PR includes fixes from @caphm's PRs which gave us multi-step config options, more async/event driven behavior and fixes for many open issues.
- Add binary sensor vibration / connectivity device class for presence detection (#99) @sti0
- Light Group "All Lights" turn_on behavior removal @jseidl (#233)
🐛 Bug Fixes (from 3.0 beta)
- Fix Iterable import on util.py @jseidl (#234)
- Meta area exclude entities @jseidl (#232)
- Device uom pair regression fix @jseidl (#231)
- uniqueid standardization @jseidl (#227)
- fixing regression @jseidl (#224)
- Magic groups entity @jseidl (#222)
- removed integration name from unique ids bc is bad practice @jseidl (#223)
- checking if entity is on self.all_entities (valid) @jseidl (#221)
- Hotfix/magic groups entity @jseidl (#222)
- Hotfix: cover without device class name fix @jseidl (#210)
- Aggregate sensor device_class/unit of measure map key bug @jseidl (#211)
- Fixing light group attributes @jseidl (#207)
- Flatten entity groups @jseidl (#205)