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
Problem: when a (smartphone) device that is tracked by unifi addon is not connected to the unifi AP, and the HA is restarted. Then the device will be in state "Unavailable".
This is a problem if you use the device as tracker for state home or not_home.
I think the correct solution is to put the device into Away(as it is when simply disconnecting the smartphone from wifi), because if it is not found within the unifi controller, it should assume the device is away.
Home Assistant 0.108.6
Unifi Controller Addon 0.14.1
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening your first issue here! If you're reporting a 🐛 bug, please make sure you include steps to reproduce it. Also, logs, error messages and information about your hardware might be useful.
membersound
changed the title
Device in state Unkown after HA restart
Device in state 'Unavailable' after HA restart
Apr 19, 2020
The add on provides the Unifi Controller software itself. The device tracker integration is provided by Home Assistant, so you would need to log your issue there.
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
Problem: when a (smartphone) device that is tracked by unifi addon is not connected to the unifi AP, and the HA is restarted. Then the device will be in state "Unavailable".
This is a problem if you use the device as tracker for state
home
ornot_home
.I think the correct solution is to put the device into
Away
(as it is when simply disconnecting the smartphone from wifi), because if it is not found within the unifi controller, it should assume the device is away.Home Assistant 0.108.6
Unifi Controller Addon 0.14.1
The text was updated successfully, but these errors were encountered: