Home Assistant Community Add-on: UniFi Controller

Yeah, sure

18-10-08 09:52:37 INFO (SyncWorker_10) [hassio.docker.interface] Pull image hassioaddons/unifi tag 0.3.0. 18-10-08 09:52:39 ERROR (SyncWorker_10) [hassio.docker.interface] Can’t install hassioaddons/unifi:0.3.0 -> 500 Server Error: Internal Server Error (“readlink /var/lib/docker/overlay2/l: invalid argument”). 18-10-08 09:54:35 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:04:36 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:04:36 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token 18-10-08 10:14:37 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:24:38 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:34:39 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:34:39 INFO (MainThread) [hassio.homeassistant] Updated Home Assistant API token 18-10-08 10:44:40 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:54:41 INFO (MainThread) [hassio.api.proxy] /homeassistant/api/states access from a0d7b954_appdaemon3 18-10-08 10:56:31 INFO (SyncWorker_17) [hassio.docker.interface] Pull image hassioaddons/unifi tag 0.3.0. 18-10-08 10:56:33 ERROR (SyncWorker_17) [hassio.docker.interface] Can’t install hassioaddons/unifi:0.3.0 -> 500 Server Error: Internal Server Error (“readlink /var/lib/docker/overlay2/l: invalid argument”).

Have been getting these for a couple of days now.

@frenck any luck?

:tada: Release v0.4.0

Full Changelog

Changed

  • Upgrades Unifi to 5.9.29
  • Upgrades binutils to 2.30-21ubuntu1~18.04

Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck

2 Likes

That seems like a system issue, not related to the add-on.
Sorry.

@frenck thanks, will look into it. The server error put me on the wrong track :wink:

Can you share what your configuration.yaml looks like for the Unifi addon?

I am seeing this as well, also using Hassio on Ubuntu 18.04

Editing the resolv.conf solved this and I also now see Firmware versions in the Maintenance screen in settings.

I tried the daemon.json approach but that did not help even after a restart, I probably did something wrong.

Did you ever get this sorted? Is the Hass.io add-on and the Unifi WAP tracker compatible?

In the meantime, I am trying to fallback to the direct tracker but my password is being rejected. Is it the same password as for the controller?

You can setup multiple user accounts in the Unifi Controller software. Recommendation is to setup a read-only account dedicated to the device tracker so that would use a different user/pw combo to your normal admin login.

I expect Docker 18.09 to be out really soon (currently at beta 3 stage).
This will fix the DNS issues with Docker on Systemd Resolved systems (like Ubuntu 18.04)

1 Like

That’s probably good practice - I’ve done that (now) and setup a new read only user - still no login however!

Query: where is the username/password for direct access to the AP set? Or is it the same/linked as the username/password for the controller?

Ah, I’m only working with the controller, not using the direct access to the AP. I’m sure you can setup new users there, but suspect it may need to be done on the command line rather than via the web user interface. Sorry can’t help on that point.

No worries. I’ve finally got connected directly to the AP (by finding a post on the Ubiquti forum which said where to find the ssh username and password).

I’m still not clear of the advantages/disadvantages of direct AP vs controller access… I suspect I can’t do controller access due to hosting the controller on the same Pi as my Hass

Ah. detection_time. That might be the massive advantage to connecting to the controller not the AP? At the moment despite my WiFi being off on my phone for 15 minutes the controller hasn’t closed the connection to my phone and Home Assistant therefore thinks my phone is still ‘home’. Looks like there is a workaround to this integrated into the WAP component but not the direct?

My soul reason to go over to Hass.io was to get this addon. Only to be meet by the same problem allot of people seem to gotten stuck with.

I came from a new install and first thing i went for was to instll this. And im stuck on
“UniFi Controller is starting up…
Please wait a moment”

-----------------------------------------------------------
 armhf / HassOS 1.12 / HA 0.81.2 / SU 138 / stable
-----------------------------------------------------------

