it will work as your backup contains all the addon information. I did the same and it works. you only need to make sure that when executing and restoring the backup, all options are checked.
Perfect, thank you…
nice BUT …
I updated the addon from 0.19.3 to 0.20.0 (auto-update did not work) and restatter addon
I am getting the following error
I did not change ports but now not working
Any idea?
because now Unifi is down 
I started to change the port in error and got next port in error …
In fact seems like HA host remembers all ports used by Unifi addon before update. So when trying to restart after update all Unifi ports are already in use.
If this happen to you the solution is to restart the HA host:
- supervisor | system | ‘reboot host’
Now it works 
Is there a way to SSH into the controller (not directly into the devices)?
Having this issue which requires SSH access to the controller to fix 
USG L2TP issue - “Authentication Failed” | Ubiquiti Community
I think you are right there is a need for forwarding port 22/tcp to be able to ssh to controller
see https://help.ui.com/hc/en-us/articles/218506997-UniFi-Ports-Used
Created a PR that will hopefully be considered:
Map port 22 for SSH by GeertvanHorrik · Pull Request #148 · hassio-addons/addon-unifi (github.com)
1 Like
I had the same problem; I activated RADIUS in the new settings menu which resulted that the Client option was unchecked/disabled. I deleted the VPN and disabled RADIUS and reconfigured everything in the ‘old’ settings, but the client option was still disabled and greyed out…
But I was able to enable the client checkbox by using the browser developer tools. I did it with (the new) Edge browser, but it should also work with Firefox, Chrome etc.
- In the Unify controller setting menu go to Services > RADIUS (tab) > Server (sub tab)
- Here you should see you RADIUS configuration with the Client options unchecked and grayed out
- Press F12 to open the browsers developer tools
- Go to the Elements tab and press the element picker (or use Ctrl + Shift + C)
- Click on the (grayed out) Client checkbox
- Remove this text:
disabled class=“ng-pristine ng-untouched ng-valid ng-valid-divergent ng-not-empty”
Change this:
To this (option is now not grayed out anymore and you should be able to check the option now):
1 Like
I’m having a super annoying issue with my Unifi AP and I can’t even begin to troubleshoot it as I can’t find the log file! According to this server.log should be in /usr/lib/unifi/logs/ but all I see there is mongod.log which is useless in tracking my issue. Where do I look for a proper log file?
Also, while I’m at it perhaps someone will have a swing at the root issue at hand. In the last month the AP (UAP-AC-M) would drop ALL of the 30+ IoT WiFi devices (esphome, tasmota, broadlinks etc) for absolutely no reason at all. When this has happened, the AP would be actually up and running, I can connect my phone and run a iperf test to the max of the available bandwidth. The Unifi controller (via HA addon obviously) reports all the devices to be actually connected yet with very, very low experience score of 60%. In reality, however, they are NOT connected as I can see them raising their fallback hotspots and esphome shows all of them in red. Also, I just noticed around the time they all got dropped the controller reported these anomalies:
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving a domain name to an IP address (DNS timeout).
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving an IP to a MAC address (ARP timeout).
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving a domain name to an IP address (DNS timeout).
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving a domain name to an IP address (DNS timeout).
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving a domain name to an IP address (DNS timeout).
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving a domain name to an IP address (DNS timeout).
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble obtaining an IP via DHCP.
8:00am
Client is having trouble resolving a domain name to an IP address (DNS timeout).
Any clues as to what might be at play here? Don’t see how this could be related at all but this thing started happening around the time I added a legacy EOL device to the mix (UAP lite not AC)
Have been running Hass & Unifi in Docker on my NAS. Now I got a Home Assistant Blue (Odroid) to run Hass dedicatedly on separate hardware (hoping the performance will be better).
I’m also considering moving Unifi to this device. Is it possible on that same Odroid device to run the Unifi Addon on the default unifi management VLAN and Hass on my IoT VLAN and hence connect the Odroid over a “trunk” connection with these 2 VLANs (so not an untagged access connection)? If yes, how do I do this?
Thanks!
Upgraded to the latest version today’s day I’m getting this error… funny thing is that all still seems to work fine. Anyone else noticed this?
[23:06:27] INFO: Starting the UniFi Controller...
2021-04-07 23:06:30,600 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
2021-04-07 23:06:32,103 main ERROR Unable to locate appender "InMemoryAppender" for logger config "root"
Hi All, I’m getting desperate and would appreciate your help. Since about a month, I can no longer connect to my Unifi Controller. Add-on and HA core are fully up to date. If I click on Open Web UI I just get an error page Connection Refused. I tried with or without SSL, no difference. When I uninstall it and reinstall it, the setup page comes up, but as soon as I restore my Controller backup the same thing happens again. I didn’t change any settings before it happened. Any tips are greatly appreciated.
I’m also having problems connecting to https://homeassistant.local:8443/ after the upgrade.
-----------------------------------------------------------
Add-on: UniFi Controller
Manage your UniFi network using a web browser
-----------------------------------------------------------
Add-on version: 0.21.0
You are running the latest version of this add-on.
System: Home Assistant OS 5.13 (armv7 / raspberrypi3)
Home Assistant Core: 2021.4.4
Home Assistant Supervisor: 2021.04.0
-----------------------------------------------------------
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 DEBUG
[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.
[16:26:45] INFO: Starting the UniFi Controller...
2021-04-13 16:26:56,448 main ERROR Error processing element InMemoryAppender ([Appenders: null]): CLASS_NOT_FOUND
2021-04-13 16:26:58,957 main ERROR Unable to locate appender "InMemoryAppender" for logger config "root"
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
log_level: debug
memory_max: 1024
memory_init: 512
Mine suddenly started working again, out of the blue. Very strange. I have set SSL: True.
Same for me
So is it safe to upgrade from 0.20.2 to 0.21.0 or better wait?
thanks
Hi everyone,
My HA install crashed recently, probably because of a bad SD card.
I’ve reinstalled everything on an SSD now, and every time I install the Unifi Controller add-on, the whole system becomes unresponsive at a level that it’s not usable anymore.
I’m on an RPI3, HassOS 64 bit, with an SSD and I only have SSH, File Management, and DuckDNS installed.
I think that the CPU is an issue here but I have no way to check this as the whole system doesn’t respond anymore, even though SSH (or extremely sluggish).
I didn’t have the issue before my SD crash and I know that the version of the controller changed between the 2.
Has anyone experienced the same issue? How can I check it and, ideally, fix it?
Here is my system info:
## System Health
version | core-2021.4.4
-- | --
installation_type | Home Assistant OS
dev | false
hassio | true
docker | true
virtualenv | false
python_version | 3.8.7
os_name | Linux
os_version | 5.4.83-v8
arch | aarch64
timezone | Europe/Brussels
<details><summary>Home Assistant Cloud</summary>
logged_in | false
-- | --
can_reach_cert_server | undefined
can_reach_cloud_auth | undefined
can_reach_cloud | undefined
</details>
<details><summary>Home Assistant Supervisor</summary>
host_os | Home Assistant OS 5.13
-- | --
update_channel | stable
supervisor_version | supervisor-2021.04.0
docker_version | 19.03.15
disk_total | 116.7 GB
disk_used | 3.8 GB
healthy | true
supported | true
board | rpi3-64
supervisor_api | undefined
version_api | undefined
installed_addons | SSH & Web Terminal (8.1.1), Duck DNS (1.12.5), File editor (5.2.0), UniFi Controller (0.21.0)
</details>
<details><summary>Lovelace</summary>
dashboards | 1
-- | --
resources | 0
mode | auto-gen
</details>
Thank you very much for your support.
Best regards,
Olivier.