Alright, then it should be working. Can you screenshot the entity_id please just for verification. Because at this point, that’s the only possibility as to why this isn’t working. I guess the other possibility is that the automation is turned off.
this may help ?
famiglia:
name: Famiglia
entities:
- person.demetrio
- person.nada
- person.chiara
Of course automation is enabled
Then it should be working. Everything you’ve posted is correct and verified. It should trigger when the group naturally changes from not_home to home.
I’ll switch back to entity group.famiglia and give it another try
having the same issue. it was working fine until the update to 2022.3.5. I added a guest person as a device tracker controlled by an input boolean. Both the other person entities are home
, but when i toggle the guest to home
, the entire group changes to home, when i set the guest person to away
, the entire group goes to away even though the other two person entities show home. See example here:
poking around some more, i was looking at the history of the person
entity for myself and i see that it has status of home but both in green and in blue. does this mean that HA thinks these are different statuses?
posted this in the other thread as well, but just in case someone is monitoring this one instead of the other…
Was digging a bit more and also noticed that in my logbook, the values for home
are sometimes different:
I think that may be the crux of the issue. There are only 2 trackers assigned to my person, one is the IOS cloud the other is the HA App. It looks like both of the trackers can use home
value with lower case h
and also Home
with upper case H
. not sure if that would cause an issue or not, but assuming the compare done in the group may be case sensitive.
Did you ever find a solution for this? I am on version 2022.5.5 and I’m having the same issue. When someone arrives home, they aren’t triggering the automation.
alias: Alarm - Disarm for Family
description: Testing
trigger:
- platform: zone
entity_id: group.some_family
zone: zone.home
event: enter
condition: []
action:
- service: alarm_control_panel.alarm_disarm
data: {}
target:
entity_id: alarm_control_panel.alarmo
mode: single
Same issue here. Pretty basic functionality of using a group to track family presence and trigger automations. I’m pretty new at HA and very exited but now surpised to see such a basic feature not working. Must be a bug. I saw it working after setting up the group but then it gave up and even configuring everything from scratch does not bring back the automation to trigger again.
It’s not a bug. Zone triggers only work with gps entities. A group does not have gps coordinates.
If you’re looking for him/away functionality for a group, use a state trigger with the states home and not_home.
It works!
Why in hell is the group status in the dashboard showing ‘Away’ and if you check the developer tools it says ‘not_home’. Triggering on ‘not_home’ works. And ‘Home’ and ‘home’ was another issue. I try to tiggered 'Home" because the dashboard was showing this but the real status was in lower cases.
Petro, thanks for the hint. Can you explain why the Group is showing Away in dashboard but not_home in state?
All states shown in the UI are translated to your language.
I’ve had the same problem. Took me a while to figure out the actual stat was ‘not_home’ rather than the ‘away’ shown in the history.
‘Not_home’ and ‘away’ are both English? Mine is set to English
All states under the hood are English. Away is the translation used when your language is set to English. For other languages, it’s whatever Away is in the selected language.
Than how can you know what the different state names are before translation to UI language? You only see current state when looking at states and the translated states in history.
developer tools → states page has all unaltered states.
At the risk of sounding like a total noob but I only see the ‘current’ state in the states page.
If I’m at home, the state is home. Where can I find that the other state is not_home without changing the current state?
You can’t, you can only see current states.