Releases: jseidl/hass-magic_areas
3.1.1
Please read the 3.1.0 release notes if you're not upgrading from 3.1.0.
This is a small hotfix to fix a regression on Climate Groups where groups would be created regardless of the feature being enabled for that area, as long as you had climate devices. This was a regression from the code refactor and is fixed in this release.
Thanks Discord member Ragle for reporting!
Also on this release I'm addressing an issue identified by @tbrasser regarding the new function parameters for the AreaEntry object coming up on the channel branch of Home Assistant. Now as long as we can keep catching those changes on the beta branch, we can future-proof breakings for stable users.
🐛 Bug Fixes
Other Changes
Contributors
Assets 2
3.1.0
⚠️ You need to removemagic_areas:from your configuration.yaml before restarting when you upgrade! You don't need to reconfigure anything as configuration will be kept!
The 3.1.0 version brings a LOT of changes that users will not even notice and a couple really nice quality-of-life improvements. First, I got rid of the automatic creation of Magic Area integration entries on load and opted to follow the full GUI experience. Now you can add (and remove!) Magic Areas for any area you want! Secondly, Magic Area entries are now a device in Home Assistant allowing you to see all it's switches and sensors in one place.
We're also fixing the bug introduced by Home Assistant 2024.2 which introduced area icons. I'll be shortly deprecating the icon attribute on Magic Areas in favor of using the area's icon.
The whole codebase was revised and a majority of it was refactored to make it more repeatable, stable and fast. Over 1.5k lines of code were removed and another 1.5k were added.
I'd like to give a huge thanks our Discord members who helped beta-test this release. You folks are the best! ❤️
🚀 Features
- Area Devices + Major code refactor @jseidl (#300)
- Config flow setup @jseidl (#299)
- Adding last_active_sensors to better help debug flipping sensors @jseidl (#310)
- Adding support for binary sensors to act in ALL mode @jseidl (#303)
- Light groups now release control if manually controlled @jseidl (#284)
🐛 Bug Fixes
- Fix loading issues under 2024.2.0 @grinco (#309)
- Update climate.py fix for 2024.1 @tbrasser (#298)
- Add async to load_entities method in add_entities_when_ready @Julien-Decoen (#315)
- Checking if area was just occupied when bright before turning off @jseidl (#302)
- Fixing condition to skip binary sensors w/o device class @jseidl (#301)
- Fixing dict copy that was overwriting entity_id @jseidl (#283)
🧰 Maintenance
- Updating minimum HA version on HACS.json by @jseidl in #277
- Fixed CI pipeline now that ha-blueprint is deprecated @jseidl (#307)
- Updating some metadata and readme for latest updates @jseidl (#311)
- Updating minimum HA version on HACS.json @jseidl (#277)
✨ New Contributors
- @tbrasser made their first contribution in #298
- @grinco made their first contribution in #309
- @Julien-Decoen made their first contribution in #315
Full Changelog: 3.0.2...3.1.0
Contributors
Assets 2
3.0.2
This is a mostly-bugfix release to address the failure to load in the latest HA update, thanks for our hero @cerebrate!
Also shipping on this release is a few fixes for things being deprecated (thanks @frenck!) and some minor features including a German localization by @klatka and a missed "feature" of having the sun.sun available as a dark state.
🚀 Features
- Add german localization @klatka (#275)
- Adding SUN_DOMAIN (sun.sun) to the config flow entity filter @jseidl (#274)
🐛 Bug Fixes
- Update init.py to fix #265 which caused MA failing to load on recent HA update @cerebrate (#269)
- Fixing version number on release drafter @jseidl (#276)
- Replacing the deprecated DEVICE_CLASS_ variables @jseidl (#273)
🧰 Maintenance
All Changes
Contributors
Assets 2
3.0.1
⚠️ WARNING! If you're coming from 2.x releases, read CAREFULLY the release notes for 3.0.0 as there are BREAKING CHANGES
This release is a minor bugfix (major bug, minor fix) for the configuration UI who lost defaults, optional fields and selectors stopped working after a Home Assistant update. Turns out it was poorly implemented by me and now I hope that I got it right this time.
This has been tested in my dev env, in my production deployment and also by community members, if you still experience issues please cut me a bug report!
Changes
🐛 Bug Fixes
Contributors
Assets 2
3.0.0
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)
🧰 Maintenance
Contributors
Assets 2
3.0.0-beta2
This is a minor release fixing the breakings brought by Home Assistant's 2022.4 update.
What's Changed
Contributors
Assets 2
3.0.0-beta1.1
Adding more debug logging to initialization
Read all info https://github.com/jseidl/hass-magic_areas/releases/tag/3.0.0-beta if you're not upgrading from the last beta! As the 3.x release is BREAKING and NOT BACKWARDS COMPATIBLE.
3.0.0-beta1
Fixed all bugs reported on #144 and Light Group feature now creates a switch entity (switch.area_light_control_$area-slug) that allows you to switch light control on/off on the fly, no longer having to work with Presence Hold to prevent light actions from happening.
on_states is 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.
Read all info https://github.com/jseidl/hass-magic_areas/releases/tag/3.0.0-beta if you're not upgrading from the last beta! As the 3.x release is BREAKING and NOT BACKWARDS COMPATIBLE.
3.0.0-beta
Changes
This is a beta release for the 3.0.0 version.
This new major version is BREAKING and you will have to reconfigure your areas. This is currently under TESTING (I've been running for a week at my home but bugs might still exists!)!
The general configuration should hold but since we moved the configuration storage for the features you will need to reconfigure your areas.
Issue tracker: #144
🚀 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.
- Presence Hold Timeout (#58 ) @sti0 - You can now set a timeout for presence hold.
- Add binary sensor vibration / connectivity device class for presence detection (#99) @sti0
Huge thanks for all contributors! I'm still missing the cool smart behavior for light groups from @caphm but that will be coming shortly!
Contributors
Assets 2
v2.0.5
HA update 2021.8.0 added a new requirement and we hadn't added yet. Thanks @cerebrate for the quick patch!
Changes
- Fixes integration breaking with latest HA update #132 @cerebrate