Home Automation Domotica Forum Europe, Bwired Forum

Posted: **Thu Feb 24, 2022 7:13 pm**

Firmware version 5.3 is now available on the web site.

Posted: **Sun Feb 27, 2022 11:55 am**

Just installed the latest firmware. Thanks for fixing this so fast. And man! i love the over the air upgrade option. 15 seconds and its done.

Thank you for all the great work!

Posted: **Wed Mar 02, 2022 4:11 pm**

Just to report that I also just encountered a case where the OTGW went into a freeze up and required a power cycle to restart it.

In my case I am (was) using the following configuration..

- OTGW F/W v5.2
- Driving a Viessmann Vitodens 100 boiler
- No thermostat connected
- Using OpenHAB binding (PR #12367) https://github.com/openhab/openhab-addons/pull/12367 to send CS and CH commands

I have been running it about two weeks and I only had this freeze up once. So it fits into your estimate about the bug occurring 1 in 1000 times. Because of the new feature of v5.2 (Limit the validity of a CS command. A remotely set control setpoint expires after just over a minute) I have to send the CS command every 30 seconds, so therefore the 1 in 1000 times could occur more frequently than if CS would be only sent when its value actually needs to be changed (i.e. sending CS every 30 seconds instead of about every 30 minutes).

=> I will load v5.3 now and let you know if the problem will have been solved.

Posted: **Sun Mar 06, 2022 1:33 pm**

A couple of days ago I posted a response to this thread saying that I had also encountered this lockup error; but it seems that post was not (yet) approved ??

Anyway, I want to report that I did upgrade the firmware to v5.3 when I made that post. However unfortunately even with v5.3 installed I encountered the same lockup again today. The symptoms are the same as previously reported, namely after sending CH and CS commands, the 'Boiler Maintenance' LED ligts up, the OpenTherm TX and RX communications stop, and the serial port comms (in my case over the USR-TCP232 module) stop.

I don't have any OTGW logs, but in case it helps, you can see my openHAB logs below. Note: to interpret this log: when you see the 'Central Heating Enabled at xx.x°C' message, the openHAB binding sends a CS setpoint command followed by a respective CH on command; and every 30 seconds thereafter, if the setpoint has not changed, the binding repeats sending the exact same CH and CS values..

```
2022-03-06 08:38:10.603 [INFO ] [org.openhab.core.model.script.Rules ] - Central Heating Enabled at 55.2°C (was 55.1°C)
2022-03-06 08:39:10.596 [INFO ] [org.openhab.core.model.script.Rules ] - Central Heating Enabled at 55.1°C (was 55.2°C)
2022-03-06 08:39:50.610 [INFO ] [org.openhab.core.model.script.Rules ] - Central Heating Enabled at 55.0°C (was 55.1°C)
2022-03-06 08:49:50.597 [INFO ] [org.openhab.core.model.script.Rules ] - Central Heating Enabled at 50.0°C (was 55.0°C)
... repeats sending the same CH on and CS = 50.0 commands every 30 seconds (in my case sent commands are not written to the log file if the values did not change from the prior command values)
2022-03-06 09:19:27.717 [WARN ] [rnal.OpenThermGatewaySocketConnector] - Error communicating with OpenTherm Gateway: 'Read timed out'
```

Posted: **Sun Mar 06, 2022 2:20 pm**

> If an interrupt happens to fire at that deepest level and the interrupt routine decides to update some LED state, that adds 3 more levels

Just for info: I have the following LEDs settings..

A = Flame Status
B = CH Status
C = DHW Status
D = Boiler Maintenance
E = GPIO A = Opentherm TX
F = GPIO B = Opentherm RX

So when the openHAB binding sends the CS and CH commands every 30 seconds it may be triggering some of these LEDs and GPIO pins at the same time. So perhaps one work around may be to disable the LEDs, or assign them to monitor a different state. => Any thoughts??

Posted: **Mon Mar 07, 2022 1:56 am**

It doesn't matter if the function is assigned to a LED or not. The subroutine is always called to update the function state. That's necessary for the LED to immediately show the proper state when a new function is assigned.

But why are you looking for work-arounds when a solution for the problem is already available?

Posted: **Wed Mar 09, 2022 10:36 am**

Ok. Thanks for the feedback about the LEDs.

I think the problem is worse in v5.3 than it was in v5.2; on the former, I had it lock up once in about two weeks whereas on v5.3 I have had it lock up twice in one week.

Do you think that the problem with the floating point calculation might depend on the number of places of decimals in the CS command? In the case of the OpenHAB binding, the math calculations for the setpoint are done with 8 places of decimals precision; obviously that is way more than necessary, and I could try rounding to just one place of decimals in case that might make a difference. ??

Posted: **Wed Mar 09, 2022 1:51 pm**

Are you implying that the fix doesn't work? Are you sure you are experiencing the same problem? With 2 stack levels less, that shouldn't be possible.

An excessive amount of decimal places doesn't increase the recursion depth. Only the first 2 digits are really used, with the 3rd only for rounding. Everything after that is discarded.

Posted: **Wed Mar 09, 2022 2:19 pm**

hvxl wrote:Are you implying that the fix doesn't work?

Yes.

hvxl wrote:Are you sure you are experiencing the same problem?

Well I suppose to be quite strict, I have no way to know if it is the same internal problem in the code, but I certainly observe exactly the same external symptoms as the OP did..

A. The OpenHAB binding connects over the serial port, and registers to receive PS reports, and then sends one CS "setpoint" plus one CH "on" resp. "off" command every 30 seconds; the OpenHAB binding does not send anything else; and there is no thermostat attached, so nothing being forwarded from that side.

B. This setup works perfectly for about 2..3 days, and then,

C. The OTGW goes into a lockout state where the Boiler Maintenance LED turns on, the OTGW ceases sending PS messages on the serial port, and it ceases sending and receiving messages on the OpenTherm bus (i.e. no TX or RX LED activity).

D. And the only way to restore operation is to power cycle the OTGW.

Posted: **Wed Mar 09, 2022 2:30 pm**

Please provide a log. Then maybe I can determine if it is the same internal problem.

Posted: **Wed Mar 09, 2022 3:04 pm**

^

the Boiler Maintenance LED turns on

...and for the avoidance of doubt, I can confirm that in the received PS MsgID=0 messages there was never a message received with bit 0 set; so I think that rules out the boiler maintenance LED being caused by an error in the boiler....

Posted: **Wed Mar 09, 2022 4:04 pm**

hvxl wrote:Please provide a log.

Ok I would be happy to do that. But before I start logging something that might be wrong for you, perhaps you can let me know what exact information you want to see via this specific OpenHAB setup? The OpenHAB binding is connecting as a client to the serial port via the USR-TCP232 server, and running the Java pseudo code below; important is to note that it is operating in PS=0 mode..

So I guess it is sufficient if I make a verbatim dump of the payloads of the below mentioned socket.write() and socket.readln() calls? In any case I shall probably have to make code changes in the OpenHAB binding so if there is anything else that your need, please let me know. ??

Alternatively I could connect TWO clients to the OTGW USR-TCP232 server -- namely 1) the OpenHAB binding (running the code below), and also b) the OTMonitor monitor app to doing the logging. The USR-TCP-232 server will accept more that one client connections, but I am not 100% sure that the second connection always mirrors the exact same data as the first? => So please advise, either way..

