Bad News.
The otgw was working well with the new PIC for about a month. Since last week I've got the same issues as before: no new messages in the logfile while the red led is turned on. And once again it overrode the room setpoint to 67 degrees and the room thermostate indicated an OT error.
The last lines in the logfile:
Code: Select all
19:50:31.362262 WDT reset!
19:50:31.364953 0
19:50:31.374704 0010A00
19:50:31.383017 0010A00
19:50:31.392691 0000200
19:50:31.402432 0000204
22:54:56.499200 090000enT
06:36:01.507110 herm Gateway 4.2.5
06:36:01.519571 WDT reset!
06:36:01.522431 0
06:36:01.532049 0010A00
06:36:01.540286 0010A00
06:36:01.550041 0000200
06:36:01.559686 0000204
06:36:01.590190 090000enTherm Gateway 4.2.5
06:36:01.602686 WDT reset!
06:36:01.605412 0
06:36:01.615049 0010A00
06:36:01.623416 0010A00
06:36:01.633158 0000200
06:36:01.642782 0000204
06:36:01.673308 090000enTherm Gateway 4.2.5
06:36:01.685688 WDT reset!
06:36:01.688556 0
06:36:01.698176 0010A00
06:36:01.706537 0010A00
06:36:01.716159 0000200
06:36:01.725936 0000204
06:36:01.902741 090000enTherm Gateway 4.2
... repeated many times, sometimes with interval of some hours
Dbus info:
Code: Select all
dbus-send --dest=com.tclcode.otmonitor --print-reply / com.tclcode.debug.Eval ':set errorInfo'
method return time=1591607792.719618 sender=:1.0 -> destination=:1.1 serial=8 reply_serial=2
string "can not find channel named "sockbfc9a0"
while executing
"chan close sockbfc9a0"
invoked from within
"catch $script""
dbus-send --dest=com.tclcode.otmonitor --print-reply / com.tclcode.debug.Eval ':fconfigure $dev'
method return time=1591607813.828990 sender=:1.0 -> destination=:1.2 serial=9 reply_serial=2
string "-blocking 0 -buffering line -buffersize 4096 -encoding utf-8 -eofchar {{} {}} -translation {crlf cr} -mode 9600,n,8,1 -xchar { }"
dbus-send --dest=com.tclcode.otmonitor --print-reply / com.tclcode.debug.Eval ':fileevent $dev readable'
method return time=1591607825.451036 sender=:1.0 -> destination=:1.3 serial=10 reply_serial=2
string "receive"
That was when the room setpoint went to 67 degrees.
Today there was a slightly different lgofile:
Code: Select all
12:16:21.083926 T00110000 Read-Data Relative modulation level: 0.00
12:16:21.208919 BC0110000 Read-Ack Relative modulation level: 0.00
12:16:21.997443 192000
12:16:22.007204 0010A00
12:16:22.015426 0010A00
12:16:22.025160 0000200
12:16:22.034780 0000204
12:16:22.044554 0000200
12:16:22.052786 0000204
12:16:22.062542 0110000
12:16:22.072174 0110000
12:16:22.080548 192000
12:16:22.090180 0010A00
12:16:22.098583 0010A00
12:16:22.108188 0000200
12:16:22.117964 0000204
12:16:22.127538 0000200
12:16:22.135912 0000204
12:16:22.145654 0110000
12:16:22.155290 0110000
12:16:22.163537 192000
12:16:22.173295 0010A00
12:16:22.181734 0010A00
12:16:22.191287 0000200
12:16:22.201036 0000204
12:16:22.210668 0000200
12:16:22.218941 0000204
12:16:22.228692 0110000
12:16:22.238426 0110000
12:16:22.246658 192000
12:16:22.256417 0010A00
12:16:22.264653 0010A00
12:16:22.376183 0T80000200
12:17:26.364559 OpenTherm Gateway 4.2.5
12:17:26.374135 WDT reset!
After the WDT reset! there where no other messages and the red led was turned on.
Temperatures of the the components on the otgw are all within reasonable ranges.
Any suggestions?