Problem with mDNS / service-discovery with latest firmware, whereas gen1 devices work just fine

VPN/Proxy erkannt

Es scheint, dass Sie einen VPN- oder Proxy-Dienst verwenden. Bitte beachten Sie, dass die Nutzung eines solchen Dienstes die Funktionalität dieser Webseite einschränken kann.

    • Autor

    My Shelly Pro 3EM is on - as of today - latest firmware version: 1.7.0 - 6d4afb10.

    The high-level problem is, that it's rarely being disovered by mDNS/DNS-SD scans, whereas all the other devices, incl. shellys (though all of them gen1), are being discovered reliably.

    Technically it appears, that the Shelly Pro 3EM does not react to scans, nor does it periodically (at least not in reasonable intervals) send out DNS-SD advertisements.

    It does at startup (so I can trigger that by rebooting) and also when changing settings (e.g. toggling eco-mode (doesn't matter whether from off to on or vice versa)).

    While I can't swear on whether it have been working (better) before, this feels like a regression. At least the PRO compared the predecessor (Shelly 3EM gen1).

    Scans initiated via `avahi-browse` (other implementations I tried didn't make a difference) - all devices in the same network-segment without any firewall / wifi client isolation rules.

    Is the Pro 3EM connected via Wi-Fi or LAN?

    I can “see” my Pro 3EM (connected via LAN) FW 1.7.0 under both _http._tcp. and _shelly._tcp.

    Überwiegend PRO 3EM im Einsatz zur Haus und PV Überwachung

    Referring to my post here on community shelly cloud, I have a similar issue with mDNS on Gen 4 devices.

    • Gen2 devices broadcast mDNS, Gen4 device sends zero mDNS packets
    • Same network, same conditions, different behaviour
    • Configuration shows discoverable:true but device is silent and shows bad address when pinged,

    See that thread for details (or I can post here if requested).

    In my case I was using the same IP Address (different SSID) for both Primary and Fallback Wifi.

    Disabling the fallback allowed the device to be discovered using the shellyminig4-deviceid.local address.

    I still need to test whether a different subnet for each Wifi will work.

    I have the same problem when connecting my Shelly Pro 3EM to my Hoymiles Battery Unit. I did manage to connect it immediately after I restarted my Shelly, but the connection is intermittent and the pairing is lost regularly which involves restarting everything and a laborious process which doesn't always work. That said, the Shelly communicates just fine with my homeassistant set up through MQTT. Isn't it possible to sort out a script or similar that will regularly send mDNS packets? This is certainly a bit frustrating as I need the battery units to connect to the Shelly. One thing that occurs to me, is does the Shelly need to operate in server mode to generate advertising mDNS packets??

    Einmal editiert, zuletzt von Invicta (22. November 2025 um 11:39) aus folgendem Grund: Update

  • Dieses Thema enthält 2 weitere Beiträge, die nur für registrierte Benutzer sichtbar sind.