this post was submitted on 25 Jan 2025
21 points (100.0% liked)
homeassistant
12647 readers
94 users here now
Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I get what you mean and yea I don't think you can easily use groups for that.
Zones have a several things going on.
In no particular order:
Making a mock entity for #1 is easy enough, a helper number thing whose state is the sum of the group members' states.
The other stuff is more complicated.
#2... Might be easier to add the different zones as multiple triggers, which might be a pain to manage. But then, I assume you'd also want to ignore whenever someone moves between zones in that same group.
#3... idk, if it's just for displaying purposes in that person's "badge" thing, just use the same display name for all zones in group. If it's for use in an automation, then you probably need to duplicate everything again.
Might be easier to implement polygonal zones than group normal ones.
I think nodered might already have that geofencing feature.
There's a bit of discussion in here: https://github.com/home-assistant/architecture/discussions/1014
In the current version of Home Assistant, if a person is in two overlapping zones, what happens? It's possible to be in that state today.
I suppose it doesn't really matter though. I've named all my home zones similarly: home1, home2, etc. It would be easy enough to check for a zone where the object_id starts with "home"
Good question, I'd guess it would be the closest to the center of whichever zone.
I haven't tested them, but if they work, it'd be easier to use non circular zones than deal with multiple overlapping ones.