Skip to content

Releases: jseidl/magic-areas

4.4.1

11 Sep 16:29
@github-actions github-actions
4.4.1
8b8699e

Choose a tag to compare

View all tags
4.4.1 Latest
Latest

This is a minor bugfix update fixing an issue with the new area reload functionality that causes high-load when reloading.

As a side update, @VPelt added the FAN domain to the list of allowed entities in the "Include entities" option. Thanks!

🐛 Bug Fixes

  • Prevent magic areas from reloading on its own entity changes and before HA is fully initialized @jseidl (#553)

Changes

Contributors

jseidl and VPelt
Assets 2
Loading

4.4.0

30 Aug 18:04
@github-actions github-actions
4.4.0
cbfb54f

Choose a tag to compare

View all tags
4.4.0

Hello Wizards! 🧙‍♂️ This release brings a little extra magic to your homes. ✨
We’ve banished the race condition gremlins once and for all! Areas now reload at just the right moments — after Home Assistant finishes starting, when entities or devices are added or move between areas, and when configurations are updated.

The magic doesn’t stop there: meta areas, including floors, now automatically reload whenever one of their child areas reloads. No more manual reloads to catch all your entities — the system handles it for you, smoothly and reliably.

On top of that, Wasp in a Box has learned a new trick: a configurable timeout that prevents motion flickers from spoiling the spell. Add in fresh translations and a shiny README, and you’ve got a release full of stability, polish, and a touch of magic.

Thanks again our community members @andreasbrett for updating the German translations for the new "Wasp Timeout" field and @Julien-Decoen for helping with the area reload rework and beta-testing❤️

🚀 Features

🐛 Bug Fixes

  • Reload meta-areas on regular-area load @jseidl (#511)

🧰 Chores

Contributors

jseidl, andreasbrett, and Julien-Decoen
Loading

4.3.1

06 Aug 16:25
@github-actions github-actions
4.3.1
19ed12d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
4.3.1

This is a minor update to prevent a bug on upcoming version of home assistant 2025.8. The core recently had a change to how Threshold Sensors are initialized.

Thanks @andreasbrett for updating the German translations ❤️

🐛 Bug Fixes

Changes

Contributors

jseidl and andreasbrett
Loading

4.3.0

08 Mar 08:49
@github-actions github-actions
4.3.0
ce97a27

Choose a tag to compare

View all tags
4.3.0

This is a major update. Please read through the release notes and breaking changes especially. The docs/wiki was updated with information about the new features, please check it out if you have any questions or hop on our Discord server if you need additional help.

A huge thank you to everyone who helped test this version and shared their feedback allowing me to quickly validate the changes and release early!

The end of Climate Groups

Climate groups was an underutilized feature that did not performed climate control very well as it was limited to turning the climate devices on or off. I've made Climate Groups initially to control "Generic Thermostats" which I used to control fans based off a temperature sensor, so from concept, climate groups were never intended to be a real climate control solution but rather a fancy turn-on-and-off my fans.

Climate devices isn't something you usually group, even Home Assistant doesn't have support for grouping climate devices and I had to Frankenstein code in order to make it work. It was a sign to me that probably Climate Groups was a mistake, and it was.

Note

Although Climate groups is no longer available, two new features should pick up the slack and perform much, much better: Climate control & Fan groups.

Rest in peace Climate Groups, you won't be missed!

Fan groups

Fan groups are supposed to do what I used to do with the Generic Thermostat and Climate Groups. Fan groups can be tied to track a given aggregate sensor (say, temperature) and turn the grouped fans on or off based on a configured setpoint. It does basically the same as the duo mentioned before, but without the overhead of having to create a Generic Thermostat.

Climate control

Climate control is a feature that possibly most of the community have been looking for in terms of actually smart climate control. This feature allows you to map an area's states (both primary and secondary) to given presets of a climate device. You can now, for example (using "Interior" Meta-area):

  • Set HVAC to away when your "Interior" area is clear
  • Set HVAC to home when your "Interior" area is on "extended" state
  • Set HVAC to sleep when your "Inteiror" area is on "sleep" state.

Tip

If you have multi-floor HVAC, you should use floor meta-areas and enable this feature on it. The controlled climate device does not need to be in the same area as the climate control feature.

Meta-area secondary states revamp

Meta-areas only really tracked primary states (occupied/clear). In this release, you can choose between 3 calculation modes and the meta-area's secondary states will be calculated off their children. The default calculation mode is called "majority" where if >50% of the child areas are on "sleep" state, so it will be the meta-area. Other available modes are all and any, which are self-explanatory.

Wasp-in-a-box

Probably the most upvoted feature ever on our feature request board must be the Wasp-in-a-box functionality. Well, now you have it!

Wasp-in-a-box is a great feature for when you have limited presence sensors (such as no mmWave) or in areas that are challenging to cover such as garages. To learn more about this feature, it's better to read on the wiki!

📄Wiki Article: Magic Areas in every room!

I've wrote a new wiki article with examples on how can you use Magic Areas in every type of room in your home, make sure to check it out!

⚠️ Breaking changes

  • update_interval option was removed. This option didn't bring a lot of value as a configuration parameter and is now hardcoded to one minute. If you had this configured to something else, well, it's one minute now 😛

🚀 Features

🐛 Bug Fixes

  • Fix color mode resolution to not use deprecated constants @jseidl (#509)
  • Add is_meta checks on switches that are not available to meta areas @jseidl (#503)
  • Fix area default icon not showing up @jseidl (#502)
  • Reduce aggregates default device classes @jseidl (#501)

🧰 Maintenance

Contributors

jseidl and VPelt
Loading

4.2.1

11 Feb 05:51
@github-actions github-actions
4.2.1
99bb07a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
4.2.1

What's Changed

  • Fix device-class resolution on sensor and binary sensor platforms by @jseidl in #480

Full Changelog: 4.2.0...4.2.1

Contributors

jseidl
Loading

4.2.0

08 Jan 08:59
@release-drafter release-drafter
4.2.0
b12aee9

Choose a tag to compare

View all tags
4.2.0

Happy new year! This is a long due new release of Magic Areas with a couple new (exciting!) features, a bunch of bugfixes and some code improvements.

tl;dr: BLE Tracker support, Meta-areas now track Magic Entities, Magic Areas now auto-reloads on entity/device area change and can ignore diagnostic entities. Area-Aware media player and Climate Groups fixed. One entity_id has changed, see below!

⚠️ The entity_id (and unique_id) for the "All Lights" entity for all Meta-Areas has changed as it was missing the translation_key that every other entity has in order to support translation. This was missed when I first implemented translation and will not be changed again.

🚀 Features

  • Ignore diagnostic and config entities @jseidl (#470)
  • Support BLE Trackers as source of presence @jseidl (#467)
  • Reload Magic Areas entry when entity registry is updated @jseidl (#422)
  • Set control switches to CONFIG entity_category @jseidl (#415)
  • Migration for meta areas to use magic entities only @jseidl (#458)
  • feat(translation): add french translation file @Julien-Decoen (#410)

🐛 Bug Fixes

  • Fix broken climate groups @jseidl (#469)
  • Add translation key to meta "All lights" group @jseidl (#408)
  • Fixing Area-Aware media player @jseidl (#460)
  • Added logic to handle state class TOTAL INCREASING @jseidl (#453)
  • Show correct icon for floor meta areas @jseidl (#452)
  • Fixing entity id resolution for area aware media player @jseidl (#414)

Other Changes

Contributors

jseidl, marcjay, and 3 other contributors
Loading

4.1.0

05 Sep 06:43
@release-drafter release-drafter
4.1.0
59e738d

Choose a tag to compare

View all tags
4.1.0

This release brings up two new features/enhancements:

  • Keep-only sensors: You can now select which presence sensors will be ignored unless the room is already occupied. This is super useful for flappy sensors such as mmWave and BLE trackers.
  • Light threshold sensor now has configurable hysteresis. This will allow you to tune its "sensitivity" to changes.

Some fixes:

  • Unit of measurement on sensors was kinda spotty. I've refactored the code to consider the unit of measurement is more "popular" between your sensors of the same device class in that area and set that to the sensor group (aggregate), HA should deal automatically with unit conversions. @tbrasser spotted an issue with what I was using to resolve unit of measurements on the beta channel and was the trigger for me to look for a better way of doing it. Thanks again for keeping an eye on the beta channel! ❤️
  • Added tests for a lot of stuff, there's still a lot to go but should considerably increase the stability of releases.
  • Lastly, I seem to finally have figured it out (after 4 breaking changes) what was causing breaking changes, so we shouldn't have many more of those in the future.

🚀 Features

  • Aggregates illuminance threshold hysteresis @jseidl (#401)
  • Keep-only presence sensors, for those pesky flappy sensors such as mmwave @jseidl (#398)
  • Make schemas tolerant to extra keys @jseidl (#400)
  • Modernize and expand tests @jseidl (#380)

🐛 Bug Fixes

  • Fixing broken logic on unit of measurement popularity contest @jseidl (#399)
  • Fix unit of measurement resolution @jseidl (#393)
  • Fixing #375 and changes to the threshold sensor on 2024.7 @jseidl (#378)

🧰 Maintenance

  • Docs upgrade on README.md @jseidl (#404)
  • Fixing threshold sensor test to pass on GitHub and minor version bumps + consolidation of latest releases @jseidl (#397)

Contributors

bjeanes, jseidl, and tbrasser
Loading

4.0.1

04 Jul 10:43
@release-drafter release-drafter
4.0.1
2079727

Choose a tag to compare

View all tags
4.0.1

This is a small hotfix to resolve an issue with the threshold sensor due a change on Home Assistant 2024.7 and an issue with adjusting color temperature in the light groups (#377).

Changes

Contributors

dependabot
Loading

4.0.0

06 Jun 20:49
@release-drafter release-drafter
4.0.0
367b887

Choose a tag to compare

View all tags
4.0.0

Hey folks! This is a BIG BOI release! I've went through our feature request list and picked the top ones and implemented almost all of them! I've mostly re-written most of the code to remove complexity and improve stability.

Due to configuration schema changes this release can break your ability to configure existing areas. Removing the entry and adding it back will restore back to normal.

Check them new changes below:

  • Floor meta areas: You can now have floors as meta areas just like the Interior/Exterior ones!
  • Config UI revamp: Options have now a menu where you can hop in, change one specific setting and hop out without going through the full flow "wizard" like before. Options are now with better descriptions and organized.
  • Goodbye dark entity! Dark entity has been renamed to "Area Light Sensor" as most people used a sort of light binary sensor for that. This change now requires this entity to be a binary sensor and also be of device class light. This helps filtering the select for this entity to only light binary sensors and the sun sensor.
  • New entity ids, unique ids and names. This update brings generated unique ids and entity ids which used to be derived from the name. This enables Magic Areas to go full internationalized meaning you can now have the entities in your own language! Current translations available are: US English, Latin Spanish and Brazilian Portuguese (translated by a human - me) and German and Dutch (auto-translated). Let me know if you'd like Magic Areas in your own language and it's not on this list. I can provide automatically translated versions and you can help make it better! Names are no longer "Area {XYZ} ({Area Name})" and instead will show up as "{Area Name} {XYZ}" which is compatible with Homekit and most smart home platforms. Unfortunately this means you might have to update your UI or automations if you reference the old entity ids.
  • Default timescale for most options is now minutes! The most requested feature is now available, there's a migration function that will automatically convert your settings to minutes (if over a minute, if less, it will set to the defaults).
  • Device class selection for aggregate sensors and health sensors! You can now choose which device classes gets sensors created for aggregates and which device classes are considered for health sensors!
  • Area State icons are deprecated as an option and are now pulled from the area's icon in Home Assistant!
  • Calculated light: You can now have aggregates generate a binary sensor of light device class according to a set point on the aggregate illuminance for an area. This is a Threshold sensor, if you're familiar with them. Hysteresis is currently not configurable but coming in a future patch (probably). This is especially useful for the Exterior meta area so you can use as an Area light sensor for your interior areas.
  • Light groups now only changes lights that are one. If you change a light groups color, brightness, color temp (literally anything), it will forward the changes only to lights that are one! Isn't that dope? If no lights are on then it will act normally and turn on all the lights in the group. This feature was originally brought in by @caphm but only now I had the chance to port it back into the codebase. @caphm my man, you're awesome, thanks a lot for your work!
  • Config version and migrations: I've finally figured out how to handle config entry migration so hopefully further possibly breaking changes can be handled automatically.
  • Lots of things you won't see or care: The codebase has been massively revamped. Magic Areas grew from a small proof-of-concept code and new features were piled in a not-so-solid base. Most of the code has been completely re-written and (to my feel) is much faster and stable.

Thanks once again to all contributors who were part of the beta and all the ones who contribute to Magic Areas. You folks are the best!

Hope y'all like the new version, let me know your thoughts on our Discord! If anything looks broken, try first deleting and re-creating the Magic Area. If it is still broken, cut me an issue or come chat on Discord!

🐛 Bugfixes

  • Update magic.py to use the async_get directly @pinkfish (#330) (this is the one that broke with 2024.6)
  • Secondary state tracking now considers ABOVE_HORIZON to support sun.sun @jseidl (#346)

🚀 Features

  • Adding floors as meta area types @jseidl (#342)
  • Health sensor configurable device classes @jseidl (#356)
  • Change default timescale and added migration script @jseidl (#355)
  • Light groups now only act on lights that are on, if there are any @jseidl (#354)
  • Spanish translation @jseidl (#352)
  • Calculated area light @jseidl (#350)
  • Configurable aggregate device class @jseidl (#349)
  • Climate and Media player groups control switches @jseidl (#344)
  • Simplify config flow options and add better descriptions and helper texts @jseidl (#343)
  • Use area icon instead of configuration value @jseidl (#341)

All other changes (mostly related to dev environment, CI/CD, testing and version bumps)

Contributors

jseidl, pinkfish, and 2 other contributors
Loading

3.1.1

29 Feb 23:42
@release-drafter release-drafter
3.1.1
f535dcd
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
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

  • Adding back feature enable check to climate groups @jseidl (#321)

Other Changes

  • Adding Area default values for parameters that will be required in future versions @jseidl (#322)
  • updating info.md for hacs @jseidl (#320)

Contributors

jseidl and tbrasser
Loading