Unifi Network Add-On showing as stopped but is running

Third party integrations
1

hi everyone,

I’m experiencing a very weird issue with my unify network add-on.
The state shows that it’s stopped (only “Start” button available and red dot in the upper right corner) but it’s actually running and working perfectly fine.

unifiyaddon
unifiyaddon1014×508 28.3 KB

the add-on log doesn’t show any error

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.7.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2023.8.3
 Home Assistant Supervisor: 2023.08.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:01:49] INFO: Configuring timezone (Europe/Vienna)...
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:01:50] INFO: Now starting the UniFi Network Application...
[07:01:50] 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.65.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

Unfortunately this means that the watchdog function doesn’t work, meaning if I restart my HA host (rasperry pi 4B) or the add-on crashes, it won’t automatically restart.

HA logs don’t show anything regarding this integration.

Again, the add-on works just fine and is available via https://<rasperry_ip>:8443

Does anyone have an idea what the issue might be?

Thanks in advance!

2

Your browser have cached the page an is showing that cached page not knowing that things have changed since last visit.
Force reload the page in the browser.

3

hello Wally,
thanks for your reply.

I use 2 different computers and 3 mobile devices with HA companion app installed, the state is the same on all devices so I can rule out the browser cache.

4

Seems like HA is missing a NO_CACHE option on that page.
It should be purely cosmetic though.

5

Not purely cosmetic I’m afraid.
like I said, HA doesnt seem to recognize the running state and therefore the watchdog option doesnt work.
neither does autostart when rebooting.

6

Have you restarted the host lately?
If not then try that to see if that helps.
It is not enough to just restart the HA core here, because it is an addon.

7

I restarted the host (rasperry pi 4b) several times before I created this thread and it didn’t help but I reboot just now fixed the problem and the state is now “running”.

thanks!

edit: ops, celebrated too early…
the add-on was working after the reboot but now a couple of minutes later it’s down and wont start at all. crap :frowning:

edit 2:
I just uninstalled the add-on, rebooted the pi, re-installed the add-on.
after that the state went to “running” and (for now) stays that way.
I now re-adopted my APs und re-did my config (since it wasn’t much) instead of importing a unifi backup.

maybe the problem came from the migration and importing the backup, who knows…
for now the add-on is up&running and also showing the correct state in HA.

I’m really afraid of rebooting HA, though xD

8

The fact that it was actually down and would not start indicates a problem in the addon or it’s configuration and not just a wrong status on the addon info page.