Support for thermostat setpoints and Modes

[thucar]

First of all, great work on creating this library. It's much appreciated. I'm running close to 100 Z-Wave devices in my house at this point and Node-Red is holding up very well.

However, I have yet to get a thermostat working. So far I've only managed to read data from the sensors, setpoints, modes, etc. I'm unable to change setpoints or thermostat modes. The thermostats I have tried: Qubino PWM flush thermostat, Qubino On/Off thermostat, HeatIt thermostat, MCOHome thermostat.

The way I have been trying to do it is as follows:

setValue {"args":[100,64,1,1]} - set thermostat Mode to 1, or 'ON'
setValue {"args":[100,67,1,30]} - set thermostat setpoint to 30C

neither of the above give any errors, but they do not register with the thermostats either. There is no reaction. Am I missing something or is this a known issue?

[ekarak]

any contributions are welcome.

[dionmes]

So I stopped using a zwave thermostat because the setpoint only gets changed after a wake-up of the device. At least for the thermostats I encountered. The thermostat does not listen all the time so there could be an extensive delay between sending the setpoint change and the actual change. You can check this by setting the wakeup interval really short, like 1 minute and then see the change happen in 1 minute or less. However this will drain the battery of your thermostat.

[fraser73]

Hi I'm using a Secure/Horstmann SCS317. I paired it separately with its boiler switch and have it included into the main zwave network - I can't remember exactly how I did this, but it took a bit of trial and error. The upside is that if the main network goes down, the heating keeps going.

I set it to wake up every 5 mins, which balances power use with getting the heating to change in a reasonable time.

The initial configuration of the thermostat wake interval was done in open zwave control panel. Which I continue to use for some of the tinkering stuff that isn't easy to do with node red. If you then save the xml file and do a file link between the one that OZWCP uses and the one that node-red uses, you keep the config changes from either app.

Here is how I create the message to set the setpoint, with msg.payload.value being an integer IIRC:

var returnMsg={topic:"setValue", payload:{"nodeid": thermostatNodeId, "cmdclass": 67, "instance": 1, "cmdidx": 1, "value":msg.payload.value}};

This is then passed to the zwave node. I also pass a similar message to MQTT so I can monitor more conveniently.

I've also got a bunch of logic to record that a setpoint change has been issued and is awaiting being received by the thermostat, however it's a bit involved. I can post it on the node red forum, if you want.

[fraser73]

I should also note that I've got a few Danfoss zwave TRVs and they've been a bit of a pain, but generally work ok. These are set to wake every 15mins and are controlled with the same method.

[tobi8]

Hi,

@fraser73 can you explain what you mean with a file link. I am having the same problem but cannot follow what you did.
Thanks.