Opentherm Gateway 4.0 alpha/beta testers wanted

[hvxl]

Looking at the schema, it seems not required when omitting the thermostat, but only Schelte will be able to confirm.

Not sure why I would be the only one who can confirm. But yes, if you don't intend to connect a thermostat, you don't need the 24V.

[hvxl]

I tried to upload a logfile but failed.

The log file parser was having trouble with some of the new additions of the 4.0 beta versions of otmonitor. I have corrected that and uploaded your logs to confirm it works now. Thanks.

[Templar]

The log file parser was having trouble with some of the new additions of the 4.0 beta versions of otmonitor. I have corrected that and uploaded your logs to confirm it works now. Thanks.

Thanks.
By the way, Intergas spells Kompakt with two k 's.

[hvxl]

By the way, Intergas spells Kompakt with two k 's.

Korrekted Thanks again.

[sappien]

@hvxl

I get a error when I look at the graph (when using otmonitor in daemon mode)

Code: Select all

*** INTERNAL SERVER ERROR (BEGIN #1) ***
socket: sock8523978
peerhost: 192.168.1.230
peerport: 54633
port: 8080
rawtime: 1390386467
time: Wed Jan 22 11:27:47 CET 2014
method: GET
uri: /graph.svg
path: /graph.svg
protocol: HTTP/1.1
rawheader: {Host: 127.0.0.1:8080} {Connection: keep-alive} {Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8} {User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.76 Safari/537.36} {Referer: http://127.0.0.1:8080/graph.html} {Accept-Encoding: gzip,deflate,sdch} {Accept-Language: nl-NL,nl;q=0.8,en-US;q=0.6,en;q=0.4,af;q=0.2,de;q=0.2,lt;q=0.2}
header host: 127.0.0.1:8080
header connection: keep-alive
header accept: text/html {} application/xhtml+xml {} application/xml {q 0.9} image/webp {} */* {q 0.8}
header user-agent: Mozilla/5.0 {(Windows NT 6.3; WOW64)} AppleWebKit/537.36 {(KHTML, like Gecko)} Chrome/32.0.1700.76 Safari/537.36
header referer: http://127.0.0.1:8080/graph.html
header accept-encoding: gzip {} deflate {} sdch {}
header accept-language: nl-nl {} nl {q 0.8} en-us {q 0.6} en {q 0.4} af {q 0.2} de {q 0.2} lt {q 0.2}
accept type: text/html application/xhtml+xml image/webp application/xml */*
accept charset: 
accept encoding: gzip deflate sdch
accept language: nl-nl nl en-us en af de lt
accept transfercoding: 
errorinfo: can't read "track(dhwmode)": no such variable
    while executing
"lindex $track($name) 1"
    ("dict for" body line 5)
    invoked from within
"dict for {name data} $line {
             set coords {}
             set color [dict get $data color]
             set title [dict get $data name]
   ..."
    (body of "dict with")
    invoked from within
"dict with dict {
         set zero [expr {$y + $max * $zoom}]
append # [subst {<!-- Horizontal lines -->
}]
         for {set v $min} {$v <= $max} {in..."
    ("dict for" body line 3)
    invoked from within
"dict for {group dict} $graph {
     incr y 8
     dict with dict {
         set zero [expr {$y + $max * $zoom}]
append # [subst {<!-- Horizontal lines..."
    ("uplevel" body line 27)
    invoked from within
"uplevel 1 "set # {}; $script; set #""
    (procedure "template" line 17)
    invoked from within
"template $body"
    (procedure "::wibble::zone::templatefile" line 8)
    invoked from within
"{*}$command $state"
    (procedure "getresponse" line 38)
    invoked from within
"getresponse $request"
*** INTERNAL SERVER ERROR (END #1) ***

[hvxl]

I get a error when I look at the graph (when using otmonitor in daemon mode)

This happens if you request the graph before otmonitor has had a chance to collect at least one data point for each parameter in the graph. I will fix it in the next version.

[Domoticus]

The gateway is not showing the Return Water Temp with PS=1.

I'm using 4.0b1. I have a Remeha Avanta with a Honeywell round modulation thermostat.
I added the option to show Return Water Temperature with AA=28.
I now request the info via PS=1

PS: 1 00000011/00000010,33.00,00000011/00000011,100.00,0/0,22.50,0.00,0.00,22.97,29.98,0.00,11.50
sometimes it also cuts the last 2 digits of the faked Outside temperature: (I sent OT=11.50)
PS: 1 00000011/00000010,33.00,00000011/00000011,100.00,0/0,22.50,0.00,0.00,22.97,29.98,0.00,11.
And only once in the +/-20 times I see the Return Temperature added at the end. (Quick check on the boiler learnt me it was indeed the correct value by then).
(also the Outside Temperature is staying "11.50", even if I send OT=99, with response OT: - )

(BTW, I want to thank you for sharing this great product!)

[hvxl]

Both PS reports you show are cut short, the outside temperature is not the last parameter that it supposed to be reported. There are 13 more. And there should be a newline after the PS: 1. I am unable to reproduce the effects you describe, I always get complete reports. How do you collect the output from the gateway?

The firmware indeed doesn't clear the outside temperature value when you send OT=99. Clearing the value doesn't make any more sense than leaving it at the last known value because both are valid outside temperatures. What would you have expected to happen?

[Domoticus]

I'm very sorry. fault was not in the Gateway.
It was in my serial software: php_serial.class.php. which i use to get the data in my Synology NAS.
It timed out before the gateway's answer was complete.
I enlarged the time and its working fine now!
Sorry for your time, I hope to contribute in other ways soon.

[OTGvis]

Using Bosch HRC 30 I have many Error 01 (about once a sec) with 3.4 in GW mode. Just upgrade the OTG to 4.0b3.
After the upgrade the Diagmostic window only showed a Txxxxx message and underneath Error 01. Over and over again, nothing else so all communication failed.

Then I checked the option Tools > Setting : Ignore multiple mid-bit transitions and immediately communication started again and no more Error 01.

So things are working now as before, the OTG monitor looks good and information is shown again in VeraLite. Still it seems not possible to overrule the Thermostat setting using OTG .

Conclusion: the Error 01 is gone now, good work!, still looking for a way to overrule the temp settings on my Bosch.

[cyberde]

I've just updated to 4.0b3 and noticed that the command TC=temperature doesn't work anymore with my Honywell round thermostate.
Sending the command results in correct answer though, but the setpoint doesn't change (not even after more than two hours of waiting)

TC=20.5
TC: 20.50
PS=1
PS: 1
00000010/00000000,10.00,00000000/00000000,0.00,0/0,20.00,0.00,0.00,19.88,34.00,0.00,5.70,0.00,0/0,0/0,0.00,80.00,546720,0,0,278580,6310,0,0,0

Will flash back to 4.0b2 later today and will check if it works again.

[OTGvis]

Verry hot this morning in my house... The communication stalled from my thermostat (Error 01) and the right temperature was not sent to the boiler so it kept on heating. Changing from gateway to monitor restored the communication and put the boiler on ease. (Perhaps a future failsave option in OTG?)

Seems Bosch is deviating from the OT specs too much for OTG at this moment. Is there anything I can provide to see what is going (wr)on(g) and perhaps update OTG?

[hvxl]

I've just updated to 4.0b3 and noticed that the command TC=temperature doesn't work anymore with my Honywell round thermostate.

Please collect a log (with PS=0), so I can have a look at what the problem might be.

[hvxl]

Verry hot this morning in my house... The communication stalled from my thermostat (Error 01) and the right temperature was not sent to the boiler so it kept on heating. Changing from gateway to monitor restored the communication and put the boiler on ease. (Perhaps a future failsave option in OTG?)

There are a few failsafe mechanisms in the gateway already. Which firmware version are you using?

[hvxl]

still looking for a way to overrule the temp settings on my Bosch.

You keep mentioning what kind of boiler you have, but whether it's possible to override the temperature setting depends on the thermostat. Which one do you use?