Hello folks,
i have configured all my Shelly Gen1 devices to:
But it seems like Home Assistant OS is not listening:
So, what needs to be done to make Home Assistant OS listening?
Thanks!
Install the Shelly integration.
I did, of course.
All my Shelly Gen2 devices work fine!
Sorry, my mind reading skills are a bit off today.
Try manually adding one of the Gen 1 devices.
Adding the devices manually does not work:
I can say for sure that the Shellys are woken up and reachable. They are in the same IP network as the Home Assistant OS, nothing in between (like a firewall).
Sometimes, Home Assistant OS can discover the Gen 1 Shelly on it’s own (but never all of them at the same time):
If i add the Shellys as suggested, those Shellys get into a flapping state. The status is permanently switching between these two states:
This Problem is not related to one or few Shellys. All my Gen 1 Shellys have this problem.
Also, the Home Assistant is still not listening on CoIoT Port (udp/5683). I think this is the Problem.
Firmware up to date on the Shellys?
yes, all of them have the latest firmware.
What installation type, core and OS version are you running?
Home Assistant OS (running on KVM)
Home Assistant OS: 15.2
Home Assistant Core: 2025.5.3
It is running on a keyboard video and mouse switch?
No, KVM ist a Hypervisor like VMWare ESXi.
See: Kernel-based Virtual Machine - Wikipedia
There are official Home Assistant OS Images for KVM:
Check your network adapter is bridged to the VM correctly.
Also what host OS are you using for the VMs?
Bridge Settings are correct, everything else works fine (like SSH, for example).
Host OS is “Proxmox”. It’s a Debian based Distro designed as a KVM Hypervisor.
Can you do me a favor and enter netstat -tulpn into you Home Assistant Commandline?
Had to pipe it through more there were a lot:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8883 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8884 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:9090 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 368/sshd: /usr/sbin
tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:57435 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8485 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:3483 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:3493 0.0.0.0:* LISTEN -
tcp 0 0 10.1.1.100:139 0.0.0.0:* LISTEN -
tcp 0 0 10.1.1.100:445 0.0.0.0:* LISTEN -
tcp 0 0 10.1.1.100:40000 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN -
tcp 0 0 172.30.32.1:62919 0.0.0.0:* LISTEN 369/ttyd
tcp 0 0 0.0.0.0:4357 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN -
tcp 0 0 0.0.0.0:8123 0.0.0.0:* LISTEN -
tcp 0 0 127.0.0.1:64969 0.0.0.0:* LISTEN -
tcp 0 0 172.30.32.1:64969 0.0.0.0:* LISTEN -
tcp6 0 0 :::1883 :::* LISTEN -
tcp6 0 0 :::1884 :::* LISTEN -
tcp6 0 0 :::8883 :::* LISTEN -
tcp6 0 0 :::8884 :::* LISTEN -
tcp6 0 0 :::9000 :::* LISTEN -
tcp6 0 0 :::111 :::* LISTEN -
tcp6 0 0 :::22 :::* LISTEN 368/sshd: /usr/sbin
tcp6 0 0 :::8485 :::* LISTEN -
tcp6 0 0 :::3306 :::* LISTEN -
tcp6 0 0 :::3493 :::* LISTEN -
tcp6 0 0 fe80::b064:6540:3:40000 :::* LISTEN -
tcp6 0 0 :::5355 :::* LISTEN -
tcp6 0 0 :::4357 :::* LISTEN -
tcp6 0 0 :::8086 :::* LISTEN -
tcp6 0 0 :::8088 :::* LISTEN -
tcp6 0 0 :::8123 :::* LISTEN -
udp 0 0 0.0.0.0:111 0.0.0.0:* -
udp 0 0 10.1.1.255:137 0.0.0.0:* -
udp 0 0 10.1.1.100:137 0.0.0.0:* -
udp 0 0 0.0.0.0:137 0.0.0.0:* -
udp 0 0 10.1.1.255:138 0.0.0.0:* -
udp 0 0 10.1.1.100:138 0.0.0.0:* -
udp 0 0 0.0.0.0:138 0.0.0.0:* -
udp 0 0 0.0.0.0:42775 0.0.0.0:* -
udp 0 0 0.0.0.0:1900 0.0.0.0:* -
udp 0 0 0.0.0.0:1900 0.0.0.0:* -
udp 0 0 0.0.0.0:34991 0.0.0.0:* -
udp 0 0 0.0.0.0:3483 0.0.0.0:* -
udp 0 0 0.0.0.0:36446 0.0.0.0:* -
udp 0 0 0.0.0.0:36832 0.0.0.0:* -
udp 0 0 0.0.0.0:45801 0.0.0.0:* -
udp 0 0 10.1.1.100:5353 0.0.0.0:* -
udp 0 0 127.0.0.1:5353 0.0.0.0:* -
udp 0 0 10.1.1.100:5353 0.0.0.0:* -
udp 0 0 172.30.32.1:5353 0.0.0.0:* -
udp 0 0 172.30.232.1:5353 0.0.0.0:* -
udp 0 0 0.0.0.0:5353 0.0.0.0:* -
udp 0 0 172.30.32.1:5353 0.0.0.0:* -
udp 0 0 0.0.0.0:5353 0.0.0.0:* -
udp 0 0 0.0.0.0:5353 0.0.0.0:* -
udp 0 0 0.0.0.0:5355 0.0.0.0:* -
udp 0 0 0.0.0.0:54709 0.0.0.0:* -
udp 0 0 0.0.0.0:5683 0.0.0.0:* -
udp 0 0 0.0.0.0:39527 0.0.0.0:* -
udp6 0 0 :::111 :::* -
udp6 0 0 :::58972 :::* -
udp6 0 0 :::1900 :::* -
udp6 0 0 :::1900 :::* -
udp6 0 0 :::53936 :::* -
udp6 0 0 :::46110 :::* -
udp6 0 0 :::5353 :::* -
udp6 0 0 :::5353 :::* -
udp6 0 0 fe80::b064:6540:37:5353 :::* -
udp6 0 0 :::5355 :::* -
(12th line from the bottom is CoIoT).
I wonder what’s necessary to enable this…
Nothing. The integration listens on the port.
In my case, netstat states that it does not.
The shelly integration is running in the core/homeassistant container, right? Or could it be, that there’s a different container that’s listening?
I think, i will login to the HA OS host itself and check out the Docker compose file. This way, i can verify if udp/5683 is mapped to the Container (and find out which container it is)
I found this guide:
But it requries physical access to the hardware, which i do not have today. I will do it tomorrow.