Page 4 of 20
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Mon Jul 29, 2013 12:00 pm
by fabian
hvxl wrote:
Yes, the most crummy thermostat I know with the most crummy boiler (opentherm-wise) should actually work pretty well now with the gateway in between.
Do i-sense a hint to look for a less crummy thermostat ?

Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Wed Jul 31, 2013 12:26 am
by blb
Hi Schelte,
Thanks for the new version (4.0a6)! I have installed it on my gateway in combination with my Celcia20 Thermostat. The good News is the messages are now without errors, so the less strict timing works well for the Celcia20 as well. I have noticed the IT command is not available any more and the PR=T command as well, which seems to be in line with this.
What doesn't work for me is the manual setpoint override. I see in your overview of new features "Stop sending the Celcia setpoint in DataID 9.", it's unclear to me why you have taken this feature out as it seem I can't control the setpoint anymore. Or do I something wrong?
Bernard
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Fri Aug 02, 2013 6:12 pm
by hvxl
Hi Bernard,
Sorry for not responding sooner. I only just got the notification mail of your update.
As far as I know, the Celcia20 doesn't look at MsgID 9 for a setpoint override. It looks at MsgID 4 instead. And if someone with a different thermostat used the TR command by accident, it could put their setpoint to its max. Mine would go to 35! So I started sending the correct setpoint in MsgID 9, instead of using the same value the Celcia wants to see in MsgID 4. This was already changed in the first 4.0 alpha firmware version and
you reported you did not see any negative impact from it.
A more likely cause of problems with the manual setpoint override is the new auto-detect of Remeha thermostats. The gateway needs to see a Master configuration message (MsgID 2, reporting the thermostat brand), followed by a Master product version message (MsgID 126, indicating the thermostat model) from the thermostat before it knows it's dealing with a Celcia20. These messages are transmitted by the Celcia about once every 6 minutes, but unfortunately in the wrong order. So, after flashing the new firmware, it may take up to 6 minutes until MsgID 2 comes by, and then another 6 minutes for the following MsgID 126.
If you tried your manual override within this time, the gateway will not have applied the special treatment required by the Celcia20. Have you tried this again after the gateway had been running on the new firmware for a while?
You can check if the gateway correctly detected that you are using a Celcia20 by dumping address 0x69 (DP=69). It should report 69=A0 for a Celcia20 (C0 for an iSense, 80 for another Remeha thermostat like the c-Mix, and 00 for a non-Remeha thermostat).
If you don't get A0, let me know. Otherwise, if the manual override doesn't work while you do see A0, can you send me a log where you issue a TT or TC command?
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Aug 04, 2013 12:05 am
by blb
Schelte,
Thanks! I'm sure I did test it indeed within 12 minutes after upgrading the gateway, according your explanation that seems to have caused the problem! it's working now as is should be. DP=69 gives indeed A0 as result.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sun Aug 04, 2013 11:17 am
by Puffin
Hi Schelte,
Thanks for the new version 4.0a6 I have installed it on my gateway in combination with an
intergas Kompact Solo HRE and an Chronotherm Touch Modulation.
Working like a charm, thanks for the new features.
Kind regards,
Folkert
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Tue Aug 06, 2013 9:36 pm
by hvxl
It's nice to just get an appreciative message without any problems or questions once in a while. I'm glad you like the new firmware.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Wed Aug 28, 2013 10:34 pm
by hvxl
steelrv wrote:what about my first request? the CMD to reboot/reset the OTG print? Is that possible in a future release?
I was just reminded by another thread that this feature was implemented in 4.0a6: The command is GW=R.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Thu Aug 29, 2013 10:16 pm
by visserej
Today I tested the firmware 4.0a6. This is my equipment:
- Intergas Kombi-Kompakt HRE 28/24 Combi (boiler)
- Honeywell Round Modulation thermostat
Normally I never use the thermostat itself but I use DomitiGa to override the setpoint on demand or with a time schedule. This firmware test was only done with the otmonitor application.
I found that only the monitor mode (GW=0) gives a correct result. In gateway mode (GW=1) the output gets stuck on a random 'T' message followed by an 'error 1' of which the counter increases endlessly.
The current release 3.4 works without any (noticeable) issues.
Code: Select all
Logfile snippet:
22:14:48.801171 T10010A00 Write-Data Control setpoint: 10.00
22:14:49.694056 BD0010A00 Write-Ack Control setpoint: 10.00
22:14:49.980693 T80000200 Read-Data Status: 00000010 00000000
22:14:50.004793 B40000200 Read-Ack Status: 00000010 00000000
22:14:51.448895 T90101000 Write-Data Room setpoint: 16.00
22:14:51.486013 Command: PR=A
22:14:51.536982 BF0101000 Unk-DataId Room setpoint: 16.00
22:14:51.587532 OpenTherm Gateway 4.0a6
22:14:52.175727 T80190000 Read-Data Boiler water temperature: 0.00
22:14:52.198385 BC0193D00 Read-Ack Boiler water temperature: 61.00
22:14:52.951935 T10010A00 Write-Data Control setpoint: 10.00
22:14:53.187931 BD0010A00 Write-Ack Control setpoint: 10.00
22:14:53.944194 Command: GW=1
22:14:53.970648 IP
22:14:54.019183 T80000200 Read-Data Status: 00000010 00000000
22:14:54.640337 B40000200 Read-Ack Status: 00000010 00000000
22:14:55.213919 T101816E1 Write-Data Room temperature: 22.88
22:14:55.310557 Error 01
22:14:56.267272 T101816E1 Write-Data Room temperature: 22.88
22:14:56.292575 Error 01
22:14:57.500639 T101816E1 Write-Data Room temperature: 22.88
22:14:57.529239 Error 01
22:14:58.731890 T101816E1 Write-Data Room temperature: 22.88
22:14:58.758195 Error 01
22:14:59.962983 T101816E1 Write-Data Room temperature: 22.88
22:14:59.989273 Error 01
22:15:01.196122 T101816E1 Write-Data Room temperature: 22.88
22:15:01.221578 Error 01
22:15:02.432206 T901816E3 Write-Data Room temperature: 22.89
22:15:02.460578 Error 01
22:15:03.614636 Command: GW=0
22:15:03.640409 IP
22:15:03.684197 T901816E3 Write-Data Room temperature: 22.89
22:15:03.718462 Error 01
22:15:04.896798 T901816E3 Write-Data Room temperature: 22.89
22:15:05.082775 BF01816E3 Unk-DataId Room temperature: 22.89
22:15:05.940260 T80190000 Read-Data Boiler water temperature: 0.00
22:15:06.140638 BC0193D00 Read-Ack Boiler water temperature: 61.00
22:15:06.987120 T10010A00 Write-Data Control setpoint: 10.00
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sat Aug 31, 2013 12:49 pm
by hvxl
Apparently some equipment doesn't produce clean transitions between the logical levels of the opentherm signal, but cause the signal to bounce a few times. I guess I will have to reintroduce the IT command to ignore these spurious transitions.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Tue Sep 03, 2013 10:05 am
by sybe@sijbesma.org
I also would like to test this version.
Can this version be used to integrate an outside temperature probe to the gateway.
And if so, where can I get the info.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Sat Sep 07, 2013 5:47 pm
by algol
Hi all,
I also have the same errors 01 reported by visserej after upgrading to 4.0a6 from 3.4.
Boiler: Hoval TopGas Comfort 15kW
Theromostat: Hoval TopTronic RS-T
This occurs when setting the OTGW in Control (GW=01).
I also have an error 03 that I still need to investigate.
Log snipet:
Code: Select all
17:40:47.895698 T90020016 Write-Data Master configuration: 00000000 22
17:40:48.187576 B50020016 Write-Ack Master configuration: 00000000 22
17:40:48.945538 T00030000 Read-Data Slave configuration: 00000000 0
17:40:49.185176 BC0031908 Read-Ack Slave configuration: 00011001 8
17:40:49.994561 T00050000 Read-Data Application-specific flags: 00000000 0
17:40:50.292160 BC0050000 Read-Ack Application-specific flags: 00000000 0
17:40:51.043691 T00060000 Read-Data Remote parameter flags: 00000000 00000000
17:40:51.362939 Error 03
17:40:52.093986 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:40:52.569282 B500E6400 Write-Ack Maximum relative modulation level: 100.00
17:40:53.143378 T10100A00 Write-Data Room setpoint: 10.00
17:40:53.511036 BD0100A00 Write-Ack Room setpoint: 10.00
17:40:54.193135 T00110000 Read-Data Relative modulation level: 0.00
17:40:54.509686 Error 03
17:40:55.242236 T90181680 Write-Data Room temperature: 22.50
17:40:55.565609 B50181680 Write-Ack Room temperature: 22.50
17:40:56.292061 T80190000 Read-Data Boiler water temperature: 0.00
17:40:56.639361 B40193CF5 Read-Ack Boiler water temperature: 60.96
17:40:57.341346 T801A0000 Read-Data DHW temperature: 0.00
17:40:57.656349 B401A3D1C Read-Ack DHW temperature: 61.11
17:40:57.742922 Command: GW=1
17:40:57.807382 OK
17:40:58.391134 T001B0000 Read-Data Outside temperature: 0.00
17:40:58.422552 Error 01
17:40:59.442183 T801C0000 Read-Data Return water temperature: 0.00
17:40:59.473093 Error 01
17:41:00.493285 T00300000 Read-Data DHW setpoint boundaries: 0 0
17:41:00.525890 Error 01
17:41:01.544360 T80380000 Read-Data DHW setpoint: 0.00
17:41:01.583388 Error 01
17:41:02.595417 T00390000 Read-Data Max CH water setpoint: 0.00
17:41:02.626975 Error 01
17:41:03.646812 T907C024D Write-Data OpenTherm version Master: 2.30
17:41:03.675330 Error 01
17:41:04.698026 T107E0118 Write-Data Master product version: 1 24
17:41:04.726126 Error 01
17:41:05.749795 T10800000 Write-Data Message ID 128: 0
17:41:05.777245 Error 01
17:41:06.800931 T80000200 Read-Data Status: 00000010 00000000
17:41:06.828043 Error 01
17:41:07.852167 T10010000 Write-Data Control setpoint: 0.00
17:41:07.880530 Error 01
17:41:08.903318 T90020016 Write-Data Master configuration: 00000000 22
17:41:08.931793 Error 01
17:41:09.954124 T00030000 Read-Data Slave configuration: 00000000 0
17:41:09.980130 Error 01
17:41:11.050228 T00050000 Read-Data Application-specific flags: 00000000 0
17:41:11.076261 Error 01
17:41:12.056296 T00060000 Read-Data Remote parameter flags: 00000000 00000000
17:41:12.087092 Error 01
17:41:13.107586 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:41:13.135175 Error 01
17:41:14.159768 T10100A00 Write-Data Room setpoint: 10.00
17:41:14.187423 Error 01
17:41:15.209609 T00110000 Read-Data Relative modulation level: 0.00
17:41:15.243712 Error 01
17:41:16.261900 T90181680 Write-Data Room temperature: 22.50
17:41:16.289682 Error 01
17:41:17.312598 T80190000 Read-Data Boiler water temperature: 0.00
17:41:17.345259 Error 01
17:41:18.363700 T801A0000 Read-Data DHW temperature: 0.00
17:41:18.390607 Error 01
17:41:19.414773 T001B0000 Read-Data Outside temperature: 0.00
17:41:19.441812 Error 01
17:41:20.465853 T801C0000 Read-Data Return water temperature: 0.00
17:41:20.492860 Error 01
17:41:21.516975 T00300000 Read-Data DHW setpoint boundaries: 0 0
17:41:21.544198 Error 01
17:41:22.569279 T80380000 Read-Data DHW setpoint: 0.00
17:41:22.609455 Error 01
17:41:23.620121 T00390000 Read-Data Max CH water setpoint: 0.00
17:41:23.647791 Error 01
17:41:24.671500 T907C024D Write-Data OpenTherm version Master: 2.30
17:41:24.697907 Error 01
17:41:25.723653 T107E0118 Write-Data Master product version: 1 24
17:41:25.750111 Error 01
17:41:26.774379 T10800000 Write-Data Message ID 128: 0
17:41:26.800965 Error 01
17:41:27.825602 T80000200 Read-Data Status: 00000010 00000000
17:41:27.852579 Error 01
17:41:28.877815 T10010000 Write-Data Control setpoint: 0.00
17:41:28.905066 Error 01
17:41:29.929161 T90020016 Write-Data Master configuration: 00000000 22
17:41:29.955285 Error 01
17:41:30.981795 T00030000 Read-Data Slave configuration: 00000000 0
17:41:31.008072 Error 01
17:41:32.031870 T00050000 Read-Data Application-specific flags: 00000000 0
17:41:32.058316 Error 01
17:41:33.083010 T00060000 Read-Data Remote parameter flags: 00000000 00000000
17:41:33.115642 Error 01
17:41:34.134329 T900E6400 Write-Data Maximum relative modulation level: 100.00
17:41:34.161957 Error 01
17:41:35.185390 T10100A00 Write-Data Room setpoint: 10.00
17:41:35.213688 Error 01
17:41:36.237536 T00110000 Read-Data Relative modulation level: 0.00
17:41:36.264936 Error 01
17:41:37.289996 T1014D120 Write-Data Day of week and time of day: Sat 17:32
17:41:37.316607 Error 01
17:41:38.339659 T90150907 Write-Data Date: 9 7
17:41:39.422902 Error 01
17:41:39.465712 T901607DD Write-Data Year: 2013
17:41:39.508833 Error 01
17:41:40.442817 T90181680 Write-Data Room temperature: 22.50
17:41:40.471224 Error 01
17:41:41.493523 T80190000 Read-Data Boiler water temperature: 0.00
17:41:41.520417 Error 01
17:41:42.544594 T801A0000 Read-Data DHW temperature: 0.00
17:41:42.571697 Error 01
17:41:43.595763 T001B0000 Read-Data Outside temperature: 0.00
17:41:43.630933 Error 01
17:41:44.651193 T801C0000 Read-Data Return water temperature: 0.00
17:41:44.684441 Error 01
17:41:45.698956 T00210000 Read-Data Exhaust temperature: 0.00
17:41:45.725609 Error 01
17:41:46.750320 T00300000 Read-Data DHW setpoint boundaries: 0 0
17:41:46.777643 Error 01
17:41:47.207370 Command: GW=0
17:41:47.247357 OK
17:41:47.800995 T80380000 Read-Data DHW setpoint: 0.00
17:41:48.002145 BC0383400 Read-Ack DHW setpoint: 52.00
17:41:48.851084 T00390000 Read-Data Max CH water setpoint: 0.00
17:41:49.165335 B40394600 Read-Ack Max CH water setpoint: 70.00
17:41:50.071497 T907C024D Write-Data OpenTherm version Master: 2.30
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Mon Sep 09, 2013 1:19 am
by blb
Schelte,
I have found something strange with the PR=G command. It doesn't matter if I have set GW=0 or GW=1, in both cases the result of PR=G is always 00. As far as I see the gateway is always in gateway mode (Reacting on temperature control commands via serial if).
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Mon Sep 09, 2013 1:46 pm
by hvxl
Bernard,
Due to the new configurable GPIO pins feature, I changed the meaning of PR=G: It now reports the GPIO pin settings. There is a new PR=M command to request the operating mode of the device. In 4.0a6 this still returns '1' for gateway mode and '0' for monitor mode. While writing this down I realize that doesn't make much sense. So for 4.0a7 I am planning to change that to 'G' for gateway mode and 'M' for monitor mode.
Thanks for reporting this. I will update the web site.
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Wed Sep 18, 2013 11:22 pm
by MarFan
I'm testing my new OTG, first I installed the 'normal' firmware. Everything seems to work normal. (I see log, I see graph ....)
Because I did not see the Return Water Temp, I tried the 4.06 firmware.
After the program, it's not working correctly

