Shelly devices on mesh nodes aren't discovered

[Marfre888]

Hi,

I've discovered a weird problem. I have 4 shellies. 3 connected to the main router, and 1 to the mesh node network.

The web interface on all 4 works perfectly, and I can turn them on and off from there. However the shelly 1pm connected to the mesh network is never discovered by this plugin. I can discover it by connecting it to the main router (and turning the mesh node off), but the second I turn it back on it moves back to the mesh router because the connection is stronger and becomes permanently offline in the admin panel.

Help?

[Karo-X]

It's a network issue

[Marfre888]

@Karo-X You're helpful.

It isn't a network issue. The shelly connects fine to the network, all the other 10 devices (not shelly devices) also connect fine to homebridge. The problem has to be with the way the plugin looks for devices

[Karo-X]

You write yourself that it works in the "normal" network and not in the mashed network. It is nothing new that the mashed networks have problems with multicast transporting. You may want to check if this works in your network correctly.

It's possible, that "other devices" may work in your mashed Network, but maybe they don't use multicast?

Network ist a complex thing, if you don't use it for browsing in the web only.

[kengura3]

I have TP Link Deco M5 and I had to turn off beamforming feature.

[mtthsrtl]

Same here.

3 Shellys connected to Main Router (AVM FritzBox!7590) are discovered - 5 are connected to the same network via mesh repeater (FritzBox!4020 and FRITZ!WLAN Repeater 1750E) are not discovered - neither with config file.

[currybeast]

Hello, I had the same, you need to disable Broadcast filtering in your WIfi Mesh. Also fancy things like multicast transmission filtering and dynamic multicast optimization. These seem to block mDNS and Bonjour or confuse it and it never hands off to the other AP's

[alexryd]

See this page for a description of why this is happening and what you can do to troubleshoot it.