search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.93k stars 30.99k forks source link

Opentherm gateway: Received erroneous message #31688

Closed renehonig closed 4 years ago

renehonig commented 4 years ago

The problem

I have the Opentherm gateway running and regularly receive error messages like below. Any idea what the problem is?

Environment

Problem-relevant configuration.yaml

n/a, standard configuration via integration screen.

Traceback/Error logs

2020-02-10 09:21:51 WARNING (MainThread) [pyotgw.protocol] Received erroneous message, ignoring: b'\x00\x7f\xff\x00'
2020-02-10 09:22:21 WARNING (MainThread) [pyotgw.protocol] Received erroneous message, ignoring: b'\x10\x10\x15\xff'
2020-02-10 09:24:18 WARNING (MainThread) [pyotgw.protocol] Received erroneous message, ignoring: b'\x07\xff\xff\x00'

Additional information

probot-home-assistant[bot] commented 4 years ago

Hey there @mvn23, mind taking a look at this issue as its been labeled with a integration (opentherm_gw) you are listed as a codeowner for? Thanks!

frenck commented 4 years ago

Can you please fill out the full issue template? There is now a lot of information missing. Thanks!

renehonig commented 4 years ago

thanks, updated my issue using the template.

mvn23 commented 4 years ago

These messages get thrown when the gateway receives incorrect messages. On the serial interface they will start with the letter E. This can happen when either your boiler or thermostat is not complying with the specification or your OpenTherm Gateway needs tweaking. In the first case, there's not much you can do apart from replacing the boiler/thermostat. In the second case, you can try to tweak the VR Voltage Reference setting on the gateway according to the Serial commands section.

As for the bug report: this is not a bug in the opentherm_gw integration. It's receiving information that the gateway received incorrect data and throws a warning message. This is expected behavior and the bug report should be closed.

renehonig commented 4 years ago

many thanks for the explanation, I will look into your suggestions.