Yeah same issue, on one of my instances at least. It had a lot of network issues after HA OS 11.0 upgrade.
I reverted to HA OS 10.5 with the following:
ha os update --version=10.5
That will cause a reboot. After that 11.0 will show as an update again, which I pressed “Skip” on, and then subscribed to potentially related GitHub issues like this one.
Thanks I also did the downgrade to get wireless up again. The only diagnosis I attempted was to remove and then readd the inform address which had no effect
Ive tried to installed the HA again with the Unifi controller on it.
Seems to work for now 
but i’ve got another issue now.
I want to adopt my AP’s but it keeps failing. Probably its assigned to the Unifi controller that i run on my pc.
Is there an walktrough to change this?
have you followed the configuration instructions and configured an inform address? are you running HAOS 11 or 11.1?
Eagerly awaiting an update to Unifi Controller 8.0.7, so I can replace my USG with the new UXG Lite 
Upgrades to this add-on are not automated. If you want this to happen sooner, you could open a PR like this one.
Hi all,
I decided to try and install the controller again and to my surprise it worked! Here are my details from the log:
6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
Add-on: UniFi Network Application
Manage your UniFi network using a web browser
-----------------------------------------------------------
Add-on version: 2.8.1
You are running the latest version of this add-on.
System: Home Assistant OS 11.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.11.3
Home Assistant Supervisor: 2023.11.3
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[08:22:29] INFO: Configuring timezone (Australia/Brisbane)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-unifi: starting
s6-rc: info: service init-unifi successfully started
s6-rc: info: service unifi: starting
s6-rc: info: service unifi successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[08:22:30] INFO: Now starting the UniFi Network Application...
[08:22:30] INFO: Note: No add-on specific logs beyond this point.
The issue I am having now though is it’s picking up a strange IP address of 172.30.33.1 as the Server IP in the controller… my raspberry PI is running an IP of 192.168.1.116 though and from reading this is some sort of internal networking interface for HomeAssistant? When I run an ifconfig from terminal I see that same IP:
[core-ssh hacs]$ ifconfig
eth0 Link encap:Ethernet HWaddr 02:42:AC:1E:21:01
inet addr:172.30.33.1 Bcast:172.30.33.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:425460 errors:0 dropped:0 overruns:0 frame:0
TX packets:1274 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:121463941 (115.8 MiB) TX bytes:704421 (687.9 KiB)
Has anyone had this issue before? I had a look in /config which is a symlink to /homeassistant and cannot find any config files for the unifi at all. That IP is preventing me from adopting any of my AP’s. I tried to restore a backup from my windows controller I am currently using however the AP wouldn’t adopt so I factory reset the AP, it can see it and when I try and adopt, the AP is definitely receiving that weird 172. IP:
Thu Nov 23 22:37:21 2023 daemon.err mcad: mcad[1175]: ace_reporter.reporter_fail(): Timeout (http://172.30.33.2:8080/inform)
Thu Nov 23 22:37:21 2023 daemon.err mcad: mcad[1175]: ace_reporter.reporter_fail(): initial contact failed #1, url=http://172.30.33.2:8080/inform, rc=4
Hi all,
I have the Network Application 7.5.187 running on a Home Assistant yellow without any faults. Installation was no problem. Before I had it on a Raspi. Now I want to update the application to version 8.0.7. But I actually do not really know how to do. On the raspi i could do it via SSH. Now I can download the new release, via the interface, but I do not know what to do with it. Do I simply have to wait for an update of the add.-on, as statet further up in this trheadP
Same here. I unfortunately am not well trained in the whole Github process. I´m therefore not sure how I can help with the building of the new solution.
On a sidenote, if someone knows a good site how to learn Github merges / pulls ,etc so I can contribute more in the future, would be appreciated!
Yes. Or open a PR as mentioned above.
OK I prepared a pull request to pull in the update. I think I did it correct. Just see an error on incorrect label, but maybe that is something that Frenck updates once he approves it.
Update to version 8.0.7 by renewoensdregt · Pull Request #466 · hassio-addons/addon-unifi · GitHub
If anything else is missing, happy to work it out!
Please verify the upgraded version works before opening the PR.
The upgraded version works fine and smooth. Thanks for providiing.
Hi - I am trying to migrate from an existing controller (on Windows) to the Home Assistant add-on (running on a Pi4). I have setup the HA version and it sems to be working fine (on 8.07) and backed up the Win version (also 8.07). However when I try to restore the backup to the HA version - it just says “upload failed”. Any ideas please?
I used this tutorial:
How to Migrate Unifi Controller - The Easiest Way (lazyadmin.nl)
Maibe it can help?
thanks - when I try to upload the backup file I get the same error message which says
“There was an error uploading the backup file.”
It seems to be uploading to the Pi is the issue - could this be related to the IP address or remote access?
My home assisstant is completely local at the moment
I have sorted it, I needed to connect locally to the unifi controller rather than through the ui website. Worked first time when i did this.
Maybe you ask here:
ubiquiti - Deutsches Fan Forum (ubiquiti-networks-forum.de)
They are very helpful and fast. But in German. Maybe they will answer in English, too.
Heho
I running the unify 8.0.7 application on my HA Blue.
Is there a reason why some features from the announcement from ui are not available?
(Like wireguard)
Are they only available for the original devices or needs the addon to fake a newer device?
Features like this are often only available on the Dream Machines. I’m running a USG at home, don’t have the wire guard option. My Dream Machine at work does.