[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting the UniFi Controller

Ive read the whole thread and to what i find theres no solution to this? Some has been talking about waiting. im on my 8 hour now. Some say change port. But that does nothing aswell. i spent 3 more hours trying a diffrent port. Loggs says nothing to help out aswell… What am i missing here?

Yeh seems to be the nr1 problem with the addon right now.

Sadly the same problem here. It did work this morning though, as I added another access point this morning. No problem at all. I’ve shut down the server (clean shut down) to do some maintenance (cleaning the dust out and moving it to a new location) and since then it does not work anymore. I enabled the other logging but no regard. It was on for 5 hours, it was still not started.

Log

“url”: “Home Assistant Community Add-on: UniFi Controller”,
“detached”: false,
“available”: true,
“build”: false,
“network”: {
“1900/udp”: 1900,
“3478/udp”: 3478,
“6789/tcp”: 6789,
“8080/tcp”: 8080,
“8443/tcp”: 8443,
“8843/tcp”: 8843,
“8880/tcp”: 8880,
“10001/udp”: 10001
},
“host_network”: false,
“host_pid”: false,
“host_ipc”: false,
“host_dbus”: false,
“privileged”: ,
“full_access”: false,
“apparmor”: “default”,
“devices”: null,
“icon”: true,
“logo”: true,
“changelog”: true,
“webui”: “https://[HOST]:8443”,
“stdin”: false,
“hassio_api”: true,
“hassio_role”: “default”,
“auth_api”: false,
“homeassistant_api”: false,
“gpio”: false,
“devicetree”: false,
“docker_api”: false,
“audio”: false,
“audio_input”: null,
“audio_output”: null,
“services”: ,
“discovery”:
} .last_version
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing…
TRACE: hass.config.true: ssl
TRACE: hass.jq.is_boolean: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl boolean
TRACE: hass.jq: /data/options.json .ssl | if type==“boolean” then true else false end
TRACE: hass.config.get: ssl
TRACE: hass.config.exists: ssl
TRACE: hass.jq.exists: /data/options.json .ssl
TRACE: hass.jq: /data/options.json .ssl
TRACE: hass.config.is_secret: ssl
TRACE: hass.jq.is_string: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl string
TRACE: hass.jq: /data/options.json .ssl | if type==“string” then true else false end
TRACE: hass.config.is_secret: ssl
TRACE: hass.jq.is_string: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl string
TRACE: hass.jq: /data/options.json .ssl | if type==“string” then true else false end
TRACE: hass.jq.is_string: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl string
TRACE: hass.jq: /data/options.json .ssl | if type==“string” then true else false end
TRACE: hass.jq.is_boolean: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl boolean
TRACE: hass.jq: /data/options.json .ssl | if type==“boolean” then true else false end
TRACE: hass.jq: /data/options.json .ssl // false
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 50-persist-data.sh: executing…
TRACE: hass.directory_exists: /data/unifi/data
TRACE: hass.directory_exists: /backup/unifi
[cont-init.d] 50-persist-data.sh: exited 0.
[cont-init.d] 60-ssl.sh: executing…
TRACE: hass.config.false: ssl
TRACE: hass.jq.is_boolean: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl boolean
TRACE: hass.jq: /data/options.json .ssl | if type==“boolean” then true else false end
TRACE: hass.config.get: ssl
TRACE: hass.config.exists: ssl
TRACE: hass.jq.exists: /data/options.json .ssl
TRACE: hass.jq: /data/options.json .ssl
TRACE: hass.config.is_secret: ssl
TRACE: hass.jq.is_string: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl string
TRACE: hass.jq: /data/options.json .ssl | if type==“string” then true else false end
TRACE: hass.config.is_secret: ssl
TRACE: hass.jq.is_string: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl string
TRACE: hass.jq: /data/options.json .ssl | if type==“string” then true else false end
TRACE: hass.jq.is_string: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl string
TRACE: hass.jq: /data/options.json .ssl | if type==“string” then true else false end
TRACE: hass.jq.is_boolean: /data/options.json .ssl
TRACE: hass.jq.is: /data/options.json .ssl boolean
TRACE: hass.jq: /data/options.json .ssl | if type==“boolean” then true else false end
TRACE: hass.jq: /data/options.json .ssl // false
[cont-init.d] 60-ssl.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting the UniFi Controller

Same for Debug:

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 v0.4.0

Manage your UniFi network using a web browser

