Page 1 of 1

Open Therm Thermostat instead of a gateway translating the stuff

Posted: Tuesday 10 January 2017 9:48
by CaptainSlow
Hi,

I have Remeha Tzerra CV with an eTwist thermostat. I added the OTGW connecting it to the OT terminals IN the CV.
The protocol between the eTwist and the internal own gateway of the CV is NOT Open Therm so messages or roomtemp adjustments sent from domoticz are not "seen" by the thermostat.
Is the only way to resolve this buying a thermostat who talks OT directly to the CV or are there other methods?

thx for any help

willem

Re: Open Therm Thermostat instead of a gateway translating the stuff

Posted: Thursday 12 January 2017 12:15
by CaptainSlow
In addition...is there anybody who has a setup where the thermostat also understands / reads when an open therm command is sent with domoticz to the OTGW?
Example: I set the the room temp for instance from 19,5 degrees to 20 with domoticz via OTGW. My thermostat does not see it. any examples where this works? do I need to have a full open therm thermostat for that like the Nest or the I or q sense?

thx in advance

willem

Re: Open Therm Thermostat instead of a gateway translating the stuff

Posted: Saturday 03 March 2018 20:38
by pwhooftman
I have a Remeha Calenta heater with an iSense thermostat, the iSense talks Opentherm. The OTGW is placed in between the thermostat and the heater, and acts as a passthrough device between thermostat and heater. Domoticz reads all relevant values (water temp, room temp etc) by querying the OTGW periodically. In Domoticz, an thermostat setpoint device is added which represents the actual thermostat setpoint. When the setpoint is changed in domoticz, the iSense reflects this change after several seconds (up to 1 minute) delay.

One cavecat: if the setpoint is changed on the iSense manually or by the programmed schedule in the iSense, the change in the setpoint isnt represented in domoticz.