Domoticz

Currently there are only three thermostat setpoint devices available on the OTGW hardware.
It would be great to have an additional thermostat setpoint device available on the OTGW hardware device to allow setting the 'Control setpoint' override value on the OTGW (command CS=<value>).

Looking at the source code for the OTGW hardware driver I can see that (most of) the code for handling this setpoint correctly is already in place.
A thermostat setpoint device (Type=242) with a device Id like '0000001' (e.g. ID4 of the deviceID should be 1), will issue the CS=<> command with the setpoint value.
For testing this, I have manually added a new thermostat setpoint device with device id '0000001' to my OTGW hardware device in the domoticz database.
This actually works and enables me to send a 'Control Setpoint' value to the OTGW.

Only thing missing right now is actually updating the issued setpoint value into the database (e.g. there is currently no UpdateSetPointSensor() method call in the hardware driver code).

It would also be great if this additional thermostat setpoint device for the 'Control setpoint' would be automatically created by the OTGW hardware driver.
Note: Needed because the 'Control Setpoint' override value is not reported back by the OTGW with the PS=1 command (instead it returns the last control setpoint value that is set by the thermostat).

Hi all,

This is a quite old topic, but I still need a setpoint device for OTGW CS command. I can issue the command manually from the OTGW Hardware setup page like "CS=60" but it would be much better to have a device for that.
Anyone can help on this?

Thanks!

Hi all,

Still old, but I can't find a embedded solution.
I hoped with version 5.1 but after reconfigure I cant get a overwrite CS thermostat.

Are there plans to do?

Thanks!

Although the post is old, the problem is still open.
In my case, the command to set control point is the only way to command the water temperature,
hence to control the heather.
Unfortunately there is not such device in Domoticz, but I find a workaround in opentherm monitor,
that is by using mqtt.
In a bash shell the command is the following:

mosquitto_pub -h localhost -t actions/otmonitor/ctrlsetpt -m "{\"name\":\"temp\",\"type\":\"float\",\"value\":$ts}"

where ts is a variable with the desired temperature.
One should activate mqtt from the menu of opentherm.

The problem is that, once you send the command, it is implemented, but after some time the
gateway forgets it and send CS command with the preset temperature.

In order to patch it, I prepared a bach shell that reads the desired temperature from a file and, each 20 seconds,
send the CS command to the gateway through mqtt.

This works rather good for me.
#!/bin/bash
tfile=xxxxxxxxxxx put the file name here
while true
do
# read temperature
read ts < $tfile
mosquitto_pub -h localhost -t actions/otmonitor/ctrlsetpt -m "{\"name\":\"temp\",\"type\":\"float\",\"value\":$ts}"
sleep 20
done

Not exactly what is asked but you could make a dummy/virtual selector switch with some presets and use the action scripts with the api JSON.

Eg See wiki https://www.domoticz.com/wiki/Domoticz_ ... om_command