New User - Out of the box test?

[altego]

Hey Guys,

New OTGW user here, just finished building the Nodo unit and wanted to test it in isolated (before hooking it up my heating system, which is a Baxi DuoTec 40e with a Tado thermostat).

Is this possible?

I've added it to my home assistant (using the OTGW addon) and it just sits there cycling between "heat" and "unavailable" ?

Also, do the username/password for MQTT configuration not work, my homeassistant log says it never presents a username (but does see the connection)...

Thanks muchly!

[hvxl]

My suggestion would be to first get the OTGW working with your central heating system using OTmonitor. You can follow the troubleshooting instructions if you want to do it step by step. Once that is working, you can proceed to integrate it with your home automation system. Doing it the other way around makes debugging any issues much harder (and I will not be able to help because I am not familiar with how the different home automation systems interface with the OTGW).

[altego]

thanks, i took the plunge and hooked it up.

it seems to be working, i can see requests from the tado, I can see stats from the boiler (and the tado).

opentherm monitor and homeassistant are both working, it seems

Is it ok to see a few Errors ? I have 0x Error01, 1x Error02, 26x Error03, and 3x Error04... Is that normal?

One last thing - LED D is on, which apparently corresponds to Boiler Requires Maintenance... How is that determined?

[hvxl]

The occasional error is no problem. Unless you got those amounts of errors in just a few minutes, there is not much to worry about.

The maintenance LED indicates that either the fault indication bit (ID0:LB0) or the diagnostic/service indication bit (ID0:LB6) in the slave status byte is set. In such a situation, ID5 may provide more details.

[altego]

Thanks

How do I issue an ID5 cmd?

I tried doing some PS commands in opentherm monitor, but I just get back a bunch of "SE's"...

[hvxl]

When something doesn't work as you expect, please show exactly what you did and what the response was. A remark such as "I tried doing some PS commands" requires mind reading to guess what may have been wrong with those commands.

When the OTGW first finds the fault or diagnostic/service bit set, it will automatically request ID5 in the next available spare slot. If you missed that, you can manually request it with the PM=5 command.

[altego]

OK I ran PM=5:

01:02:46.525135 Command: PM=5
01:02:46.600227 T801B7FFF Read-Data Outside temperature: 128.00
01:02:46.605724 PM: 5
01:02:46.722316 BF01B0000 Unk-DataId Outside temperature: 0.00
01:02:47.096290 T801B7FFF Read-Data Outside temperature: 128.00
01:02:47.101855 R00050000 Read-Data Application-specific flags: 00000000 0
01:02:47.217348 BC0050000 Read-Ack Application-specific flags: 00000000 0


I am assuming the response is the last two lines there? all bits clear right? According to the Opentherm 2 spec this would mean no fault?

Inside Opentherm the "Fault indication" checkbox is off, but the LED D "boiler requires maint" (as per I/O pins setting page) is still on on the actual PCB...

Am I misunderstanding something?

[hvxl]

The opentherm spec does not define which OEM fault code means "no fault", if any. Different boiler manufacturers use different methods. Some do report 0 when everything is fine. But others may use 255, or not have a code that explicitly means "no fault". For example my Remeha Avanta reports 0 when there is no problem, but may also report error 0 in case of a problem with the flow- or return sensor. The way to know which of the two applies, is to look at the fault bit in the status byte.

To analyze your situation, please provide the following:

• OTGW Firmware version (PR=A)
• Output of PR=L
• Log containing one more status message requests and responses

[altego]

Here you go:

11:51:17.730716 Command: PR=A
11:51:17.834332 PR: A=OpenTherm Gateway 6.1

11:52:10.954135 Command: PR=L
11:52:11.061690 PR: L=FXOMPH

I wasn't sure if the following diag code is relevant? Does this message indicate a request from the Therm, with the boiler responding?
11:52:47.607268 T80730000 Read-Data OEM diagnostic code: 0
11:52:47.739358 B40730000 Read-Ack OEM diagnostic code: 0
11:52:47.745029 SC: 11:52/3

Is this the status request/response?
11:52:48.620157 T00000300 Read-Data Status: 00000011 00000000
11:52:48.741383 B4000004A Read-Ack Status: 00000000 01001010
11:52:49.104807 T00000300 Read-Data Status: 00000011 00000000
11:52:49.236824 B4000004A Read-Ack Status: 00000000 01001010
11:52:49.622220 T00000300 Read-Data Status: 00000011 00000000
11:52:49.754377 B4000004A Read-Ack Status: 00000000 01001010

[hvxl]

This shows that the OTGW works as intended. Your boiler indicates a diagnostic/service event. Due to this, the OTGW turns on the maintenance LED.

Message ID115 is definitely interesting. While ID0:LB0 corresponds to a fault, which may have details in ID5 (OEM fault code), ID0:LB6 indicates a diagnostic event, with possible details in ID115 (OEM diagnostic code). Apparently the thermostat came to the same conclusion as the OTGW and requested ID115 for more information.

The whole status response from your boiler is very strange, though. The Opentherm spec says: "The status exchange is a special form of conversation which should be initiated by the master by sending a READ-DATA(id=0,MasterStatus,00) message. The slave must respond with READ-ACK(id=0,MasterStatus, SlaveStatus) to send back the Slave Status information in the same single conversation." So, the boiler is supposed to echo the master status in the high byte. It doesn't do that. It also reports that central heating is on (CH mode + Flame). I wouldn't expect that at this time of year, with outside temperatures of 25°C or higher.

[altego]

Thanks for your help thus far.

It is winter here in Australia, with day time temps of around 12c, and night time dipping into the low single digits... thus the heating coming on.

The Thermostat (a Tado Smart Thermostat) doesn't report any odd behaviour (and they apparently added some reporting for faults just recently); however with so many different boilers to support I am not surprised if its missed something.

Maybe I will take a look at the service manual of the boiler and see what I can find, I dont think they publish Opentherm codes though...

[hvxl]

I wasn't aware Opentherm (and an OTGW) made it all the way to Australia. in that case it makes sense that the heating is on. Then the diagnostic bit and the wiped master status are the only strange things remaining.

Curious that the Tado doesn't indicate a problem, even though it seems to have detected it. Possibly it interprets an OEM diagnostic code of 0 as no problem, although that is not defined in the spec.

[altego]

Yes we are very progressive down-under

I love data, I wanted to see what the Tado was doing, and actually wanted to see how the boiler and system was performing, specifically trying to dial in return temps for efficiency. So far its providing a great level of detail - so thanks for everything you do

It integrates well with Home Assistant as well:

otgw demo.PNG (277.69 KiB) Viewed 2519 times