Unifi controller 5.10.12 breaks with home assistant device tracker?

mzac · February 7, 2019, 2:36am

I just updated my Unifi controller to 5.10.12 and it seems that now the device tracker with Unifi is broken. Can anyone else confirm? I am also seeing errors in the unifi log file:

[21:33:52,878] INFO api - [api] api.err.Invalid: /api/login

mzac · February 7, 2019, 3:09am

Looks like there is a fix but it hasn’t made it into the Home Assistant release yet…

github.com/home-assistant/core

update to pyunifi 2.16

home-assistant:dev ← finish06:pyunifi_version_update

opened 02:16AM - 13 Jan 19 UTC

finish06

+3 -3

## Description: **Related issue (if applicable):** fixes #20027 **Pull …request in [home-assistant.io](https://github.com/home-assistant/home-assistant.io) with documentation (if applicable):** home-assistant/home-assistant.io#<home-assistant.io PR number goes here> ## Example entry for `configuration.yaml` (if applicable): ```yaml ``` ## Checklist: - [x] The code change is tested and works locally. - [ ] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass** - [x] There is no commented out code in this PR. If user exposed functionality or configuration variables are added/changed: - [x] Documentation added/updated in [home-assistant.io](https://github.com/home-assistant/home-assistant.io) If the code communicates with devices, web services, or third-party tools: - [x] New dependencies have been added to the `REQUIREMENTS` variable ([example][ex-requir]). - [x] New dependencies are only imported inside functions that use them ([example][ex-import]). - [x] New or updated dependencies have been added to `requirements_all.txt` by running `script/gen_requirements_all.py`. - [x] New files were added to `.coveragerc`. If the code does not interact with devices: - [ ] Tests have been added to verify that the new code works. [ex-requir]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard.py#L14 [ex-import]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/keyboard.py#L54

gbboy · February 7, 2019, 3:51am

That fix was for 5.10.5 on HA 86.x . Haven’t upgraded my controller yet to 5.10.12 to see if I also get that issue. Can you confirm what version of HA you are using?

mzac · February 7, 2019, 1:38pm

I am running HA 0.86.4. I tried loading in the unifi.py into the custom components but it didn’t seem to work, ie I’m not seeing my devices being tracked. However, I am no longer getting the api login errors on my unifi controller.

However, checking the logs on my unifi controller, I don’t see the unifi user logging in since I updated last night

brettyj · February 12, 2019, 6:33pm

Can confirm this is a bug - I’ve upgraded unifi and HASS won’t even start until I comment out the unifi section of my config.

gbboy · February 12, 2019, 9:44pm

I just updated the controller, I’m running docker 87.1 with 5.10.12 without any login issues. Can see the HA account logon in the event logs also. What installation method are you both running?

mzac · February 14, 2019, 1:15am

I’m running HassOS on a Raspberry Pi 3 running HA 0.87.1 as well.

My Unifi controller is running on Raspbian on another Pi 3.

tom_l · February 14, 2019, 1:29am

v5.10.17 was released today. Might be worth a try.

mzac · February 14, 2019, 1:36am

I installed it this afternoon, no change…

gbboy · February 14, 2019, 6:43am

Definitely seems like an issue with your hassOS install and the dependency not correctly using pyunifi 2.16. I suggest removing and updating that. No issues with .17 and latest uck firmware either.

mzac · February 15, 2019, 2:04am

Suggestions on how to update pyunifi on HASSos on a Pi?

hopkins35 · February 18, 2019, 10:19am

This is also happening to me with Unifi controller versions 5.10.12, 5.10.17 and 5.10.19 but I’m using HA on a Windows box.

As with the OP I’m seeing successful logins from HA in the Unifi Controller event log but in HA was seeing " Failed to perform <function Controller._read at 0x08FCFED0> due to api.err.LoginRequired" every hour at 2 minutes past the hour followed by a sccessful login (according to the controller log) 10 minutes later which then correctly identifies my tracking status for the next hour.

My pyunifi version appears to be 2.16