Shelly integration: native or MQTT with recent Shelly devices

CiaraRutherford shared this idea 11 hours ago
Under Consideration

Hi all

I'm still in doubt after reading the (sadly archived) posts about Shelly & working with MQTT or native integration.

Reason why I'm willing to change or redo the setup: Quite a few (Gen2 and up) devices complain about no state updates. I currently got CoIoT enabled with multicast. Shelly documentation says to enable multicast for Gen1 devices but is not clear whether it's a general recommendation or whether just for Gen1
So a change I could do is changing all devices to static IP (orchestrated by network router, not the individual device). This is a hassle (as you have to go to each individual device through IP geometry vibes).

Another option is to change to MQTT. From what I read it's faster and better state feedback. MQTT doesn't play nice with dimmers but I don't have that, so that's OK by me.

Would you guys still advice going MQTT over standard integration?

Or would you just switch to unicast on all of the Shelly devices with static IP?

Would you also configure the Shelly to use a static IP? I generally try to avoid that. I prefer orchestrating it from the network (Ubiquiti in this case, Asus before). Maybe there's something in my Ubi settings that's part of the problem, but I don't have snooping enabled for the "domotica" network (which is separated and closed).

Any other things I should do "best practice"? I got about 30-40 Shelly devices and several other smart home stuff. I have a Zigbee running for Philips Hue lights.

Thanks in advance!

Leave a Comment
 
Attach a file
Access denied