Thanks mate, I used to use the SSH method in the past but didn’t prevent it from happening, now I use the Discovery app because it’s faster.
Great stuff, thanks.
Quick question regarding the step"
Change the Controller Hostname/IP to match the IP or hostname of
the device running [Hass.io ]
Is this the external hostname (as in does the controller need to be accessed publically?) or could the internal ip work (ie the IP of the raspPi?)
Cheers
I’m using the internal ip
I think this was asked earlier in the thread but not sure it was answered. Running Hass.io on RPi3 and I plan on deploying a CC2531 zigbee2mqtt USB dongle. Does this add-on avoid the MQTT conflict issues mentioned in main Unifi page - https://www.home-assistant.io/components/unifi/?
The default settings for this add-on and the MQTT Server and Web Client add-on have everything configured to use different ports, so you should be fine.
Many thanks!
Wow, works perfect! Thanks a lot
btw: I am running this and Zigbee2MQTT without any (MQTT) issues.
Release v0.11.0
This is a general maintenance release and contains no breaking changes.
Changes
-
Added SNMP port as an option. (#44) -
Upgrades openjdk-8-jdk-headless to 8u222-b10-1ubuntu1~18.04.1 -
Upgrades add-on base image to v3.1.4
-
Upgrades UniFi Controller to 5.10.26
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
4 Likes
Hi all, I’m sure I’m being super dim here but I simply can’t get the addon to start on hass.io version 0.97.1. I’ve added it from the addon store, switched SSL to false and hit start and then nothing. The start button spins for a few seconds then returns to blue. There’s nothing logged on the addon log at the bottom of the page and nothing in the homeassitant.log either. Am I missing something really simple here?
Check the logs under the Developer Tools -> Info.
This has happened to me on several add-ons that won’t start, it looks like it’s starting for a few seconds then it just stops. Nothing showed up under the log for the add-on. Reinstalling wouldn’t help.
The log viewer also showed nothing. However under the Developer Tools -> Info I found the error, somehow the add-on was getting locked.
Either way 99% percent of the time, a restart to Hassio (or even the host) solves the issue, including the random locks on add-ons.
Hi @gurbina93, thanks for the update. No luck though I’m afraid. There’s nothing visible in the developer logs and a restart, plus upgrade to 0.97.2 still has the addon stuck at not starting. It’s really strange.
Hi Guys,
Just installed the unifi controller add-on in Hassio. I have a couple of problems:
- I can’t access the controller with my duckdns url. I can only access it through http:// with the local ip-address and port 8443. Is it possible to access through duckdns with the use of the ssl certificate?
- I can’t adopt my devices (1x USG router and 3 AP’s). I’ve followed the instructions of the manual. Changed the controller hostname/IP to my local IP address (without http:// and port). Also checked the overwrite inform checkbox. All my devices show the status not connected. My old controller is still working and there I see the devices connected. I used the inform url at the adopt pane with the local ip address and port 8443. What can I do to adopt the devices to the Hassio unifi controller?
@gurbina93, I think I’ve just spotted the problem, or at least the cause. I attempted one more startup and happened to look at Hass.io >> System Log (How did I miss this before) and I spotted the following :-
19-08-15 12:29:02 INFO (SyncWorker_1) [hassio.docker.interface] Clean addon_a0d7b954_unifi application
19-08-15 12:29:05 ERROR (SyncWorker_1) [hassio.docker] Can’t start addon_a0d7b954_unifi: 500 Server Error: Internal Server Error (“driver failed programming external connectivity on endpoint addon_a0d7b954_unifi (18c40e114660df99f8cfc26a5d3291b2b3b0057625e6fd5cba01d99577d67808): Error starting userland proxy: listen tcp 0.0.0.0:8080: bind: address already in use”)
Now I just need to figure out what’s using port 8080. I’m running Esphome, Node Red and the embedded MQTT server and it seems like MQTT could be the culprit. I’m not actively using and MQTT devices now my multisensors are running Esphome so I’ll check that first.
It was definitely the embedded MQTT broker causing the problem. I can’t seem to reach the WebUI over my Nabu Casa cloud connection but I’ll check when I get home for the local UI link.
1 Like
In order to view it remotely you will need to forward port 8443 in your router
Thanks @sparkydave, that was my guess too. I have a workaround for the current controller so I’ll just adapt it to the new controller once I have it up and running. A few things have jumped up the queue at home but I’ll be back to the UniFi soon.
Release v0.12.0
This is a general maintenance release and contains no breaking changes.
Changes
-
Upgrades add-on base image to v3.2.0
-
Upgrades UniFi Controller to 5.11.39
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
1 Like
I am getting 19-08-31 14:31:55 ERROR (SyncWorker_7) [hassio.docker] Can't start addon_a0d7b954_unifi: 500 Server Error: Internal Server Error ("driver failed programming external connectivity on endpoint addon_a0d7b954_unifi (a795c7ac496316e2881b6bea61c0ea21e4817edef64b84821ecd09b925b467e4): Error starting userland proxy: listen tcp 0.0.0.0:8080: bind: address already in use") as well. Before I had the UniFi add-on working I had another docker container using port 8080 but I moved it so I could run this. After running this addon once (and subsequently attempting to “restart” it from the hassio UI) I’m now getting the 8080 error.
Nevermind, the other container was still claiming port 8080. All is well now.
thanks frenck for your work! I bought this week 2 ap’s and a usgs and your controller works great!!