It appears after upgrading my Unifi Cloud Key to v2.0.24 which upgrades the network OS to v6.0.43, the integration breaks. From my understanding and observations on the network side, the ports for the controller change from 8443 to 443 & 80.
Attempting to reintegrate with the new ports either is futile as HomeAssistant says the integration already exists or HomeAssistant locks up while the integration is trying to be installed.
Got it, and yes, the full removal of the integration, port change to 443 during reinstall worked.
There’s still an issue where I was unable to change the port on the old integration as HA just froze when “Options” was clicked. Perhaps this is the bug that needs to be address so to prevent a full reinstall of the integration.
It is also possible to manually edit port in the .storage/core.config_entries file.
You can’t access options if the integration is not running and there is no option to re-configure the main service configuration from the GUI. I will look to remedy that in the future.
I updated the firmware for my cloudkey after reading this thread and I got a similar behavior (HA would never start due to Unifi errors). I then tried to do the port update by editing the config file and it seemed to work because HA started up fine with no more errors.
But then later I noticed that the Unifi gateway monitoring entities (firmware_upgradable, alerts, lan, vpn, etc.) never got re-created.
So I deleted the integration and re-installed it. But I end up with the same thing.
Maybe I don’t understand what a “local user” is. However, those were all working before and I could log in with the superadmin user I created on the controller in the old software.
Am I missing something to get those working again?