From: Community Hass.io Add-ons
By: Franck Nijhof [email protected]

amd64 / null / HA 0.81.5 / SU 138 / stable

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing…
Log level is set to DEBUG
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executing…
DEBUG: Requested API resource: http://hassio/supervisor/ping
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {“result”: “ok”, “data”: {}}

DEBUG: Requested API resource: http://hassio/addons/self/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {“result”: “ok”, “data”: {“name”: “UniFi Controller”, “slug”: “a0d7b954_unifi”, “description”: “Manage your UniFi network using a web browser”, “long_description”: “# Community Hass.io Add-ons: UniFi Controller\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\n[![Support my work on Patreon][patreon-shield]][patreon]\n\nThe UniFi Controller allows you to manage your UniFi network\nusing a web browser.\n\n## About\n\nThis add-on runs Ubiquiti Networks’ UniFi Controller software, which allows\nyou to manage your UniFi network via the web browser. The add-on provides a\nsingle-click installation and run solution for Hass.io, allowing users to get\ntheir network up, running, and updated, easily.\n\nThis add-on supports all Hass.io supported architectures, including the\nRaspberry Pi.\n\n[Click here for the full documentation][docs]\n\n![UniFi Controller][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: chat: invalid server https://discord.me/hassioaddons\n[docs]: https://github.com/hassio-addons/addon-unifi/blob/v0.4.0/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: Home Assistant Community Add-on: UniFi Controller https://img.shields.io/maintenance/yes/2018.svg\n[patreon-shield]: https://www.frenck.nl/images/patreon.png\n[patreon]: https://www.patreon.com/frenck\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-experimental-yellow.svg\n[release-shield]: https://img.shields.io/badge/version-v0.4.0-blue.svg\n[release]: https://github.com/hassio-addons/addon-unifi/tree/v0.4.0\n[screenshot]: https://github.com/hassio-addons/addon-unifi/raw/master/images/screenshot.jpg”, “version”: “0.4.0”, “auto_update”: true, “repository”: “a0d7b954”, “last_version”: “0.4.0”, “state”: “started”, “protected”: true, “rating”: 5, “boot”: “auto”, “options”: {“log_level”: “debug”, “ssl”: false, “certfile”: “fullchain.pem”, “keyfile”: “privkey.pem”}, “arch”: [“aarch64”, “amd64”, “armhf”, “i386”], “machine”: [“intel-nuc”, “qemux86”, “qemux86-64”, “qemuarm”, “qemuarm-64”, “raspberrypi”, “raspberrypi2”, “raspberrypi3”, “raspberrypi3-64”, “tinker”, “odroid-c2”, “odroid-xu”], “url”: “Home Assistant Community Add-on: UniFi Controller”, “detached”: false, “available”: true, “build”: false, “network”: {“1900/udp”: 1900, “3478/udp”: 3478, “6789/tcp”: 6789, “8080/tcp”: 8080, “8443/tcp”: 8443, “8843/tcp”: 8843, “8880/tcp”: 8880, “10001/udp”: 10001}, “host_network”: false, “host_pid”: false, “host_ipc”: false, “host_dbus”: false, “privileged”: , “full_access”: false, “apparmor”: “default”, “devices”: null, “icon”: true, “logo”: true, “changelog”: true, “webui”: “https://[HOST]:8443”, “stdin”: false, “hassio_api”: true, “hassio_role”: “default”, “auth_api”: false, “homeassistant_api”: false, “gpio”: false, “devicetree”: false, “docker_api”: false, “audio”: false, “audio_input”: null, “audio_output”: null, “services”: , “discovery”: }}

