Core: iOS device tracker showing as not_home after HA restart

Created on 24 Nov 2018  路  13Comments  路  Source: home-assistant/core

Home Assistant release with the issue:

0.83.0b0

Last working Home Assistant release (if known):
0.82 (Not really sure)

Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

iOS device_tracker

Description of problem:
After restarting HA the iOS device tracker state is always not_home (even when at home) and have to be manually update it from the iOS app for it to start registering properly again.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

ios:
Home Assistant iOS integration

Traceback (if applicable):


Additional information:
Was told is a server side issue.

ios

All 13 comments

The device_tracker shows the same behavior in the iOS app 1.2 and 1.5 beta.

Looks like the issue also appears with owntracks. After the update to 0.83.0 (Release) and restarting hass, my devices show up as "not home" untill owntracks sends a new update down mqtt
Update: Same behaviour in 0.83.1

@arsaboo mentioned this bug affects geofency too.

This seems to be the case with all device trackers after 0.83, all of them will reset to away state until it gets another update.

Cross-post from Discord user phnx:

the entire state machine is getting overhauled in 0.84
should probably ask some of these folks to test the beta

If anyone can give the beta a shot and confirm, that would be helpful.

Not fixed in beta, still marks me as not_home after a restart as before.

Not fixed in beta, still marks me as not_home after a restart as before.

was worth a shot, thanks for the try.
~phnx

@jjlawren pretty confident that is what did it. Reverted the change and did a few test restarts, issue isn't there anymore. Nice find.

Glad to hear that 馃帀馃帀馃帀

Can you just test by changing the condition to and from or?

@arsaboo I did a quick test with a single restart and it seemed to work. I need to space out my restarts or it doesn't always restore states properly if I do them back to back.

update: that seems to do the trick. Few more restarts and it is persisting the state.

Fixed on 0.84.0b3 with #19133

Was this page helpful?
0 / 5 - 0 ratings