So, got it going finally, went to bed way too late, but I was a happy man. Only to discover this morning, the controller wasn’t accessible anymore. Reboot of the Home Assistant, nada. Eventually I ended up with a fresh image of the Home Assistant install, restored my snapshot from several weeks ago and then installed the addon.
All was running, but I had to configure my MQTT IP again. Changed the IP in config.yaml and restarted Home Assistant for my changes to take effect. Now the controller is not accessible again…
Stopped the mosquito addon, now the controller is accessible. Looking in the addon configs of both, I don’t see any conflicting ports?
I stopped the Mosquitto addon, but later started it again. Due to networking magic, both addons are running succesfully now…
Or was I too impatient, does the Unifi addon really take ~20 minutes or longer to start?
Yeah, I’ve had a couple of reboots now (fixing bugs after recovery from snapshot), and the addon is booting just fine. Als MQTT working as expected. Anyway, it is fixed and thanks for your help René.
I currently run this add-on through the hassio supervisor on an Rpi 3B+. I just ordered the Rpi 4B and was wondering how I would migrate? I know I have to create a snapshot on the Rpi 3, put it in the samba share of the Rpi4 backup folder and reboot de Rpi4 and restore the snapshot. But since I noticed that unifi has separate directories inside the backup folder, should I also transfer those or are those included in the snapshot?
The snapshot will backup all the folders inside the backup folder. On Top it will also backup the content of your Addon Container. So if you restore, it should be back to the previous state.
EDIT Sorry… big mistake. The Backup WILL NOT backup your BACKUP Folder at all.
Hi @frenck,
First of all, thanks for this super easy way of installing the UniFi Controller.
I am running it on a Pi3+ and seems to work perfect. Good to know for all though, is that the initial startup takes a little longer than you’d might expect, since the ‘open GUI link’ is shown before it’s ready for use. You can see this in the log.
No problem in daily life, but since I am a newbie I thought it didn’t work. Because I was short on time, I therefor decided to install the Windows controller. So, give it a minute to start
Anyway. Now I’d like to migrate to your add-on but unfortunately bump into the same (version) issue as @HillNet. As a result of that and without the intention to put any pressure or what soever, I am curious if you have an indication on releasing the new version
Is it posible to update de controler to version 5.13.29 (Build: atag_5.13.29_13635)? I need this version to restore the configuration from an other controller.
Or does anybody knows how to migrate the USG & AP form one controller to the other
Migrating only works if the controllers are the same version. Also the advanced adoption failed when I tried to adopt them to an older controller version. The only thing that you can do to “adopt them” to an older version is to factory reset them and connect them to the older version controller.
But before you do, rebuild your config manually on the older version controller. This way you know for sure the used features are available in both versions of the controller and once adopted, you have a working network without the (time)pressure of rebuilding
Based on the indication of @frenck, I decide what to do because one of the things I am missing while waiting is not having presence-data. I use it within several automations.
This is a common problem for many.
On the Home Assistant side you install an Integration which is a bit of software that adds a function to Home Assistant. In this case the interface to a Unifi controller.
This Unifi controller can be a piece of hardware from Ubiquiti. It can be a piece of Ubiquiti software you install on a different server.
The Addon is the Unifi controller software neatly packaged so it can be installed from Home Assistant.
If you uninstall the Addon you will remove the Ubiquiti software but the HA integration remains and will keep its config but will no longer have someone to connect to.
If you remove the integration, the Addon keeps on working happily and you can keep on using it as a Unifi controller. When you add the integration again all the devices and entities will be created inside HA from fresh.
When you remove an integration with the purpose to clean things up it is usually a good idea to restart home assistant before adding it again to be sure all the old is flushed away.
This is true for all integrations that works with an Addon.