DEBUG: Filtering response using: .version
DEBUG: Requested API resource: http://hassio/addons/self/info
DEBUG: API HTTP Response code: 200
DEBUG: API Response: {“result”: “ok”, “data”: {“name”: “UniFi Controller”, “slug”: “a0d7b954_unifi”, “description”: “Manage your UniFi network using a web browser”, “long_description”: “# Community Hass.io Add-ons: UniFi Controller\n\n[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]\n\n[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]\n\n[![Buy me a coffee][buymeacoffee-shield]][buymeacoffee]\n\n[![Support my work on Patreon][patreon-shield]][patreon]\n\nThe UniFi Controller allows you to manage your UniFi network\nusing a web browser.\n\n## About\n\nThis add-on runs Ubiquiti Networks’ UniFi Controller software, which allows\nyou to manage your UniFi network via the web browser. The add-on provides a\nsingle-click installation and run solution for Hass.io, allowing users to get\ntheir network up, running, and updated, easily.\n\nThis add-on supports all Hass.io supported architectures, including the\nRaspberry Pi.\n\n[Click here for the full documentation][docs]\n\n![UniFi Controller][screenshot]\n\n[buymeacoffee-shield]: https://www.buymeacoffee.com/assets/img/guidelines/download-assets-sm-2.svg\n[buymeacoffee]: https://www.buymeacoffee.com/frenck\n[discord-shield]: chat: invalid server https://discord.me/hassioaddons\n[docs]: https://github.com/hassio-addons/addon-unifi/blob/v0.4.0/README.md\n[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg\n[forum]: Home Assistant Community Add-on: UniFi Controller https://img.shields.io/maintenance/yes/2018.svg\n[patreon-shield]: https://www.frenck.nl/images/patreon.png\n[patreon]: https://www.patreon.com/frenck\n[project-stage-shield]: https://img.shields.io/badge/project%20stage-experimental-yellow.svg\n[release-shield]: https://img.shields.io/badge/version-v0.4.0-blue.svg\n[release]: https://github.com/hassio-addons/addon-unifi/tree/v0.4.0\n[screenshot]: https://github.com/hassio-addons/addon-unifi/raw/master/images/screenshot.jpg”, “version”: “0.4.0”, “auto_update”: true, “repository”: “a0d7b954”, “last_version”: “0.4.0”, “state”: “started”, “protected”: true, “rating”: 5, “boot”: “auto”, “options”: {“log_level”: “debug”, “ssl”: false, “certfile”: “fullchain.pem”, “keyfile”: “privkey.pem”}, “arch”: [“aarch64”, “amd64”, “armhf”, “i386”], “machine”: [“intel-nuc”, “qemux86”, “qemux86-64”, “qemuarm”, “qemuarm-64”, “raspberrypi”, “raspberrypi2”, “raspberrypi3”, “raspberrypi3-64”, “tinker”, “odroid-c2”, “odroid-xu”], “url”: “Home Assistant Community Add-on: UniFi Controller”, “detached”: false, “available”: true, “build”: false, “network”: {“1900/udp”: 1900, “3478/udp”: 3478, “6789/tcp”: 6789, “8080/tcp”: 8080, “8443/tcp”: 8443, “8843/tcp”: 8843, “8880/tcp”: 8880, “10001/udp”: 10001}, “host_network”: false, “host_pid”: false, “host_ipc”: false, “host_dbus”: false, “privileged”: , “full_access”: false, “apparmor”: “default”, “devices”: null, “icon”: true, “logo”: true, “changelog”: true, “webui”: “https://[HOST]:8443”, “stdin”: false, “hassio_api”: true, “hassio_role”: “default”, “auth_api”: false, “homeassistant_api”: false, “gpio”: false, “devicetree”: false, “docker_api”: false, “audio”: false, “audio_input”: null, “audio_output”: null, “services”: , “discovery”: }}

DEBUG: Filtering response using: .last_version
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirements.sh: executing…
[cont-init.d] 10-requirements.sh: exited 0.
[cont-init.d] 50-persist-data.sh: executing…
[cont-init.d] 50-persist-data.sh: exited 0.
[cont-init.d] 60-ssl.sh: executing…
[cont-init.d] 60-ssl.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting the UniFi Controller

Are there any news on this? I would love to be able to use @frenck’s awesome work.

I recently upgraded to 0.82 on hassos from 0.68 on resin on a RPi3 and installed and started the Unifi Controller without issue.
My problem is that I’m trying to restore from a back-up of my previous ( non hassio ) Unifi install.
After the restore, the system tries to auto adopt my gateway and access point and seems to be stuck in a loop of adopting and re-adopting…

Like Jivesinger mine started working on 0.82 magicly. So guess it was a homeassistant problem.