Since removing the integration and addon completely, and reinstalling it, the issue was solved.

Problem/Motivation

Both "enable newly added entities" and "track devices" is enabled. Anyways my new phone only shows up inside the unifi controller software, but not inside hassio.

Everything is running on the latest version.

What is strange: under "Network access controlled devices" in the integrations hassio unifi addon config, I actually can see my new devices listed. But not in HA devices or entities.

What could be done to track why no new devices are found?

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

Same problem here. I've configured the static IP using nmcli, but AdGuard Home addon still listens to 127.0.0.1. Thought it can detect the host network interface in the DHCP settings page.

Your installation is not supervised and it is irrelevant to this topic. Can you please keep issue to the topic. If you are having issue with installion, please discussion home assistant forum or refer to this supervised install https://github.com/home-assistant/supervised-installer

Not really. My installation was done literally form the link you pasted below, here, with containers.

Lastly to Hassos still have supervisor install. 'Hassio' no longer in used. Refer to installation method. https://www.home-assistant.io/installation/

I call hassio to everything. Not my problem if the project changes names and goals and breaks things. I am commenting in order to make others not have the same problems I did.

Exactly Container install does NOT have supervisor. If you need supervisor, please install using the 1st link. https://github.com/home-assistant/supervised-installer. I suggest you reinstall your rpi minimal and install home assistant with the link provided above.

Your problem is not with adguard addon. You dont have have supervisor to begin with. Please dont confused other with your container installation which does not support addons

Your installation is not supervised and it is irrelevant to this topic. Can you please keep issue to the topic. If you are having issue with installion, please discussion home assistant forum or refer to this supervised install https://github.com/home-assistant/supervised-installer

Not really. My installation was done literally form the link you pasted below, here, with containers.

Lastly to Hassos still have supervisor install. 'Hassio' no longer in used. Refer to installation method. https://www.home-assistant.io/installation/

I call hassio to everything. Not my problem if the project changes names and goals and breaks things. I am commenting in order to make others not have the same problems I did.

Turns out I followed the stuff from here, and now I realized Hassio doesn't have supervisor anymore and I ended up with a useless thing as I can't restore the snapshot. For people who end up here: https://community.home-assistant.io/t/where-is-supervisor-hassio-from-home-assistant-installed-via-docker/172853/43

Your installation is not supervised and it is irrelevant to this topic. Can you please keep issue to the topic. If you are having issue with installion, please discussion home assistant forum or refer to this supervised install https://github.com/home-assistant/supervised-installer

Lastly to Hassos still have supervisor install. 'Hassio' no longer in used. Refer to installation method. https://www.home-assistant.io/installation/

Problem/Motivation

Controller identifies the networking equipment as unreachable / cant communicate with the networking equipment. Devices: UAP-AC-LR & US-8-60W

Expected behavior

Controller should be able to communicate with the devices just as it did before.

Actual behavior

Devices not listed as connected in the controller. Can however SSH into the devices via home assistant SSH. Also network traffic capture shows communication from devices to controller.

Steps to reproduce

Logfile

Add-on: UniFi Controller Manage your UniFi network using a web browser

Add-on version: 0.23.1 You are running the latest version of this add-on. System: Home Assistant OS 6.0 (amd64 / qemux86-64) Home Assistant Core: 2021.6.5 Home Assistant Supervisor: 2021.06.3

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... 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". Importing keystore /tmp/tmp.bIl1HYoGAA 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. [16:04:07] INFO: Starting the UniFi Controller... org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called Exception in thread "Thread-15" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:177) at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1123) at com.ubnt.service.ooOO.Ö00000(Unknown Source) at com.ubnt.ace.Launcher$2.run(Unknown Source) [16:06:49] INFO: Starting the UniFi Controller...

(How can someone else make/see it happen)

Proposed changes

Tried downgrading to 0.23 and fresh install from backup files, no results.

Edit: Fixed via resetting the inform address on both my devices!

Problem/Motivation

Controller identifies the networking equipment as unreachable / cant communicate with the networking equipment. Devices: UAP-AC-LR & US-8-60W

Expected behavior

Controller should be able to communicate with the devices just as it did before.

Actual behavior

Devices not listed as connected in the controller. Can however SSH into the devices via home assistant SSH. Also network traffic capture shows communication from devices to controller.

Steps to reproduce

Logfile

Add-on: UniFi Controller Manage your UniFi network using a web browser

Add-on version: 0.23.1 You are running the latest version of this add-on. System: Home Assistant OS 6.0 (amd64 / qemux86-64) Home Assistant Core: 2021.6.5 Home Assistant Supervisor: 2021.06.3

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... 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". Importing keystore /tmp/tmp.bIl1HYoGAA 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. [16:04:07] INFO: Starting the UniFi Controller... org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: destroy called Exception in thread "Thread-15" java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext at org.springframework.context.support.AbstractRefreshableApplicationContext.getBeanFactory(AbstractRefreshableApplicationContext.java:177) at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1123) at com.ubnt.service.ooOO.Ö00000(Unknown Source) at com.ubnt.ace.Launcher$2.run(Unknown Source) [16:06:49] INFO: Starting the UniFi Controller...

(How can someone else make/see it happen)

Proposed changes

Tried downgrading to 0.23 and fresh install from backup files, no results.

I got an old home assistant snapshot from a friend with plugin version 0,19 and I fix it, than I moved the controller outside using docker

I suppose i will remain in 0.20.3 until the rpios64 is ready. Thanks anyway

The HA OS supports 64 Bit, and afaik you can run Debian 10 on a Pi. Any other OS is likely to fall under the unsupported category....

I strongly need the gpios, and they don't work in debian/hassos 64. I have to wait until raspios64 is ready.

@ai Thanks for your reply. After further investigation, I realized that we are using precss plugin for our project. I've contacted the maintainer for postcss-advanced-variables about override readonly variable.

I suppose i will remain in 0.20.3 until the rpios64 is ready. Thanks anyway

The HA OS supports 64 Bit, and afaik you can run Debian 10 on a Pi. Any other OS is likely to fall under the unsupported category....

Are you running RaspberryPi OS 64bit without any issues?