Gateway hangs

[rtenklooster]

Hi,
Running my gateway, connected to a rPi.
I'm having some stability problems every now and then.
The problem is, the gateway, directly connected to opentherm monitor spits out some serial activity like:

Code: Select all

22:48:58.863125  Error 03
22:59:01.055978  0/0100000011/00000011,100.01505.,2,1000010,1.,500,7,001100.0/00/,,,0.0,,.,0201,00,105,5.0,000,,,0101,05,.2650/0,,,,0005010/80.06520,101005.01005256208,7,000015,0./2015.8500000,0/5,000520808500010017,1/00588,0.8500,000.000/176,0.0,020/0,010/207500./00,00007,11,,2,,150,,,01010.01.2,,090685,1015,0052.708/0,09,007,0011330.45,0900/00500./0,06,,0,00/0,11,00,6,0,00007,/05,2.5..660,,0200/0700150.0.0.52000,0105,,170/0,85/20,60.00,75.00,0,0,0,0,0,19200,0,0
22:59:27.470665  Error 02
23:01:01.091697  0100,000011/00000011,100.00,2.,1500,0200007,0,..2.,7/00010001015,0/1,02565001,00/00,00/.02/1.80.26,75.13,71.25,0.00,68.25,65/40,85/20,60.00,75.00,0,0,0,0,0,19200,0,0
23:01:06.995376  Error 04
23:01:28.315520  Error 04
23:02:01.107058  001,0000011/00000011,10,,50.0.,0,20/01.0/055/10,21.00,8.00,1.86,20.26,75.13,71.25,0.00,68.50,65/40,85/20,60.00,75.00,0,0,0,0,0,19200,0,0
23:02:27.026771  Error 04
23:02:31.092221  Error 04
23:05:01.158403  0/005000011/00000011,100.067208,0000020017000,.210,58,5,0,,0/015000/172302.,,9,00,00000/,0810/0000010.00.20.6,,,/5,,,0010,75.00,00000011/00000011,100.00,255/10,21.00,0.00,1.56,20.18,75.63,71.50,0.00,68.75,65/40,85/20,60.00,75.00,0,0,0,0,0,19200,0,0
23:09:41.521374  Command (via websocket from 192.168.1.14:52134): PR=A

But it's not responding to any incoming serial commands.
I have restarted the rPi, but that's not the solution. Of i try to request the gateway settings i receive a timout.
In this case the solution is powering down the gateway, wait a minute and restart.

[hvxl]

Can you reveal a bit about your setup? The output you showed looks like it has parts of PS=1 reports. Do you use that or are you normally running in PS=0 mode? Do you have multiple applications that talk to the gateway? If so, how is that orchestrated? Do you have logs that start when everything still works fine and cover the moment when it starts to go wonky?

This is a bit reminiscent of a problem that was fixed in 4.0b0. You don't happen to be running some ancient firmware, are you?