hvxl wrote:
In the Opentherm Protocol the thermostat is the master, so that's the part that controls which Data Id's are exchanged. That is not something the slave can alter, at least not according to version 2.2 of the protocol. Again, if this has changed in a later version of the protocol, I would need the details to be able to implement it. So that is almost certainly not going to happen in the near future.
Schelte.
My mistake. What I meant to say was having the Opentherm gateway reply to a certain Data-id with a user defined Data-Id. I want to fool the Honeywell Vision Modulation thermostat thinking it is connected to a ventilation device. (I want to enable the ventilation function of the Honeywell Vision Modulation thermostat. I think it uses the Data-Id range 70 to 91.)
I surely wil sniff for these Data-Id's.
Code: Select all
; New ID for ventilation/heat-recovery applications
70,"STATUS V/H",READ,FLAG,00000000,FLAG,00000000,Yes
71,"CONTROL SETPOINT V/H",WRITE,U8,0,100,0,Yes
72,"FAULT FLAGS/CODE V/H",READ,FLAG,00000000,U8,0,255,0,Yes
73,"DIAGNOSTIC CODE V/H",READ,U16,0,65000,0,Yes
74,"CONFIG/MEMBERID V/H",READ,FLAG,00000000,U8,0,255,0,Yes
75,"OPENTHERM VERSION V/H",READ,F8.8,0,127,"2,32",Yes
76,"VERSION & TYPE V/H",READ,U8,0,255,1,U8,0,255,0,Yes
77,"RELATIVE VENTILATION",READ,U8,0,255,0,Yes