Closed steve28 closed 5 years ago
This may be related - though I do not have the state restoration problem. I have been experiencing anomalous device tracker behavior as well since updating to 83.2. I have been using Owntracks (+ BT beacons) and Ping also on Ubuntu (Python virtual env, no Docker). If both Owntracks and Ping report I am not_home then I am not. If either Owntracks or Ping report I am home my status is home. The arrangement has worked reliably for me for over a year.
Since updating to 83.2, my Owntracks status bounces from home to not_home quite a bit more when my actual location is unchanged. The only change in my yaml is my moving owntracks configuration from under "device_tracker:" to "owntracks:". (Without this configuration change, ver 83.2 will not start but does not generate an error.) Ping also seems less "solid".
I've also tried duplicating some of the device tracker options (consider_home, interval_seconds, etc.) under "owntracks:" since I didn't know if owntracks would pick them up anymore in the new configuration, but no luck.
Same issue here, I downgraded to 0.82.1 because owntracks is unusable. But ios app tracker has the same issue. Maybe there's some relationship
This same issue happens with the Geofency plugin as well and has been for a while.
Yes, this has been reported and currently being investigated. Many states are not being restored. Hopefully, it will be fixed in the next release.
Having the same problem on a MQTT Device tracker I have setup though Monitor script on a Pi Zero.
Related to #18662
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.
I just installed 0.84.0b1 and it still occurs. All device_tracker entities are set to not_home
on restart.
This issue is fixed and can be closed now.
Home Assistant release with the issue:
0.83.2
Last working Home Assistant release (if known):
0.82.x (latest in the 0.82 series)
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on Ubuntu 18.04
Component/platform:
device_tracker, maybe recorer https://www.home-assistant.io/components/device_tracker/ https://www.home-assistant.io/components/recorder/
Description of problem:
Upon restart of Home Assistant, my iOS device gets marked as not_home. This occurs every restart since updating to 0.83.x. I have deleted the database file thinking that it could have been corrupted, but that did not help. As you can see from the log below, it starts out with an old state of
None
, then gets updated tohome
then 7 seconds later, it updates tonot_home
. This is 100% reproducible for me.Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information:
Here is a log of what happens on restart (filtered to show entries related to my phone
steves_iphone_x
: