Hi all,
I have a single Person with a single device_tracker - an Eero router. When I turn my phone off I see sensor state_changed events that my connection list has changed, but my Person entity state remains home. I have the Eero integration consider_home interval set to one minute, and I wait considerably longer. Can anyone explain?
because a tracker simply remembers its last position, so, when you turn it off, it’s not updated anymore…
I turned my phone off. Doesn’t the router tracker determine whether I am home by looking at whether the phone is connected, so when it’s off shouldn’t that register as unconnected and thus set the person state? What am I missing here?
Check your person settings, a common cause for a person entity being shown as “home” when they shouldn’t be is that the “Allow login” setting is on and the person’s user is logged in on some device in the house. If that device is also has a device_tracker entity, it will affect the person entity’s state. Any device that you don’t normally carry with you when you leave should not be signed in under the user account linked to your person entity.
If the device_tracker entity for your phone from Eero is switching states when the phone is turned off, but your person entity’s state is not changing after 10 minutes, then the most likely source of the issue is what I have describe above.
Surely for your tracker to determine you are not home it needs to see you are elsewhere. Just not being connected to your router is not enough as suggested above. HA will just remember your last location.
That’s what i said 
That is how most trackers work. I don’t have an Eero router so I don’t know about it. I used to use an Netgear router as a tracker, but it was very slow to figure out my phone was no longer attached to it’s Wifi. I switched to using Ping and it works well. The only issue with it is that the tracker sensor is disabled by default so you have to enable it before it shows up as a tracker in your person settings.
GPS trackers actually look at your location, but binary trackers generally just look for a connection.
Are you guys sure you’re talking about the same thing as OP?
Yes, it should change the state of the device_tracker…
All of the stationary trackers I use update the device_tracker state when the connection is lost. Both my router-based and BLE beacon-based device_tracker entities are marked as not_home if they are turned off longer than the consider_home interval.
Whether it sets the person entity state depends on whether that device tracker entity is the only thing affecting the person. You cannot rely on the list seen in the Person settings if the “Allow login” setting is enabled.
Thank you all for the commentary. Since I am seeing events corresponding to my phone disconnecting and connecting from wifi I believe the Eero is reporting properly. So that implies that it’s the tracker for the Eero that’s not changing my home state. I’m going to have to leave it at that.
ideally you need to have all 3 location trackers connected to a person from their phone:
BLE
GPS
Router
The router takes about 10 minutes to change to not being present after the last wifi connection. Only once all of those are showing as not connected, then the person shows as not home. As soon as any one of them gets a connection to the person being near the home, then the person changes to being home. I have all three set up as well as a second router connection (for a total of four). It was a hassle to get it working properly for both an android and an iphone, but once set up properly, it is pretty much bulletproof.
I very much prefer it to not change to the person not being home until all three of the above are in agreement, but showing the person as changing back to being home as soon as any of them connect, because you don’t want lights turning off etc while you are still home - but you do want them to turn on the second you arrive 
That’s why a I said this “as suggested above”
That really depends on how the network gear is configured.
Some routers have arp tineouts of just a couple of minutes and others can have hours.
On more advanced network gear it can be user defined.
Typically there are two timeout settings.
One for when state change from active to stale (which is the one you want to change) and one for when the stale device is deleted (on networks with many devices that come and go this can be used to conserve resources).
Thanks for the correction. Mine is about 15 minutes actually and is not settable as far as I can tell, I have all Omada class equipment. Also, a piece of hardware is identified by the Mac address by Omada, so 1. I have to make sure the mobile phone is configured in their WiFi settings to not change their Mac Address for that SSID; and 2. All IP addresses need to be static because whenever it appears on the network with a difference Mac Address then the router assigns it a different IP address. (Otherwise it’s like chasing a moving target to target to identify correct device for being on the network or not.)
Omada usually have a decent set of options, but sometimes the settings are hidden or can only be set through a CLI interface or similar obscure ways.
I do not know if this apply to your router, but point 2.2 is related to ARP timeouts and it starts with “Using the CLI”.
https://www.tp-link.com/us/configuration-guides/configuring_arp/?configurationId=18200#_idTextAnchor000