Shelly integration for TRV - shelly native vs MQTT?

Configuration
1

Hi everyone,

I’m trying to setup multiple zones with Shelly TRVs. Added ping sensor, and I can see (and confirm this by pinging from my own laptop) - device goes off and on through the day, it is not “constantly online” - I guess in order to make battery last longer.

When I want to set temperature (either by call-service, or by generic_thermostat component, or some custom thermostat), sometimes it doesn’t work - seems like “when device is not on WiFi/accesible, I cannot change target:temperature”).
Now wondering, does it make sense to go full MQTT - I hope for the scenario where I send MQTT message to the broker, and once device comes online, will just get the MQTT message. Does it work that way ? Im aware this makes “there will be some delays”, but at least it will be reliable ? What are your experiences here ? Does it work the same way with zigbee-based TRVs and Zigbee2MQTT ?

2

Only if the message has the retained flag set.

3

Got it, sounds very reasonable, thank you!

1 Like
4

Is there a way that if you set the temperature while the device is temporarily offline, the Shelly integration will keep on trying until the device is online while using the shelly native communication (so no MQTT)?