Home Assistant Community Add-on: UniFi Controller

This is the add-on.

So delete the integration then. As I wrote

How do you do that when it’s not in the list of integrations?

If you never installed the integration then it wont be there. Kenneth hasn’t realised that not all of us use both the Add-on and the Integration (I’m only using the Add-on too) so follow silvrr’s advice

I knew if I didn’t install the integration it wouldn’t be there… :laughing:

is it possible to install a custom version of the controller, namely a 5.14.x release? I need it for my 6 Lite AP…

Hi @frenck, could you update the controller to the latest 5.14.22? Would be great.

2 Likes

Sigh, ignore me, new version does work, toke ages to start tho

1 Like

Have been using UniFi adding for about a year and haven’t had any issues until now. Needed to make a switch port change but can’t get in. Gave me a Tomcat error. Looking at the logs from Supervisor gives me.

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…

Hass.io Add-on: UniFi Controller
Manage your UniFi network using a web browser

Add-on version: 0.18.1
You are running the latest version of this add-on.
System: HassOS 4.12 (amd64 / qemux86-64)
Home Assistant Core: 0.114.4
Home Assistant Supervisor: 235

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] unifi.sh: executing…
[cont-init.d] unifi.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[21:10:26] INFO: Starting the UniFi Controller…
Exception in thread “launcher” java.lang.IllegalStateException: Tomcat failed to start up
at com.ubnt.net.OoOO.ö00000(Unknown Source)
at com.ubnt.service.new.õÓ0000(Unknown Source)
at com.ubnt.ace.Launcher.main(Unknown Source)
Caused by: java.lang.RuntimeException: Web context failed to initialize
… 3 more

Where can I start troubleshooting?

Hello, with latest version of Home assistant (115.2) i can’t start the addons, when try the error is Failed to start addon - Unknown error, see logs, but the log is empty…


Any idea?

Hi @frenck, really appreciate the work! Love to see version 6.0.22. Any update on that?
Thanks!

1 Like

I’m new to HA but not UniFi, was stoked to see this add-on existed. Please verify, controller updates must come through add-on updates, there is no mechanism to update the controller version independent of the add-on. Thanks again, awesome work!

That’s correct.

1 Like

Hello,
I can not connect to my controller anymore since a month now.
I did the updates but I still get this error:


This site is not available…
I use duckdns and nginx, what could be wrong ?
I has working fine till I restore an backup from my Home Assistant.
Regards,
Bart

Try using the local IP address.

I guess you use DDNS. This returns your public IP address and I can imagine that you do not have the port forwarded (8443) or not forwarded to the correct internal IP address.
In case of IPv6, this IP address can change as-well of course, so make sure you have the port open for the correct IP address.

Hello,
I get the error on local address as well.
The strange thing is that it has works before !
After some updates it doesn’t work anymore.
The ports are forwarded correctly.

Hmmm, that’s strange. Do the logs show anything out of the ordinary?

I see that the add-on was upgraded to Unifi controller 6.x a few days ago, but reading the UBNT forums it would appear not insignificant numbers of people are affected by breaking changes that 6.x contained (eg. the removal of WiFi overrides) and would be affected by upgrading.

I’m not ready to move to 6.x yet on my own network because of some of the breaking changes. However, as the add-on has upgraded to 6.x already, I guess I am stuck pinned to v0.18.1 of the add-on without being able to get further 5.x updates via the add-on. (It is a good incentive to increase the priority of preparing to upgrade to 6.x though!)

It would have been nice if there was an add-on for 6.x separate to the one for 5.x, just like how it was when AppDaemon was upgraded from 3.x to 4.x. People could then move to the 6.x add-on when they were ready and/or able. In the meantime they could also keep their 5.x install updated with new 5.x releases.

Could that method be considered as a template for future rollouts of all add-ons where there is a major upgrade of the underlying software, and where older releases continue to be maintained by the software’s author(s)?

The latest version in 5 is 5.14.23, which is the same as offered in Add-On version 0.18.1.
I personally don’t expect that there will be a new v5 version and so it’ will probably be no issue.
If it is, you might want to consider installing a docker container and install the controller in it.

Hello,
This is my log:

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…

Hass.io Add-on: UniFi Controller
Manage your UniFi network using a web browser

Add-on version: 0.19.0
You are running the latest version of this add-on.
System: HassOS 4.13 (armv7 / raspberrypi3)
Home Assistant Core: 0.115.4
Home Assistant Supervisor: 245

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] unifi.sh: executing…
Importing keystore /tmp/tmp.Pz95DbwcPk to /usr/lib/unifi/data/keystore…
Warning:
The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using “keytool -importkeystore -srckeystore /usr/lib/unifi/data/keystore -destkeystore /usr/lib/unifi/data/keystore -deststoretype pkcs12”.
[cont-init.d] unifi.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:17:45] INFO: Starting the UniFi Controller…