(I did a power down/up)
1) The thermostaat shows "Aansluiting fout" (connecting error)
2) the CH starts heating HELP
3) the program shows :
Code: Select all
22:41:48.288481 T00030000 Read-Data Slave configuration: 00000000 0
22:41:48.310817 Error 01
22:41:49.198404 T00030000 Read-Data Slave configuration: 00000000 0
22:41:49.218366 Error 01
22:41:50.110552 T00030000 Read-Data Slave configuration: 00000000 0
22:41:50.140650 Error 01
22:41:51.030582 T00030000 Read-Data Slave configuration: 00000000 0
22:41:51.034750 Error 01
22:41:51.940985 T00030000 Read-Data Slave configuration: 00000000 0
22:41:51.944398 Error 01
22:41:52.850685 T00030000 Read-Data Slave configuration: 00000000 0
22:41:52.860164 Error 01
22:41:53.760750 T00030000 Read-Data Slave configuration: 00000000 0
22:41:53.770233 Error 01
22:41:54.670844 T00030000 Read-Data Slave configuration: 00000000 0
22:41:54.680445 Error 01
After re-programming the 3.6 firmware, everything is working normal.
I have a Honeywell Chronotherm Vision Modulation and a Daalderop Combipact 24/33
Re: Opentherm Gateway 4.0 alpha/beta testers wanted
Posted: Fri Sep 20, 2013 9:45 pm
by maddog_rvo
I`m also itching to test this firmware....
But first i need to receive the gateway and solder it together

.
I hope it doesn`t take too long, i`m a .NET programmer and want to start writing software for it myself.
My end goal is to replace my thermostat completely (the display is starting to give up

)