Closed danielo515 closed 3 years ago
I think that is a question for the Home-Assistant repo. It might be something that the supervisor does to try and communicate with it's add-ons or so. I don't have much knowledge on this, but I assume you could dig in the supervisor code to understand it.
Description of problem: Hello.
I have my home assistant installation and my zigbee2mqtt running on different nodes. I have configured zigbee to use home assistant as mqtt broker and everything works, a bit slow, but works.
On my zigbee server I have ufw activated, and this blocks access to all ports except for the normal ones: 443, 22, 80, etc.
If I check the log of my zigbee server I see blocked request coming from my hassio host on port 9090. I am wondering what this port is for? And what is home assistant trying to achieve by contacting my zigbee server on that port?
Running platform (details from Suypervisor > System)
System Health
Home Assistant Community Store
GitHub API | ok -- | -- Github API Calls Remaining | 5000 Installed Version | 1.12.3 Stage | running Available Repositories | 890 Installed Repositories | 20Home Assistant Cloud
logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 5.13 -- | -- update_channel | stable supervisor_version | supervisor-2021.04.3 docker_version | 19.03.15 disk_total | 24.9 GB disk_used | 16.8 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Samba share (9.3.1), AppDaemon 4 (0.6.0), File editor (5.3.0), ESPHome (1.17.1), SSH & Web Terminal (8.2.1), WireGuard (0.5.1), UniFi Controller (0.22.0), Node-RED (9.0.1), Mosquitto broker (5.1.1), Visual Studio Code (3.3.1), Home Assistant Google Drive Backup (0.102.0), MariaDB (2.3.0), Portainer (1.5.0)Lovelace
dashboards | 3 -- | -- resources | 11 views | 6 mode | storageFirewall logs