this is very generic and hard to help without details…
- What do you see in the log?
- have you tried to access through IP address and port directly : https://192.168.1.xx:8443/ or http://192.168.1.xx:8443/
this is very generic and hard to help without details…
Hi,
I have the same problem.
Regarding 2.
I have tried both. Site can’t be reached
Regading 1.
Here is my log on trace log level
[13:24:40] TRACE: bashio::fs.file_exists: /data/unifi/data/system.properties
[13:24:40] TRACE: bashio::fs.file_exists: /usr/lib/unifi/data/keystore
[13:24:40] TRACE: bashio::fs.file_exists: /data/keystore_reset
[cont-init.d] unifi.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[13:24:41] INFO: Starting the UniFi Controller...
[13:24:41] TRACE: bashio::config.has_value: memory_max
[13:24:41] TRACE: bashio::config: memory_max
[13:24:41] TRACE: bashio::jq: /data/options.json if (.memory_max == null) then
null
elif (.memory_max | type == "string") then
.memory_max // empty
elif (.memory_max | type == "boolean") then
.memory_max // false
elif (.memory_max | type == "array") then
if (.memory_max == []) then
empty
else
.memory_max[]
end
elif (.memory_max | type == "object") then
if (.memory_max == {}) then
empty
else
.memory_max
end
else
.memory_max
end
[13:24:41] TRACE: bashio::var.has_value: 1024
[13:24:41] TRACE: bashio::config: memory_max
[13:24:41] TRACE: bashio::jq: /data/options.json if (.memory_max == null) then
null
elif (.memory_max | type == "string") then
.memory_max // empty
elif (.memory_max | type == "boolean") then
.memory_max // false
elif (.memory_max | type == "array") then
if (.memory_max == []) then
empty
else
.memory_max[]
end
elif (.memory_max | type == "object") then
if (.memory_max == {}) then
empty
else
.memory_max
end
else
.memory_max
end
[13:24:41] TRACE: bashio::config.has_value: memory_init
[13:24:41] TRACE: bashio::config: memory_init
[13:24:41] TRACE: bashio::jq: /data/options.json if (.memory_init == null) then
null
elif (.memory_init | type == "string") then
.memory_init // empty
elif (.memory_init | type == "boolean") then
.memory_init // false
elif (.memory_init | type == "array") then
if (.memory_init == []) then
empty
else
.memory_init[]
end
elif (.memory_init | type == "object") then
if (.memory_init == {}) then
empty
else
.memory_init
end
else
.memory_init
end
[13:24:41] TRACE: bashio::var.has_value: 256
[13:24:41] TRACE: bashio::config: memory_init
[13:24:41] TRACE: bashio::jq: /data/options.json if (.memory_init == null) then
null
elif (.memory_init | type == "string") then
.memory_init // empty
elif (.memory_init | type == "boolean") then
.memory_init // false
elif (.memory_init | type == "array") then
if (.memory_init == []) then
empty
else
.memory_init[]
end
elif (.memory_init | type == "object") then
if (.memory_init == {}) then
empty
else
.memory_init
end
else
.memory_init
end
Hello!
How can I upgrade the controller app to latest version (6.4.54)? I have been instructed to do so by Unifi official support, due to a problem I have with a UAP. I read in this thread that updates are usually deployed through HA addons interface. However, the version installed that I have is 6.2.26, which I guess is much older than expected. I don’t see any notice in Supervisor asking me to update this addon. Any way to manually update it? Thanks!
Regards,
Sésar de la Isla
Hi René
Thanks for your help. I do not have much details about my problem.
I tried the IP address that you refer but without success, I always get the information: This site can’t be reached.
here are the logs form the add-on:
[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...
-----------------------------------------------------------
Add-on: UniFi Controller
Manage your UniFi network using a web browser
-----------------------------------------------------------
Add-on version: 1.0.0
You are running the latest version of this add-on.
System: Home Assistant OS 6.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2021.9.6
Home Assistant Supervisor: 2021.09.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.
[05:04:59] INFO: Starting the UniFi Controller...
Thanks again for the help
André
Ok so this all looks normal. Exactly as I have it.
Do you know your IP address? Should be the same as how you access home assistant through the browser, with the only difference that you have to put the webport (default 8443, see the config tab in the addon ; port in this line: Used for controller web interface and API). With that you should be able to access. Try both http and https.
You can’t. You have to wait for the next update of the addon that will include the then latest controller version.
I have a feeling you ran out of memory. The addon uses a good chunk of memory. Did it use to work before?
@Piggyback: Was working before (i.e. version 0.23.2). Memory was not the problem. I found the following solution that worked for me on github (@andrefsl maybe works for you too):
So it seems this problem happens, when migrating from 32 to 64bit hassio and then updating to unifi add-on 1.0.0. You can read some details in the conversation on github.
thanks for sharing. I migrated from 32bit to 64bit without issue, but due to issues I had that this addon would not be available each time after a restart, I started with a clean install of the addon., so never had the issue.
Hi @mnbrgr and @Piggyback
thanks for the help, how can I make a back-up of unifi controller if I’m not able to reach the controller? I’m missing something?
Thanks
You first need to restore the older version of the unifi add-on which was working. Of course that also means you need to have a backup of the old version.
I do not have the backup for the older version…
HA automatically takes a snapshot before you upgrade any add-ons! ( Unless you turned that function off )
I don’t think you can. If you have made a backup you can find it in the backup folder of homes assistant.
Hello
Thanks a lot for the help. I access the HA with samba and I found a folder with some unifi backups.
Thanks a lot for the help
André
Thank you @Piggyback. How often is the addon updated? Taking into account the difference between current version installed and latest version, it looks like it is not updated regularly.
That depends on the developer or any other volunteer with knowledge. I unfortunately am not skilled enough to do that.
How can I update the UniFi Controller Installation in HomeAssistant?