Strange/unstable connection between OTGW and Brink HR

[raf]

Hello,
I have Opentherm Gateway by Nodo shop connected to Brink Renovent HR (ventilation) in stand-alone mode with OTGW firmware version 5.1
I am testing it with otmonitor (TCP IP connection) before connecting to Openhab. I have few Alternative Data Ids defined (AA=70,AA=71,AA=77,AA=80, AA=82, )
I am observing a very strange behavior as follows:
After connecting and putting the gateway mode of the otmonitor (@ 17: 11) it is trying to read MsgID=0 several times over hours:

Code: Select all

17:11:39.963327  R00000000  Read-Data   Status (MsgID=0): 00000000 00000000
                               - CH enable: disabled (0)
                               - DHW enable: disabled (0)
                               - Cooling enable: disabled (0)
                               - OTC active: not active (0)
                               - CH2 enable: disabled (0)
                               - Summer/winter mode: winter (0)
                               - DHW blocking: unblocked (0)
...

Then after ~houes ( @19.04 ) it provides info that MsgID=0 is UnknownData (which I think is true in my case as I use Ventilation only?). Then PR=A message is generated software starts to provide other messages (fixed series and user defined) as expected:

Code: Select all

19:04:40.271601  BF0000000  Unk-DataId  Status (MsgID=0): 00000000 00000000
19:04:40.281941  Command: PR=A
19:04:40.355945  PR: A=OpenTherm Gateway 5.1
19:04:41.187522  R80190000  Read-Data   Boiler water temperature (MsgID=25): 0.00
19:04:41.241491  B70190000  Unk-DataId  Boiler water temperature (MsgID=25): 0.00
19:04:42.216974  R10010000  Write-Data  Control setpoint (MsgID=1): 0.00
…

It works about 10 minutes and @ 19.12 it has difficulties to readMsgID=82

Code: Select all

19:12:45.640194  R80520000  Read-Data   Exhaust inlet temperature (MsgID=82): 0.00
19:12:46.614284  R80520000  Read-Data   Exhaust inlet temperature (MsgID=82): 0.00
19:12:47.621675  R80520000  Read-Data   Exhaust inlet temperature (MsgID=82): 0.00
19:12:48.621006  R80520000  Read-Data   Exhaust inlet temperature (MsgID=82): 0.00
...

Then @19:22 it start again to provide expected messages:

Code: Select all

19:22:38.993512  B405214CC  Read-Ack    Exhaust inlet temperature (MsgID=82): 20.80
19:22:39.880533  R900E6400  Write-Data  Maximum relative modulation level (MsgID=14): 100.00
19:22:39.991410  BF00E6400  Unk-DataId  Maximum relative modulation level (MsgID=14): 100.00
19:22:40.947075  R80460000  Read-Data   Status V/H (MsgID=70): 00000000 00000000
                               - Ventilation: disabled (0)
                               - Bypass position: close (0)
....

It works 50 minutes and @20:20 it tries to write MsgID=1 with hundred of lines:

Code: Select all

20:12:44.971566  R10010000  Write-Data  Control setpoint (MsgID=1): 0.00
20:12:45.927355  R10010000  Write-Data  Control setpoint (MsgID=1): 0.00
20:12:46.920736  R10010000  Write-Data  Control setpoint (MsgID=1): 0.00
.....

Then @ 20:13 it seems to restart:

Code: Select all

20:13:49.833608   OpenTherm Gateway 5.1
20:13:49.844740  Thermostat disconnected
20:13:50.735382  R00000000  Read-Data   Status (MsgID=0): 00000000 00000000
                               - CH enable: disabled (0)
                               - DHW enable: disabled (0)
                               - Cooling enable: disabled (0)
                               - OTC active: not active (0)
                               - CH2 enable: disabled (0)
                               - Summer/winter mode: winter (0)
                               - DHW blocking: unblocked (0)
….

and similar (but not exactly the same) pattern repeats again preventing proper usage

Any hints what could be a cause of such a strange behavior?
What shall I investigate further to find the root cause?