Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unifi: wireless device_trackers delay in restore state on HA start / restart after upgrade to 0.103.3+ #30162

Closed
TazUk opened this issue Dec 23, 2019 · 3 comments · Fixed by #30276
Assignees

Comments

@TazUk
Copy link

TazUk commented Dec 23, 2019

Home Assistant release with the issue:
v0.103.3 and v0.103.4

Last working Home Assistant release (if known):
v0.102.3

Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 18.04 + Python 3.7.5 venv
Unifi local controller hosted on Cloud Key Gen2+ firmware 1.1.6 Controller 5.12.35 (unchanged for the circumstances described).

Integration:
Unifi Controller (via Integrations).
Settings:

  • Track network clients enabled
  • Include wired network clients enabled
  • Track network devices (Ubiquiti devices) enabled
    Consider home / time to away: 120 seconds

Description of problem:
On v0.102.3 and prior versions with this integration (and same controller versions) device trackers immediately restored their previous state after restart.
On upgrading to v0.103.3 (and subsequently to v0.103.4) wireless device trackers that were 'not_home' were briefly toggled to 'home'.
E.g. the unifi device_tracker for my car was set to home on system start this morning as I upgraded remotely from 27 miles away. The state corrected after 7 minutes.

The impact of this is that it triggers presence based automations in the system.

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

N/A 

Traceback (if applicable):


Additional information:

@probot-home-assistant
Copy link

Hey there @Kane610, mind taking a look at this issue as its been labeled with a integration (unifi) you are listed as a codeowner for? Thanks!

@geekofweek
Copy link
Contributor

I've had the same issue on two different installs since 0.103

@Kane610
Copy link
Member

Kane610 commented Dec 31, 2019

Fix will be a part of 0.103.6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants