iSense and Elco Thision
Posted: Sun Dec 08, 2013 12:59 pm
Hi Guys,
I'm new here to this forum and my question maybe is somewhat off topic, hope you apologize for that.
Running an opentherm gateway for about a year now and it works great. I'm using an Elco Thision S and the Siemens QAA73.
Because of the "Remote override room setpoint" problem with the QAA I was looking for a replacement. Some weeks ago I found a Remeha iSense for a reasonable price on ebay and bought it. Wikipedia says "A controller from manufacturer A may be used to control a boiler from manufacturer B" and so I was confident that this combination will work. But it does not. The boiler starts the burner and stops a few seconds later with error 129. The manual does not cover this error and Elco refuses to explain it to me as a "non-expert".
In OpenTherm-Monitor I saw that the QAA and the Thision were talking some "reserved" Opentherm-IDs which the iSense don't do.
Has anybody running this combination successfull? Or is it possible for the gateway to "inject" some of these reserved IDs into the communication? Or do anybody know what error 129 means?
Thanks in advance for any help,
Titus
P.S. I can provide a log from Opentherm-Monitor if it is helpful.
I'm new here to this forum and my question maybe is somewhat off topic, hope you apologize for that.
Running an opentherm gateway for about a year now and it works great. I'm using an Elco Thision S and the Siemens QAA73.
Because of the "Remote override room setpoint" problem with the QAA I was looking for a replacement. Some weeks ago I found a Remeha iSense for a reasonable price on ebay and bought it. Wikipedia says "A controller from manufacturer A may be used to control a boiler from manufacturer B" and so I was confident that this combination will work. But it does not. The boiler starts the burner and stops a few seconds later with error 129. The manual does not cover this error and Elco refuses to explain it to me as a "non-expert".
In OpenTherm-Monitor I saw that the QAA and the Thision were talking some "reserved" Opentherm-IDs which the iSense don't do.
Has anybody running this combination successfull? Or is it possible for the gateway to "inject" some of these reserved IDs into the communication? Or do anybody know what error 129 means?
Thanks in advance for any help,
Titus
P.S. I can provide a log from Opentherm-Monitor if it is helpful.