This is an automated archive made by the Lemmit Bot.

The original was posted on /r/homeassistant by /u/theseidlmeister on 2024-09-07 17:20:33+00:00.

Hi folks! I just launched a new release of my custom component Magic Areas.

This update adds a new setting under “Presence Tracking” options which allows you to select entities which will be ignored until the area is occupied. This effectively solves the hassle of mmWave sensors triggering presence in an area because the wind blew the curtains or a fan nearby disturbed it. I myself had a couple of rooms where I’ve faced the “mmWave sensor seeing through walls” issue which I no longer do. Folks using BLE trackers will also benefit from this setting as well.

Another feature is that your “Calculated Light” threshold sensor (a binary sensor of light device class that triggers when your overall area illuminance goes over a certain threshold) now has configurable hysteresis. This will possibly allow people to do a closed-loop on interior lights / luminance per area.

There are a couple of bug fixes regarding unit_of_measurement resolution on aggregates and some minor stuff. If you’re using HACS then you can update/install version 4.1.0 from it, otherwise you can download from the GitHub repository.

If you’re not familiar with the integration:

Magic Areas is a custom component for Home Assistant that magically makes sense of the devices and entities in your areas so you don’t have to! It’s main purpose is tracking presence in your Home Assistant’s areas but in reality it’s much, much more than that.

If you’re interested on learning more about it, hop on the GitHub page!