Some MsgID not updating

[Paul H te O]

Hi Schelte,

Thanks for this great OTGW firmware.

I'm using this OTGW together with HS4, it works good.
A lot of info and I can control my thermostat
Only a few devices in HS4 are only updating when I start "Compability log" in the Opentherm monitor.
(The HS4 devices where also created when I started this o.a. MsgID26, MsgID116, MsgID120 and MsgID123)
Anny idea how I can get this devices updated without doing this?

Thanks Paul.

[hvxl]

The "Compatibility log" function first collects all messages that the thermostat requests. Then it requests additional messages using the PM command. That command only requests the message once. To periodically request the information, use the AA command with the desired message ID.

By default the OTGW should already have MsgIDs 116, 120, and 123 in its list of things to request. If you don't see those and you didn't manually remove them with the DA command, it may mean that your boiler doesn't respond with Unk-DataID to any of the messages the thermostat requests. In that case you can look for a less important message that you can sacrifice. Using the UI command, you can tell the OTGW not to send some messages to the boiler, so it can use the slot to send something else. The "Compatibility log" function does that too, but it restores it when it's done. Some candidates could be Room Setpoint and Room Temperature. The boiler really shouldn't have any need for those messages.

[Paul H te O]

I haven't used commands yet, when I send PM=26 nothing happens (except that I see it in the log)
See screenshot.
I also tried the UI command but no result.

command.jpg (31.28 KiB) Viewed 6035 times

[hvxl]

This doesn't help at all.

• Don't use jpeg for screenshots. It's not a suitable format for high-contrast images, such as screenshots.
• Don't use screenshots for text anyway. The actual text is much easier to work with.
• Regardless of the above points, almost nothing can be gleaned from only 1 second of OT communications.

[Paul H te O]

I will create a log and sent it to you, by your website.
I treid the capability log but get always this error (toepassingsfout):

can't set "gui(returntemp)": can't use non-numeric string as operand of "-"
can't use non-numeric string as operand of "-"
while executing
"expr {$gui(boilertemp) - $gui(returntemp)}"
(procedure "deltatemp" line 4)
invoked from within
"deltatemp gui returntemp write"
(write trace on "gui(returntemp)")
invoked from within
"set gui($name) ???"
(procedure "unknownid" line 6)
invoked from within
"unknownid returntemp 0"
invoked from within
"specialcoro flush"
(procedure "otmessage" line 15)
invoked from within
"otmessage $us $line [expr {$type & 7}] $id $data"
(procedure "process" line 13)
invoked from within
"process [append data $line]"
(procedure "receive" line 6)
invoked from within
"receive"

[hvxl]

That was fixed since the latest release of OTmonitor. You can get a build of the current development version via github actions. Click on the latest workflow run that has a green tick mark. Then you can download the artifact for your platform. You may need to be logged in on github for the download links to work.

[Paul H te O]

Installed the latest release ( version still shows 6.4 )
Now it stays at "Checking message ID 5", whole night.
No error message.

[Paul H te O]

See here a long log file, hope it helps...

[hvxl]

Your thermostat only requests a very limited number of messages and the boiler responds with Read-Ack or Write-Ack to all of them. But the compatibility log feature should be able to find a message that it can (temporarily) use to collect the data it needs. I'll have to check why that doesn't seem to have worked. Your log file should help to simulate your situation.

You indicated before that you tried the UI command. Which value did you use in that command?

[Paul H te O]

I used this commands:
UI=16
UI=24
PM=26 (this one you can also see in the log file I uploaded)

[Paul H te O]

I tried "capability log" again today, and now it finisched well
See attachment.

[hvxl]

Your thermostat and boiler conspire to make life difficult in several ways:

• The thermostat only requests a few different standard message IDs and the boiler acknowledges them all.
• In addition, the thermostat request some message in the Test & Diagnostics range (128..255), to which the boiler responds with Unknown-DataID.
• The boiler apparently doesn't support any of the predefined alternatives.

This has the following effects:

Capability log hanging at "Checking message ID 5"
The OTGW only tracks standard messages to determine which slots it can use to send alternative messages. The capability log feature correctly ignores the Test & Diagnostics messages when looking for free slots. After concluding that there is no usable free slot, the feature picks the most frequent unimportant message to temporarily designate as unknown. This should create a slot for requesting information from the boiler. But in this step, the OTmonitor code failed to exclude the Test & Diagnostics messages. As a result it may pick one of the Test & Diagnostics messages, which doesn't actually provide a message slot to use. The latest OTmonitor version on github should fix this problem.

Manual PM command not producing any output
When sending alternatives, the OTGW removes a message from the list if the boiler responds 3 times with Unknown-DataID. Once the list of alternatives is empty, the OTGW forwards the message requested by the thermostat, despite being marked as unknown. When the boiler sends a positive response to a message that is marked as unknown, the OTGW removes the unknown indication. So any UI command is quickly undone when there are no alternatives and the boiler actually supports the message. To prevent this from happening, make sure there is at least one alternative on the list at all times. Pick one that your boiler definitely supports. For example AA=18. After that your UI=16 and UI=24 should remain in effect.

[Paul H te O]

Beste Schelte,

Thanks for the elaborate explanation.
I downloaded the latest version and it works fine now.

Sending the commands manualy does not "yet" give the correct result.
When I send this commands AA=18, UI=16, UI=24, two other MsgIDs should replace it if I understand correctly.
That's not happening yet, as I see it.
Go experiment some more.

But the most important thing works and that is operating my thermostat

[hvxl]

Well, after those commands, you should see that the Room temperature and Room setpoint messages get replaced with CH water pressure messages:

Code: Select all

23:14:29.101331	T10101400	Write-Data	Room setpoint: 20.00
23:14:29.102263	R00120000	Read-Data 	CH water pressure: 0.00
23:14:29.193822	B40120214	Read-Ack  	CH water pressure: 2.08
23:14:29.194797	AD0101400	Write-Ack 	Room setpoint: 20.00
23:14:29.466054	T101813A0	Write-Data	Room temperature: 19.62
23:14:29.466890	R00120000	Read-Data 	CH water pressure: 0.00
23:14:29.558460	B40120214	Read-Ack  	CH water pressure: 2.08
23:14:29.559407	A701813A0	Unk-DataId	Room temperature: 19.62

But now, a PM=26 command will send a DHW temperature request once:

Code: Select all

23:16:32.472397	T10101400	Write-Data	Room setpoint: 20.00
23:16:32.475620	R801A0000	Read-Data 	DHW temperature: 0.00
23:16:32.553878	B401A17E8	Read-Ack	DHW temperature: 23.91
23:16:32.557501	AD0101400	Write-Ack 	Room setpoint: 20.00

If you want repeated readout of the DHW temperature, use AA=26.

[gadgetboy24]

hm... thank you very much! I'm looking for this information soooo long!