Code: Select all

// TCP serial port POLLING thread
socket.write("PR=A\r\n");
socket.write("PS=0\r\n);
while (!interrupted) {
   inputString = socket.readln();
   doSomethingWith(inputString);
}

Code: Select all

// TCP serial port COMMAND thread
while (!interrupted) {
   socket.write("CS=" + setPoint.toString() +"\r\n"); // setpoint values between 50.0 and 65.0 (enabled) resp. 0.0 (disabled)
   socket.write("CH="  +  (isEnabled ? "1" : "0") + "\r\n"); 
   sleep(30000);
}

Posted: **Wed Mar 09, 2022 4:33 pm**

PS=0 is exactly what I want. In general, the best log for me is obtained if OTmonitor connects to the OTGW and other programs connect to the OTmonitor relay server port. That way the messages are reported with a time stamp and commands to the OTGW are also logged. Disable at least the "include details of bit fields" option to reduce the size of the log.

Some people have reported that OTmonitor crashes when left running for a long time. Unfortunately, none of them have ever responded to my follow-up questions about their setup and suggestions to improve the situation. I still suspect that the GUI is the main culprit. So you may want to run OTmonitor without a GUI, if you are going this route.

For this issue I suspect timing is not really important, so capturing all traffic between OpenHAB and the OTGW should be sufficient. But if you can easily add a time stamp (in microseconds, if possible), that would be even better.

As the least preferred option, connecting OTmonitor in parallel to the USR-TCP232 is also possible. Any log is better than nothing. But in this case the commands will not be logged, so that leaves some guesswork.

Posted: **Wed Mar 09, 2022 5:35 pm**

The following is an example of the kind of 'sl4j' log that I could produce (showing 2 of the 30 second command cycles). => Would that be OK?
If I let this run for a few days we may then see the point at which the error occurs (this is on my live home automation system so there might be few extraneous log entries from other things interleaved).

Code: Select all

2022-03-09 15:19:10.418 [TRACE] [rnal.OpenThermGatewaySocketConnector] - write: CS=50.0
2022-03-09 15:19:10.429 [TRACE] [rnal.OpenThermGatewaySocketConnector] - write: CH=1
2022-03-09 15:19:10.450 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: CS: 50.00
2022-03-09 15:19:10.476 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: CH: 1
2022-03-09 15:19:11.203 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00780000
2022-03-09 15:19:11.340 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC078160E
2022-03-09 15:19:12.228 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00110000
2022-03-09 15:19:12.439 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0110000
2022-03-09 15:19:13.262 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R001B0000
2022-03-09 15:19:13.452 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B601B0000
2022-03-09 15:19:14.289 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R801A0000
2022-03-09 15:19:14.464 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC01A2E19
2022-03-09 15:19:15.314 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R900E6400
2022-03-09 15:19:15.467 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B500E6400
2022-03-09 15:19:16.341 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00740000
2022-03-09 15:19:16.476 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40740632
2022-03-09 15:19:17.366 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100
2022-03-09 15:19:17.596 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0000102
2022-03-09 15:19:18.401 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80190000
2022-03-09 15:19:18.600 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40192E33
2022-03-09 15:19:19.427 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R90013200
2022-03-09 15:19:19.610 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B50013200
2022-03-09 15:19:20.448 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80380000
2022-03-09 15:19:20.601 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0383700
2022-03-09 15:19:21.472 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00390000
2022-03-09 15:19:21.608 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0394100
2022-03-09 15:19:22.498 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00780000
2022-03-09 15:19:22.726 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC078160E
2022-03-09 15:19:23.516 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R801A0000
2022-03-09 15:19:23.737 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC01A2E19
2022-03-09 15:19:24.542 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100
2022-03-09 15:19:24.744 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0000102
2022-03-09 15:19:25.568 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80190000
2022-03-09 15:19:25.758 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0192DE6
2022-03-09 15:19:26.595 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R90013200
2022-03-09 15:19:26.762 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B50013200
2022-03-09 15:19:27.618 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00740000
2022-03-09 15:19:27.770 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40740632
2022-03-09 15:19:28.641 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00110000
2022-03-09 15:19:28.875 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0110000
2022-03-09 15:19:29.682 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R001B0000
2022-03-09 15:19:29.877 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B601B0000
2022-03-09 15:19:30.701 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00780000
2022-03-09 15:19:30.891 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC078160E
2022-03-09 15:19:31.725 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R900E6400
2022-03-09 15:19:31.894 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B500E6400
2022-03-09 15:19:32.752 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R801A0000
2022-03-09 15:19:32.903 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC01A2E19
2022-03-09 15:19:33.776 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100
2022-03-09 15:19:33.912 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0000102
2022-03-09 15:19:34.806 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80190000
2022-03-09 15:19:35.028 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0192DE6
2022-03-09 15:19:35.835 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R90013200
2022-03-09 15:19:36.037 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B50013200
2022-03-09 15:19:36.866 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80380000
2022-03-09 15:19:37.046 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0383700
2022-03-09 15:19:37.885 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00390000
2022-03-09 15:19:38.060 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0394100
2022-03-09 15:19:38.911 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00740000
2022-03-09 15:19:39.064 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40740632
2022-03-09 15:19:39.934 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00780000
2022-03-09 15:19:40.166 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC078160E
2022-03-09 15:19:40.971 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100
2022-03-09 15:19:41.169 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0000102
2022-03-09 15:19:41.992 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80190000
2022-03-09 15:19:42.181 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0192DE6
2022-03-09 15:19:43.016 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R90013200
2022-03-09 15:19:43.185 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B50013200
2022-03-09 15:19:44.044 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R801A0000
2022-03-09 15:19:44.197 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC01A2E19
2022-03-09 15:19:45.065 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00110000
2022-03-09 15:19:45.202 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0110000
2022-03-09 15:19:46.090 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R001B0000
2022-03-09 15:19:46.318 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B601B0000
2022-03-09 15:19:47.126 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00740000
2022-03-09 15:19:47.326 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40740632
2022-03-09 15:19:48.149 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R900E6400
2022-03-09 15:19:48.334 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B500E6400
2022-03-09 15:19:49.175 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00780000
2022-03-09 15:19:49.343 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC078160E
2022-03-09 15:19:50.201 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100
2022-03-09 15:19:50.333 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0000102
2022-03-09 15:19:50.423 [TRACE] [rnal.OpenThermGatewaySocketConnector] - write: CS=50.0
2022-03-09 15:19:50.431 [TRACE] [rnal.OpenThermGatewaySocketConnector] - write: CH=1
2022-03-09 15:19:50.457 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: CS: 50.00
2022-03-09 15:19:50.458 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: CH: 1
2022-03-09 15:19:51.225 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80190000
2022-03-09 15:19:51.453 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40192D99
2022-03-09 15:19:52.257 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R90013200
2022-03-09 15:19:52.458 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B50013200
2022-03-09 15:19:53.281 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80380000
2022-03-09 15:19:53.466 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0383700
2022-03-09 15:19:54.311 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00390000
2022-03-09 15:19:54.586 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0394100
2022-03-09 15:19:55.326 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R801A0000
2022-03-09 15:19:55.596 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC01A2E19
2022-03-09 15:19:56.350 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00740000
2022-03-09 15:19:56.583 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40740632
2022-03-09 15:19:57.375 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100
2022-03-09 15:19:57.590 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0000102
2022-03-09 15:19:58.399 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80190000
2022-03-09 15:19:58.711 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0192D80
2022-03-09 15:19:59.434 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R90013200
2022-03-09 15:19:59.714 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B50013200
2022-03-09 15:20:00.457 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00780000
2022-03-09 15:20:00.723 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC078160E
2022-03-09 15:20:01.486 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00110000
2022-03-09 15:20:01.738 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC0110000
2022-03-09 15:20:02.506 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R001B0000
2022-03-09 15:20:02.742 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B601B0000
2022-03-09 15:20:03.532 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R801A0000
2022-03-09 15:20:03.749 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: BC01A2E19
2022-03-09 15:20:04.558 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R900E6400
2022-03-09 15:20:04.757 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B500E6400
2022-03-09 15:20:05.585 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R00740000
2022-03-09 15:20:05.766 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: B40740632
2022-03-09 15:20:06.606 [TRACE] [rnal.OpenThermGatewaySocketConnector] - read: R80000100

Posted: **Wed Mar 09, 2022 5:43 pm**

That will do quite nicely. I can easily remove the extra crud with a sed script. The "other things" may actually trigger the problem, so it's good that they will also be logged.

I thought you said the CS command had 8 decimal places of precision. That is not reflected by this log.

Home Automation Domotica Forum Europe, Bwired Forum

OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error

Re: OTGW system error