That’s a symptom of the integration not setting up correctly, not the cause.
I did a quick install of HA OS on a VM in Proxmox as I wasn’t sure whether the integration was required or not as I thought it was deprecated? The new install automatically discovered my Shelly gen1 devices on startup:
From reading the Shelly docs it seems to be an mDNS discovery.
Netstat does not show the CoIoT port…
…so I configured one of my Shelly devices (on firmware 20230913-113709/v1.14.0-gcb84623)
to use unicast/CoIoT, and gave it a reboot… and the result is oddly the same but the Shelly is functional:
So HA server and port, not just ticking the box?
There is no box to tick, it’s configured as unicast once an IP and port are entered, otherwise ‘mcast’ enables multicast.
ok, got you. Thought you meant for unicast/mcast.