Setpoint problems on thermostat HRT4-ZW (SRT 321)

[rlkoshak (Rich Koshak)]

@Charly61

How can I clearly bind one variable for “TX” value, and another one variable for “RX” value ?

If there is only one channel you cannot do this.

@Charly61

Or, how can I deal safely with only one variable, the postUpdate / sendCommand and the trigger change / on update / on command ?

postUpdate only changes the internal OH state of the Item. sendCommand will forward the new state to the actual device. But in this case, I think that will not address your problem. I think the root of your problem is that when you use the Slider or SetPoint on your sitemap/HABPanel a whole series of commands get sent. Then a whole bunch of response commands are received as the thermostat reports the new temp it was just set to.

So I think you need to use a Design Pattern: Proxy Item to represent the Thermostat.

Put the proxy Item on your Sitemap and then use a pair of rules to synchronize the Proxy with the “real” item. In one of the rules we will use a timer to avoid sending the command on to the thermostat until it has remained unchanged for a certain amount of time, half a second should about do it but you will have to experiment.

var timer = null

rule "Proxy Item changed"
when
    Item chThermo_Temp_SetPoint_Proxy received command
then
    if(timer == null) {
        timer = createTimer(now.plusMilliseconds(500), [ |
            chThermo_Temp_SetPoint.sendCommand(chThermo_Temp_SetPoint_Proxy.state)
            timer = null
        ]
    }
    else {
        timer.reschedule(now.plusMilliseconds(500)
    }
end

rule "Real Item Updated"
when
    Item chThermo_Temp_SetPoint received update
then
    chThermo_Temp_SetPoint_Proxy.postUpdate(chThermo_Temp_SetPoint.state)
end

This will eliminate any feedback loops and reduce the number of commands sent to the device drastically which hopefully will clear up your problem.

@Charly61

How can I access all the command classes supported by a zwave device ?

You can only access those command classes that the Zwave binding implements. It does not yet support this command class. If you don’t see channels representing a given command class, that version of the Zwave binding does not support it.