eon

it should work because i have tested a lot of different brands with generic drvier. Those with s2 encryption works better than those with s0. Shelly is S2 so i guess that it will work well.
I should get shelly wave 2PM by the end of he month and will let you know how well will work. 
 

Hi Andrew,
This is a screenshot from Shelly Temperature Display. So obviously it affects all thermostats on IOS17. Lets hope that Control4 will update the app soon.

 

Hi Andrew,
This is a screenshot from Shelly Temperature Display. So obviously it affects all thermostats on IOS17. Lets hope that Control4 will update the app soon.

 

Yes it works with any mqtt broker you need to configure zwavejs2mqtt on which broker it needs to connect

I like to came up with the most complicated way to control my home  zwave was connected to C4 via Vera but vera does not like the fibaro dimmers too much it is too slow if you control a scene, than i moved to native zwave on c4 for the dimmers but again the native zwave on c4 was slow and unreliable. In the meantime i used home assistant to translate some devices via http and mqtt to C4. Than i moved all my devices to zwavejs and i was amazed by the speed  so now i’m using home assistant and node red to get states from zwavejs to c4 via C42WAY driver which accepts http commands in C4 and use generic tcp driver from chowmain to send http commands to Home Assistant. And just started to thinker with berto mqtt IoT gateway and etc drivers to see if i can simplify things. Back to your original question Home Assistant has a lousy ui and there is a lot of work to achive simple thing C4 has a great Ui that is why i’m using C4 plus i’m controling my AV via C4
 
p.s. I forgot i use home assistant also to expose all my devices to homekit

You can use the following format ${DEVICE_ID::VARIABLE_LABEL}, it works i’m using it

You can use the following format ${DEVICE_ID::VARIABLE_LABEL}, it works i’m using it