Home Assistant Community Add-on: UniFi Controller

Installation Home Assistant OS
,
285

Hello, i have Hassio addon but i dont have the option to upgrade in the addon details.
Ideas?
Thanks

286

Version 0.14.0 is the latest. Which version do you have?

287

I have this version 0.14.0. But I have Unifi version 5.12.35 and now the last is 5.12.66.

288

Ok I get you now. If I see the latest pull request in Git, the version 0.14.0 is built on controller software 5.12.35 indeed. A newer version of the software would need to be a new pull request and subsequently a new add on version. We have to wait for that to come.

289

New update (14.1) released that updates to the version you were looking for (5.12.66)!

1 Like
290

My unify does not start on 14.1. As soon as I uninstall and reinstall the UI works. Then is I restore a backup no go again looks like JAVA?

image
image1533×290 21.5 KB

291

It gets stuck here

image
image1430×736 25.3 KB

292

Had to redo the whole Unifi setup and a Old backup will brick your unifi controller

293

I have auto-update enabled and my controller hasn’t updated yet even though it appears the update has been available for several days. Does anyone have any ideas why this could happen? Is there any way to force an update other than an uninstall/install?

294

I don’t do auto update as I want to validate if there are breaking changes so I can’t tell you. I use Hassio and in the addon there is an update option if there is a new Hassio addon release available for the specific add on.

295

At the end I just redid my Unifi Setup and it worked

1 Like
296

This is what I currently see after a restart:

Add-on version: 0.14.0
There is an update available for this add-on!
Latest add-on version: null
Please consider upgrading as soon as possible.

Does anyone have any ideas why I’m getting a ‘null’ for the new version? Should I submit an issue for this?

1 Like
297

This may be related to a change in the way the latest version is reported. It previously was version_last and now is version_latest. The change seems to have come with a recent update to the Hassio supervisor.

Not saying 100% that this is the issue but the timing seems right for when I started seeing this.

298

@frenck I have the same problem:

  • I made a fresh install of Unifi addon
  • Everything was ok, just some errors in the logs about the java version

  • I run the Controller app and restored a old backup, that I made just right now with another controller
  • Restoring is successful, but the UniFi Addon will not start again
 seems to be something related to Java!

Please could you help me here? :slight_smile: Thx

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.14.1
There is an update available for this add-on!
Latest add-on version: null
Please consider upgrading as soon as possible.
System: HassOS 3.12 (armv7 / raspberrypi3)
Home Assistant Core: 0.107.7
Home Assistant Supervisor: 214

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.7k5Dr1mnhy 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.
[21:11:08] INFO: Starting the UniFi Controller


1 Like
299

I’m having exactly the same issue.

My Unifi controller had stopped working and I was was also having file not found errors when upgrading to the latest Home Assistant version which seems to be a common issue when this add-on has filled up the storage with tmp files.

After removing the Unifi Controller Add-on I was finally able to upgrade but after reinstalling and restoring the latest auto backup, which was over a month old incidentally, the logs are now stopping at “Starting the Unifi Controller”

I really don’t want to restart my config from scratch as I have a USG with several VLANs and would prefer to restore it to an alternative platform if the issue cannot be resolved.

[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.14.1
There is an update available for this add-on!
Latest add-on version: null
Please consider upgrading as soon as possible.
System: HassOS 3.12 (armv7 / raspberrypi3)
Home Assistant Core: 0.108.1
Home Assistant Supervisor: 214

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.4JNrKpKzTG 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.
[15:07:57] INFO: Starting the UniFi Controller


1 Like
300

I have just upgraded to Home Assistant 108.3 and my Unifi controller installation with a restored autobackup is now starting successfully again.

If someone else can confirm this issue may be able to be closed.

[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.14.1

There is an update available for this add-on!
Latest add-on version: null
Please consider upgrading as soon as possible.
System: HassOS 3.12 (armv7 / raspberrypi3)
Home Assistant Core: 0.108.3
Home Assistant Supervisor: 216

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.jAg9niVsbJ 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.
[09:19:48] INFO: Starting the UniFi Controller

OpenJDK Client VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/armv7/libubnt_webrtc_jni.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It’s highly recommended that you fix the library with 'execstack -c ', or link it with ‘-z noexecstack’.

301

I don’t adopt my USG,
I try to hard reset but his state in adopting

Hass.io Add-on: UniFi Controller
 Manage your UniFi network using a web browser
-----------------------------------------------------------
 Add-on version: 0.14.1
 There is an update available for this add-on!
 Latest add-on version: null
 Please consider upgrading as soon as possible.
 System: HassOS 3.12  (armv7 / raspberrypi3)
 Home Assistant Core: 0.108.4
 Home Assistant Supervisor: 217
-----------------------------------------------------------
 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... 
Log level is set to INFO
[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.
[18:46:19] INFO: Starting the UniFi Controller...
OpenJDK Client VM warning: You have loaded library /usr/lib/unifi/lib/native/Linux/armv7/libubnt_webrtc_jni.so which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
302

Thanks for this great addon
 I got a little issue - and I’m stuck:

Everything works fine, when I use in the hass.io add-on details for the UniFi Controller “ssl: false” BUT
I want to store my own certificate.

the “keyfile” and “certfile” shall be stored in the ssl directory - but how? i use the docker containter (which is read-only).

Btw: the hass.io systems says:

http:
  ssl_certificate: ssl/fullchain.pem
  ssl_key: ssl/privkey.pem

and it is working


thx for help

303

I am still having the issue listed above. The add-on just stops at [21:31:44] INFO: Starting the UniFi Controller
 and never fully loads. It has been doing this for a long while and through many versions of HASSIO. I updated to the latest version today and still won’t work.

304

So, when I connect to Home Assistant through hassio.local, then this would be the controller hostname as well right?