Then you should add that to Zwave-JS-UI GitHub issue, then everybody with this thermostat can benefit from this change. I was recently looking at their GitHub and found several issues with very similar solutions that are all closed (like this one: https://github.com/zwave-js/zwave-js-ui/issues/1804 ...

Interesting, but you have to do the change for each Spirit instance. Does the changes survive to a container restart or an image upgrade ? Yes, you do need to make the changes for each spirit valve individually (only 2 in my setup so relatively easy) I just tried a restart. The changes do not ...

The first version of zwave-js-ui I installed was already the latest which includes the change (12.4.0). But I believe this only added the options in the webinterface of zwave-js-ui, where I could set the modes manually. The discovery templates used by home assistent and domoticz don't include the ...

Original template: "mode_state_template": "{{ {0: \"off\", 1: \"heat\", 11: \"cool\"}[value_json.value] | default('off') }}", Modified template: "mode_state_template": "{{ {0: \"Off\", 1: \"Heat\", 11: \"Energy heat\", 15: \"Full power\", 31: \"Manufacturer specific\"}[value_json.value] | default ...

The Philio problem is fixed by waiting. The device sends temperature and humidity data based on changing values, but only wakes up completely once a day. The radiator valve is still a problem. I can see this code in zwave-js-ui under node>home assistent: { "type": "climate", "object_id": "thermostat ...

I am trying to migrate from openzwave to Zwave-JS-UI and most of it is working well. There are 2 types of devices I have problems with: Eurotronic Spirit radiator valves: I used to set thermostat mode to "manufacturer specific" with some scripts. But now that I moved to Zwave-JS-UI Domoticz adds the ...

The structure seems fine. In the matter of fact, i have created a virtual sensor on my Domoticz 2023.2 (build 15601), and send it to the info payload you showed and it works, the Cover goes to 30%. What Domoticz version do you use exactly? TRV only supported after 2023 beta 15515. Did you enabled ...

I'm new to MQTT and JSON, but this is an example of "info" from a TRV after I changed the valve opening to 30% using the buttons. info = { "wifi_sta": { "connected": true, "ssid": "***********", "ip": "************", "rssi": -56 }, "cloud": { "enabled": false, "connected": false }, "mqtt ...

Thank you very much! I added the 2 lines and can controll the valve position from Domoticz now so I can work with that. But the only thing that doesn't work is if I change the opening with the buttons on the Shelly TRV, Domoticz doens't update the valve opening percentage. It's the same if I put ...

I am trying to control 2 Shelly TRV's from Domoticz. I want to control the valve opening, not the temperature setpoint, but valve % is added as a sensor, not as a dimmer switch like some other z-wave valves I'm using. Is this something I can fix by editing mqtt_templates?