OTGW - Get CV water pressure

[Muzzikap1]

First of all HVXL thank you for a OTGW module that has been working very well for many years.

This summer I moved to my new home.
I took the OTGW (V4.2.5 / date: 20-10-2015) from my old home and installed it in the new hardware setup:
- Intergas Kombi Kompakt HReco 36
- Honeywell modulation: T87M2018 (1603)

The setup is working pretty well.
I can monitor/control the setup using the opentherm monitor.
The only thing missing is that I cannot monitor the CH water pressure and the DHW temperature and setpoint.
As you can see in the attachment.

When I take a look at the equipment details for ( Intergas Kombi Kompakt HReco; Honeywell Round Modulation T87M2018)
I can see that the ketel can provide the messages and that the thermostat is also compatible with, ID=18/26/48.

I think I'm doing something wrong here.

As one of the first steps in an attempt to debug the problem is upgrading the firmware of the otgw to V5.8 but this didn't solve the problem.

Could you point me in the right direction how to be able to read the water pressure from the ketel>

[hvxl]

The Honeywell round modulation thermostat provides only very basic functionality. It doesn't (need to) use many different Opentherm messages to be able to do that. So it doesn't request MsgIDs 18, 26, and 56. To obtain that information from the boiler anyway, you can instruct the OTGW to periodically request that information by running the AA=18, AA=26, and AA=56 commands.

For the AA commands to have any effect, there must be some messages from the thermostat for which the boiler returns Unk-DataID. I couldn't tell from your screen shot if that is the case.

[Muzzikap1]

For the AA commands to have any effect, there must be some messages from the thermostat for which the boiler returns Unk-DataID. I couldn't tell from your screen shot if that is the case.

I first checked if I see the Unk-DataID appear in the logging. -> This is true for MsgID=14

unk-dataID.GIF (108.16 KiB) Viewed 711 times

I executed the command:

Code: Select all

21:58:55.749435	Command: AA=18
21:58:55.804328	AA: 18

I waited for some time but after a few times watching the msgID=14 pass by in the logging but I didn't see the msgID=18 appear as a substitute in the logging.

Next thing i did is trying to force msgid14 as unknown id

Code: Select all

22:00:02.083618	Command: UI=14
22:00:02.151383	UI: 14

when this didn't seem to do much I tried to force id 25.:

Code: Select all

22:01:09.160164	Command: UI=25
22:01:09.224303	UI: 25

and played with PM

Code: Select all

22:01:50.395501	Command: PM=18
22:01:50.411431	PM: 18

I don't seem to get the response I excpected.
I attached the logging in the zip.

The OTGW is running in monitoring mode ( firmware version 4.3)

[hvxl]

The OTGW is running in monitoring mode ( firmware version 4.3)

That's the problem then. As the name suggests, in monitor mode the OTGW can not make any changes to the message exchange between the thermostat and the boiler. It only monitors the messages. So, in this configuration, the thermostat fully controls what information you get.

Why did you decide to put your OTGW in monitor mode?
I thought you had updated the firmware to 5.8. Why did you go back to 4.3?

[Muzzikap1]

The reason for downgrading the firmware to version 4.3 is because the logging displays Data-inv messages when processing data from message ID 5 or 2.

Code: Select all

10:44:32.540785	T00110000	Read-Data 	Relative modulation level (MsgID=17): 0.00
10:44:32.635793	BC0110000	Read-Ack  	Relative modulation level (MsgID=17): 0.00
10:44:33.540705	T1002010D	Write-Data	Master configuration (MsgID=2): 00000001 13
10:44:33.630396	BE0020000	Data-Inv  	Master configuration (MsgID=2): 00000000 0
10:44:34.541697	T80190000	Read-Data 	Boiler water temperature (MsgID=25): 0.00
10:44:34.632905	B40191AA1	Read-Ack  	Boiler water temperature (MsgID=25): 26.63
10:44:35.540200	T10010A00	Write-Data	Control setpoint (MsgID=1): 10.00
10:44:35.632574	BD0010A00	Write-Ack 	Control setpoint (MsgID=1): 10.00
10:44:36.540021	T80000200	Read-Data 	Status (MsgID=0): 00000010 00000000
10:44:36.631147	B40000200	Read-Ack  	Status (MsgID=0): 00000010 00000000
10:44:37.539782	T00110000	Read-Data 	Relative modulation level (MsgID=17): 0.00
10:44:37.629520	BC0110000	Read-Ack  	Relative modulation level (MsgID=17): 0.00
10:44:38.540697	T00050000	Read-Data 	Application-specific flags (MsgID=5): 00000000 0
10:44:38.629271	B60050000	Data-Inv  	Application-specific flags (MsgID=5): 00000000 0

I downgraded to version 4.3 and noticed that the Data-Inv messages remained.
Didn't bother to upgrade back to version 5.8 yet.

Actions taken:
- Switched OTGW to gateway mode. The reason it was in monitor mode is that monitoring mode was working fine for me in the old situation.
- Send AA=18 again.
- monitored logging. The Unk-DataID remains showing up but no MsgID=18
- Using TP=18 doesn't seem to force a request for msg-id=18.


Are there any other settings that need to be configured in a certain way to make the AA message work?

[hvxl]

Log?

Firmware version 4.3 is nearly 3 years old, and there have been several newer versions since then. So I don't remember the exact details, but I'm quite confident that the AA command was already working back then.

Let me also try to clear up some misconceptions you appear to have:

• Data-Inv is a type of message sent by the boiler. Changing the firmware version of the OTGW has no influence on that.
• The default mode of the OTGW is gateway mode. You get the most benefit from the device by leaving it at that default mode. You should only switch to monitor mode when gateway mode is not working correctly.
• Switching between modes does not make the OTGW forget the AA commands that you entered before. You will now have multiple entries for MsgID 18 in the list of alternatives.
• TP=18 is not a valid command. You probably want PM=18.

[Muzzikap1]

I didn't have much time to investigate the issue further the last couple of weeks.

Last week there was a poweroutage.
After the poweroutage was restored the cv water pressure messages were present.

I manually powercycled the otgw before but that didn't work.
This time it worked.

Thanks for your time and help!