Opentherm Gateway

[Rene]

@Schelte: Is it possible to compile a version of the OTMonitor tool for ARM?

[hvxl]

@Schelte: Is it possible to compile a version of the OTMonitor tool for ARM?

Which one? ARMEL or ARMHF? Are you thinking of Raspberry Pi (raspbian wheezy)? I guess that should be possible.

[Rene]

I am using a Guruplug running Fedora 17. The Guruplug has a Marvell Kirkwood 88F6281 ARM Based CPU.

[Rene]

@Schelte: When I try to set the clock via otmonitor, the following lines appear in the logs (the actual time and current time of the thermostat was 23:00 and the time of the computer where I was running otmonitor was set to 12:49):

12:49:40.343525 Command: SC=12:49/1
12:49:40.367065 OK

12:50:03.649463 T10143700 Write-Data Day of week and time of day: Mon 23:00
12:50:03.674495 R00770000 Read-Data DHW burner starts: 0
12:50:03.917676 B40770068 Read-Ack DHW burner starts: 104
12:50:03.942881 A50142C31 Write-Ack Day of week and time of day: Mon 12:49
12:50:04.651346 T101607DC Write-Data Year: 2012
12:50:04.676647 R00780000 Read-Data Burner operation hours: 0
12:50:05.012082 B40780020 Read-Ack Burner operation hours: 32
12:50:05.037550 A701607DC Unk-DataId Year: 2012
12:50:05.652373 T90150A08 Write-Data Date: 10 8
12:50:05.678138 R80790000 Read-Data CH pump operation hours: 0
12:50:05.926929 B40790024 Read-Ack CH pump operation hours: 36
12:50:05.952450 AF0150A08 Unk-DataId Date: 10 8

[hvxl]

I have made versions of otmonitor available on the download page for both armel (guruplug) and armhf (raspberry pi).

[hvxl]

@Schelte: When I try to set the clock via otmonitor, the following lines appear in the logs

It looks like the thermostat asks for the time and the gateway correctly provides it. But you are saying the thermostat doesn't pick up the time provided by the gateway?

One reason could be that it needs to get a new time more than once before it will accept it. I think my thermostat asks again immediately after the gateway provides a time that differs from the clock of the thermostat. But if the iSense waits until the next minute to get confirmation that the clock really should be changed, you have to click the Set Clock button again after a minute. Can you test if that theory is right?

It's also possible that the iSense doesn't accept the time change because it doesn't get a valid response to the date requests. That would require a firmware change to fix.

[Rene]

It did not matter how many times I pressed the button. From the logs I understand the iSense is requesting the current time only once an hour:

Code: Select all

00:00:57.204644 T90146000 Write-Data Day of week and time of day: Wed 00:00
00:00:57.388833 A50146000 Write-Ack  Day of week and time of day: Wed 00:00
01:00:57.373812 T10146100 Write-Data Day of week and time of day: Wed 01:00
01:00:57.723300 AD0146100 Write-Ack  Day of week and time of day: Wed 01:00
02:00:57.508225 T10146200 Write-Data Day of week and time of day: Wed 02:00
02:00:57.833542 AD0146200 Write-Ack  Day of week and time of day: Wed 02:00
03:00:57.352008 T90146300 Write-Data Day of week and time of day: Wed 03:00
03:00:57.598097 A50146300 Write-Ack  Day of week and time of day: Wed 03:00
04:00:57.880170 T10146400 Write-Data Day of week and time of day: Wed 04:00
04:00:58.202829 AD0146400 Write-Ack  Day of week and time of day: Wed 04:00
05:00:58.171335 T90146500 Write-Data Day of week and time of day: Wed 05:00
05:00:58.496146 A50146500 Write-Ack  Day of week and time of day: Wed 05:00
06:00:57.569111 T90146600 Write-Data Day of week and time of day: Wed 06:00
06:00:57.961938 A50146600 Write-Ack  Day of week and time of day: Wed 06:00
07:00:59.626160 T10146700 Write-Data Day of week and time of day: Wed 07:00
07:00:59.864717 AD0146700 Write-Ack  Day of week and time of day: Wed 07:00

[hvxl]

It did not matter how many times I pressed the button. From the logs I understand the iSense is requesting the current time only once an hour

I have made a few quick changes to the firmware to test the second hypothesis. These changes will make the gateway respond with a Write-Ack to the date and year message ID's, rather than with Unknown-DataId. There is no way to specify the date over the serial interface yet. This is just a hack to test if the iSense will pick up the time if these messages are acknowledged by the gateway.

The experimental firmware is available at http://www.tclcode.com/download/isense.hex. Please give it a try and let me know the results. If this works, I'll look into properly adding the functionality. If it doesn't, I'll have to conclude that the iSense does not support changing the clock through the Opentherm interface.

[Rene]

Part of your site, including the download page, is unavailable.

[Rene]

Is it correct, the Thermostat has first to send the Write-Data Day of week before the gateway can send the time adjustment? Or can the gateway take the initiative?

[hvxl]

Part of your site, including the download page, is unavailable.

It seems fine to me.

[Rene]

It is now. I just downloaded the firmware and flashed the PIC.

[hvxl]

Is it correct, the Thermostat has first to send the Write-Data Day of week before the gateway can send the time adjustment? Or can the gateway take the initiative?

In an Opentherm setup the thermostat is the master, it is the part that decides what happens and when. So your statement is correct, the gateway has to wait for the Thermostat to request the time and date.

[Rene]

This is what the logs show now (the clock stil is not modified):

Code: Select all

19:27:44.743745 T90147700 Write-Data Day of week and time of day: Wed 23:00
19:27:44.865228 BF0147700 Unk-DataId Day of week and time of day: Wed 23:00
19:27:44.876551 AD014731B Write-Ack  Day of week and time of day: Wed 19:27
19:27:45.739577 T101607DC Write-Data Year: 2012
19:27:45.860589 B701607DC Unk-DataId Year: 2012
19:27:45.882811 AD01607DC Write-Ack  Year: 2012
19:27:46.741721 T10150A0A Write-Data Date: 10 10
19:27:46.855639 B70150A0A Unk-DataId Date: 10 10
19:27:46.867108 AD0150A0A Write-Ack  Date: 10 10

[hvxl]

That is what I was trying to achieve. If the iSense doesn't change the clock based on that, I'm afraid it probably doesn't have the functionality to set the clock through the Opentherm interface. At least I don't have any more ideas how it could be done at the moment.