Setback override from unknown trigger
Posted: Sun Jan 01, 2017 1:44 pm
We have installed the OpenTherm Gateway in our weekend home. (heater: Vaillant hrPRO; thermostat: Honeywell Chronoterm Touch Modulation; Raspberry 2B, OT monitor 4.3, OT gateway 4.2.5, outside temp sensor DS18B20).
The Otgw is operational for a few months. After some initial problems it is pretty stable now. One issue remains however. About once a week we see a Setback constant temp override. We have no idea what triggers this.
I expect a relation with the outside temp sensor, that is, the issue did not appear when the outside sensor was not connected and not configured (GA and GB default value 0).
The now connected outside temp sensor is configured with GA=2 (Vcc) and GB=7 (DS1820) and works fine.
If the Setback function is used, this works also via the GPIO A or B port (config 5 or 6). But in our configuration the GPIO ports are set for the outside temp sensor.
Looking into the Otgw assembler source code, in the main loop the GPIO ports are scanned, and via the GPIO config number a line in a jump table is selected that executes some code. Apparently for some reason not known the code for GPIO option 6 ('Away') is selected, which generates a constant temp override.
From the data in the datalog, no pattern can be found in time and conditions when the override happens.
Anybody any idea or suggestion what might trigger the Setback override ?
The Otgw is operational for a few months. After some initial problems it is pretty stable now. One issue remains however. About once a week we see a Setback constant temp override. We have no idea what triggers this.
I expect a relation with the outside temp sensor, that is, the issue did not appear when the outside sensor was not connected and not configured (GA and GB default value 0).
The now connected outside temp sensor is configured with GA=2 (Vcc) and GB=7 (DS1820) and works fine.
If the Setback function is used, this works also via the GPIO A or B port (config 5 or 6). But in our configuration the GPIO ports are set for the outside temp sensor.
Looking into the Otgw assembler source code, in the main loop the GPIO ports are scanned, and via the GPIO config number a line in a jump table is selected that executes some code. Apparently for some reason not known the code for GPIO option 6 ('Away') is selected, which generates a constant temp override.
From the data in the datalog, no pattern can be found in time and conditions when the override happens.
Anybody any idea or suggestion what might trigger the Setback override ?