You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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:
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:
The text was updated successfully, but these errors were encountered: