Home Automation Domotica Forum Europe, Bwired Forum

That is disappointing indeed. Thanks for the equipment matrix hint though!

At the moment I am revamping the OpenTherm Gateway Home Assistant integration. One of the things I would like to improve is to be able to show manufacturer names based on the Member IDs found in the OpenTherm protocol. As I don't have access to all brands of boilers and thermostat, I can only determ...

That last version works like a charm! Thanks again for your efforts!

Thanks for the effort, it helped me make some progress. I also found that it is likely related to the setup I'm using, more on that later on in this post. First things first, I tried the debug version, both through the GUI and from the command line. The output was the following: GUI: $ ./otmonitor-x...

When I click "Program", the button remains pushed in (see screenshot) and the entire GUI becomes unresponsive. I can only close the application with ctrl-c on the command line (or with `kill` I guess, but I haven't tried that). This behavior persists in the latest version from github. Scre...

When trying to upgrade the firmware on my gateway through otmonitor I'm running into the following: Using the GUI, I can load the file, but as soon as I press "Program" the application stops responding. The only output on the console is this one line when loading the file: $ ./otmonitor re...

Thank you for the clarification. Does this apply to MsgID 23 (room setpoint 2) as well? I tried to go through the sources, but I'm not fluent in assembly. From what I can tell it does not apply in that case, but I may very well be mistaken.

The reporter of the bug provided additional info from the OpenTherm Gateway firmware sources. It seems this is intended behavior for good reason.

Topic can be closed!

While investigating a bug report against pyotgw ( here ) I noticed the following: When the boiler sends an Unknown DataID packet, the gateway forwards this as a Write Ack packet to the thermostat. This may be intended behavior, but it seems odd to me to take the value from the boiler (in this case 0...

Haha that's awesome! Thanks for the info. I already added an 'MPC' error code in my dev version of pyotgw guess I'll have to remove it again.
I'm trying to cover all of the more or less reasonable user inputs for the pyotgw update. If I find anything else I will of course update on this forum.

While playing around with the new firmware v5.0 I ran into the following: command: C2=9.999 reponse: MPC Unfortunately I can't find this error code anywhere in the docs. I'm guessing it has something to do with the float parsing (C2=9.99 is accepted without issues) but I would like to get some more ...

The C2 and H2 commands you requested have been implemented in OTGW firmware version 5.0. I didn't implement S2, mostly because I couldn't find a matching message ID for that function. While implementing the new features into pyotgw I noticed that these new commands don't respond with the usual form...