2019-06-19 08:09:17 INFO (SyncWorker_21) [homeassistant.loader] Loaded **unifi** from homeassistant.components. **unifi**
2019-06-19 08:09:17 INFO (MainThread) [homeassistant.setup] Setting up **unifi**
2019-06-19 08:09:17 INFO (MainThread) [homeassistant.setup] Setup of domain **unifi** took 0.0 seconds.
Are you using a non-standard port in your configuration (9443)?
Note that I did not delete my known_devices.yaml - only removed the Owntracks entries from it after upgrading per the release notes. Unifi was not one of the migrated device tracker platforms for the release.
no new devices are being added the known_devices.yaml… i have restored my old known_devices.yaml, but everything of state router is set to “not_home” which isn’t true.
also i changed the password in the config to make sure it fact working, changing the password showed the error logging in… so think this quite broken.
@oriolism can you confirm that you have stuff that is both marked as “home” and “not_home” when you filter the states by type “router”
Yes, my iPhone is marked as not_home by the router and at Work by gps. Also my iPad is marked as home which is true. I had issues to load HA ui on version 0.94 and i ended deleting core.device_registry, core.entity_registry and core.restore_state to fix that problem but im not sure if that also fix the unifi problem.
I’d be willing to bet that your entity_id’s all changed. Look in your states page at your devices and see if you have new set of devices with other names.
Nevermind. Just read that it’s not creating new devices for you.
Have you tried stripping your config back to the bare miminum?
Well, you could slowly add items back in until it doesn’t work. Might take a few minutes but then you could narrow down the issue. Then decide if it’s a bug or not.