Areas no longer suck! Magic Areas will bring your Areas to life with area presence state tracking, aggregations and automations!

Just installed and really appreciate the the feature set. My query is for a room with multiple sensors - my kitchen has Aqara FP1, Aqara and Sonoff PIRs - as the ‘Clear timeout’ varies from an acceptable 60 seconds to a huge 300 seconds can I set ‘Clear timeout’ to override all sensors in a room?

The same problem. Maybe I’m doing something wrong. I done ctrl+F5 but it didn’t showed up.
Edit:
Let me answer to my own question. Read documentation.
To activate magic areas after install integration you have to add line in configuration.yaml

magic_areas:

and integration will show up on restart.

Setting/Integrations/Magic Areas /Select the area you require /Configure

@jseidl The timeout was set to 60 in the config (now 30). Where could the 300 timeout coming from that overrides the 60?

** Secondary menu for the area gives these options and a bunch more. 1) RFM 2) RFM when not tired

I am wanting to fully uninstall and remove magic areas from my HA. In HACS, when I click the 3 dots and choose Remove, I get a pop up warning: The Magic Areas integration is configured or ignored, you need to delete the configuration for it before removing it from HACS.
I can choose to IGNORE or Navigate to the integrations page.
Does anyone know the proper steps to fully remove this and not have it pop back up after a reboot?

Can’t help with the preceding post. But I’m wondering if anyone else has been getting an invalid config notification since updating to HA Core 2023.1

Yes , got this log message after install 2023.1
Dieser Fehler wurde von einer benutzerdefinierten Integration verursacht

Logger: homeassistant.setup
Source: custom_components/magic_areas/init.py:67
Integration: Magic Areas (documentation, issues)
First occurred: 08:38:41 (1 occurrences)
Last logged: 08:38:41

Error during setup of component magic_areas
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/setup.py”, line 253, in _async_setup_component
result = await task
File “/config/custom_components/magic_areas/init.py”, line 67, in async_setup
AreaEntry(
TypeError: AreaEntry.init() missing 1 required positional argument: ‘aliases’

This was due the area object changing in the new release, a new MA release is coming out this weekend!

I do not check this thread often so if you folks still need help please join our discord server at Magic Areas!

1 Like

Hey Bart, yes unfortunately uninstalling MA is a bit of a hassle.

Please follow the steps on the wiki to fully uninstall it.

This is a fantastic addition, has made what was a complex lighting setup with over 50 bulbs and 20+ sensors much simpler now to get the bedroom working to my wife’s satisfaction :blush:

Question on determining what presence sensor is driving overall state, I can see in attributes there is a list of the sensors but no indication of the state (yes I see the last updated is there) in some cases I have errant sensor s and working out which one(s) is causing the state is time consuming manually. Before I go and simply hardcode each sensor into an Lovelace card I’m wondering has any looked into a template to extrapolate those sensors form the attributes and show the status f each?

I assume it’s a matter of iterating through that list and my template skills are not yet up for this, will look into working it out but thought this would be a common ask yet cannot find anyone else asking the same. So good chance I’ve missed this capability if so anyone who can kindly point it out would be appreciated.

Hey Andrew, if you expand the attributes of the “Area State” sensor it should tell you the last_active_sensor which is the one who last triggered the presence.

image

Please join our Discord if you have further questions! It’s easier for me to keep track there than here.

@jseidl: Hallo Jan, I just became aware of this integration. Before I go thru the installation process, maybe you can tell me if I could resolve the following scenario with it:
In each room I have a window sensor (e.g. binary_sensor.gaste_wc) and an EVE Thermostat (not in HA yet but soon). Is there a way to create a magic area with the window sensors and couple them with the corresponding thermostat, so that I can close the thermostat when the window in that room opens and v.v.?

Many thank in advance!

Regards,
Joop

Yhanks Jan actually saw that about an hour after I posted much appreciated for the response