Interesting! I have the same. In the prior version it worked for me (I´m now also on the latest add-on version). I have a USG as device, not sure if @Neil_Brownlee has a different one that could cause the difference.
1 Like
I have this 
@martoq Fixed it by toggling the Threat management off, saving and then enabling again. After some time it started gathering again.
I have seen on the Unifi forum that this is a common issue and the solution above might not be lasting…
1 Like
Thank you!! That appears to have done the trick. I did require a reboot of Unifi Controller (I actually just rolled the reboot into an HA Update).
- Shutoff Threat Management
- Reboot UniFi Controller add-on
- Ensure traffic is being captured
- Turn threat management back on (assuming you’re using it)
Hi there
May I overlooked it in some changelogs, but where went the certfile/keyfile config?
Trying to add a config.gateway.json file to my controller, however I don’t seem to have the snapshotname_unify/data/unifi/data/sites/default/ directory within a partial backup, I only have snapshotname_unify/data/unifi/data/ does anyone know if this is the correct location?
So, I think I’ve worked out a slightly less stressful and hacky way to update the config.gateway.json file.
What I did was create a backup of the controller from with the UniFi Controller on Home Assistant.
I then restored this using a temporary UniFi Windows controller which exposes the full file system. Once restored I placed the config.gateway.json in the folder as described. Once correctly placed create a backup from the Windows controller.
Restore this backup to the Home Assistant based controller. Works and there is no issues with taking apart a home assistant partial backup.
1 Like
Hi,
Not the biggest issue but it’s somehow irritating me. I’m happy that the topology actually “almost” works, in my cloud key gen 1 it was compleatly blank. But it’s only the wifi clients that properly shows up. Wired clients is just floating in the topology map and I assume this as to do with the specific plufgin docker setup .
Again, not the biggest issue but if somone knows of a fix for this, please let me know,
Does anyone else have troubles starting the 2.6.0 version of the addon?
s6-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.6.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (amd64 / qemux86-64)
Home Assistant Core: 2023.5.4
Home Assistant Supervisor: 2023.04.1
-----------------------------------------------------------
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
[12:44:34] INFO: Configuring timezone (Europe/Amsterdam)...
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
[12:44:52] INFO: Now starting the UniFi Network Application...
[12:44:52] INFO: Note: No add-on specific logs beyond this point.
s6-rc: info: service legacy-services successfully started
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/usr/lib/unifi/lib/tomcat-embed-core-9.0.59.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Even removing the existing addin and installing it fresh gives the same error. I tried searching online for a fix but nothing useful yet. [BUG] The new image does not start · Issue #178 · linuxserver/docker-unifi-controller · GitHub or addon crashes · Issue #414 · hassio-addons/addon-unifi · GitHub
Any ideas?
Edit: made a github issue for it: Addon 2.6.0 does not start correctly · Issue #429 · hassio-addons/addon-unifi · GitHub
I didnt have trouble installing it but after it was installed it broke my supervisor and had to dpgk it through ssh. It was a pain because I lost ha execute permissions.
@jb567; you can also ssh into the container (using the official SSH addon), install a vim editor there and then edit the config.gateway.json that way. That is the way i did it before my Unifi Addon totally stopped working… 
docker exec -it addon_a0d7b954_unifi bash
apt-get update && apt-get install vim -y
vim /usr/lib/unifi/data/sites/default/config.gateway.json
1 Like
I have the exact same issue! I thought it might have been because I was running a Raspberry Pi 4 with 1gb of RAM… I finally got hold of a 4GB version of the Pi 4 so bought it… now I’ve wasted $100 buying it for nothing when it didn’t fix the issue.
Cheers, Mike
s6-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.6.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.5.4
Home Assistant Supervisor: 2023.06.1
-----------------------------------------------------------
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
[07:13:37] 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
[07:13:38] INFO: Now starting the UniFi Network Application...
[07:13:38] INFO: Note: No add-on specific logs beyond this point.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/usr/lib/unifi/lib/tomcat-embed-core-9.0.59.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
As posted in the Github issue:
Ok, I just got it starting again but unsure what fixed it. I removed the addon, cleaned up leftovers (controller backups/ any files i found) via ssh on the hassos instance and rebooted. After that a fresh install works now…
Wierd is that the “An illegal reflective access operation has occurred” error is still there in the logging.
Can you also check after a fresh install if you can go to https://-yourunificontrollerurloriphere-/setup? Wierd thing for me was that the setup page worked, but not the ‘parent’ directory. After going trough the setup process from cratch, everything worked again… With the exact warning still there.
Mine works perfectly and has the same warning. I just ignore it as it’s not making any difference.
s6-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.6.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.2 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.6.0
Home Assistant Supervisor: 2023.06.1
-----------------------------------------------------------
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
[00:15:20] INFO: Configuring timezone (Europe/London)...
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
[00:15:21] INFO: Now starting the UniFi Network Application...
[00:15:21] INFO: Note: No add-on specific logs beyond this point.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/usr/lib/unifi/lib/tomcat-embed-core-9.0.59.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
When can we expect an update that contains 7.4.156? I would love to use the OpenVPN/Wireguard functionality in there.
3 Likes
+1 Me too and even beter now to 7.4.162
2 Likes
Great if this add-on can upgrade to 7.4.156.
7.4.162 is still release candidate. I would already be very happy with 7.4.156.
I’m trying to add a static route (from Traffic management → Static Routes → Create New), but I keep getting this fairly generic error:
There was an error updating settings. This action could not be completed.
Has anyone tried this? Or know where I should start looking to solve this (I haven’t seen anything useful in any of the logs I have found).