When my wife and i are home, we keep getting an update to say we are home which triggers my NR automation to open the gate and switch the driveway lights on, i have removed the app and reloaded it and removed all the old devices and it still does it! only started since 106. but i dont have a backup that far back to go back there and not really wanting to start again and copy all my code!
Put a condition in your automation that the trigger from state must not be “home”.
That defeats the point of the automation as i/wife get into the home zone it runs the automation. But as we are stuck at home now, this is getting very annoying! But as the notifications dont work now either i have to keep looking at the gate to see if it is open!
No this doesn’t defeat the point of the automation. It’s just an enhancement, that it only triggers if it changed to home
and the previous state was not home
, which will solve your problem.
Which I think you could do in your trigger as well (from: not_home) if you don’t use other named zones close by.
I do have zones close by. But this is kinda counter intuitive of something that was working for the last 6 months and been invaluable to now not able to use at all!!! I know what you guys are saying and have that similar config for other things in my house, but that will not solve the issue here! as soon as i leave the zone it says i am away and when i get to work it says work, so no problems there, i get home it says home and then opens the gate and lights if after sunset. but while i’m in the house it still wants to tell me i’m home and then opens the gate! i had this issue before we went to app companion 2.0 then once we went over it was flawless. now gone to …
Yeah it will.
There’s some sort of bug in the tracker that is changing the state home → home repeatedly, possibly because an attribute is updating. IDK. Others have reported it.
I’m guessing your trigger is only the state change to: home
, so add a condition like this
condition:
- condition: template
value_template: "{{ trigger.to_state.state != trigger.from_state.state }}"
And it should solve your problem.