To make this clear: this was always a problem and is not related to the new GUI-version.
As you can see in the screenshots:
10:00:50 - The first indication, that Elvis (seanpixel3a) has left the building through loss of WiFi-connection in the HA-app
10:01:10 - The Fritzbox detects loss of connection
10:03:56 - The HA-app detects, that Elvis has left the Home zone
10:09:36 - The HA Fritzbox integration finally realizes, that the fritzbox wasn’t joking, when it reported “device offline” MORE THEN EIGHT MINUTES AGO!!
That is indeed interesting!
I’m using the fritzbox 3490, with fritzos 7.12 (nothing newer available), but since the fritzbox is pretty fast in detecting “away” and it only takes ages for HA to realize it, I doubt, the hard- and firmware-version play a role. But who knows,…
I did recognize this behaviour aswell and tried to work around it as much as I could.
Now with the updated integration options to change consider_home has been removed introducing much unwanted behaviour in my automations.
Currently if my Netatmo Outdoor Camera sees a person and within a given time frame a device disappears from the Wifi, it is assumed that that person has left. In this scenario I always needed to set a quite high time frame for it to work consistently (i.e. I check when the device drops out of the Wifi, if a movement has been detected at the front door in the last 15 Minutes!). This was a setting that worked together with consider_home set to 60s
On the other side, with the new integration, I now have my Android device dropping from Wifi, when I am not using it to often. This now triggers the good night automations, as home assistant considers me asleep (usually I enter flight mode at night), although I just havent touched the phone for a while.
Would be nice to
a) have consistent timing in the different usecases
b) have settings to tweak the values as required.
To a avoid these false “away” states when the phone drops of the wifi, I am using two device_trackers combined in a person entity. One is network based (fritz) and one gps based (companion app with zone tracking). They will never both be wrong at the same time.
Will the GPS tracking be neutral to the battery, if Google Tracking is activated anyway?
Edit: Admittedly, this does not belong specifically into this thread, using also the GPS based sensor will stop the person from being reported not_home, if the wifi device tracker drops out. In my use case this will prevent the detection of entering flight mode, as the person will remain home. I do want to get/build a reliant bed occupancy sensor to get around this problem completely, but did not yet get to it, however the proposed addition only benefits partly.
With the old integration I did not experience the Wifi drop outs and was consistently reported home, if Wifi was turned on, even if the phone was not being used and entered deep sleep.
To detect sleep mode I use a combination of two android sensors: “is charging” plus “do not disturb”.
In my life both are only and always true if I’m in bed.
DnD can be activated by turning the phone over.
But I heard this is not possible on iOS.
Any tested the latest HA version. The LAG i had before with the Dect devices is complete gone. Light bulbs switch direct, status is almost direct. Look like the problem with the LAG is gone. Using HA 2025.2.5
