Support OTGW firmware v5.1.

[PvdGulik]

Hello, I’m using this OTGW-firmware ESP solution: https://github.com/rvdbreemen/OTGW-firmware

But I can’t get Homebridge-otgw connect to it. I don’t know what I’m doing wrong, or which settings I should use.

Thank you

[ebaauw]

Can you connect to this firmware from the OpenTherm Monitor?

[PvdGulik]

Yes, thats possible

[ebaauw]

Then connect Homebridge OTGW to the web server provided by the OpenTherm Monitor.

[PvdGulik]

Which means i have to run contineusly OT Monitor on a PC or Raspberry, which connect directly to the OTGW. It would be nice if it could connect direct without OT Monitor.

[ebaauw]

You can, see the README. Use the otgw setting and enter the hostname and port that OTM uses to connect to the serial server on the NodeMCU on the gateway. Note that the NodeMCU only supports one concurrent connection.

[PvdGulik]

Thanks, one step further, but errors:

[date, time] [OTGW] warning: heartbeat 129, drift 278 [date, time] [OTGW] warning: heartbeat 131, drift 1151 [date, time] [OTGW] warning: heartbeat 132, drift 1032 [date, time] [OTGW] warning: heartbeat 134, drift 573 [date, time] [OTGW] warning: heartbeat 135, drift 267 [date, time] [OTGW] warning: heartbeat 330, drift 1018

What to do?

[ebaauw]

These are warnings, not errors. They are raised because the heart rate isn't triggered at the scheduled time. If this only happens occasionally, there's probably nothing to worry about. If this happens structurally, it could indicate an issue with some plugin blocking the NodeJS process (probably by doing synchronous I/O), or you system load being too high.

[PvdGulik]

Thanks again for your quick answer. But still I don't see any accessoires from OTGW.

In the log I see the following:

And:

Is this because I use the latest OTGW firmware, version 5.1?

Thanks again!

[ebaauw]

Homebridge OTGW issues a PS=0 to the the gateway on startup, to receive a summary message and initialise all characteristics. It looks like it doesn't like it doesn't understand the response. Don't know if that's due to the firmware or due to bad communication. Error 03 is an error returned by the gateway.

[PvdGulik]

Helle ebaauw, just checking, does your plug-in only work with Opentherm Gateway version 4.2.6 or 4.3? Is there any change it will work with 5.1?

This because I still have issues, don't know how to solve...

Thanks!

[ebaauw]

Sorry, I hadn't realised there was new firmware published on http://otgw.tclcode.com/download.html#hexfiles.

Current version was built and tested against 4.2.6. I don't have the bandwidth nor the resources to test other versions. I want to support the latest released version, but still I need to install and test 5.1. I won't be supporting custom firmware.

[PvdGulik]

No problem, just let me know when to test, I like to help.

[ebaauw]

From the notes:

The PS=1 output has changed in version 5.0. If using this function, the program processing the information will have to be adapted accordingly. POTENTIAL INCOMPATIBILITY Users who need the old format (particularly Domoticz users) should stick to version 4.3.

[ebaauw]

Could you try beta v1.3.0-0?

[PvdGulik]

/usr/local/lib/node_modules/homebridge-otgw/lib/OtgwMessageParser.js is the file to change ?

[ebaauw]

Just install the beta through the Homebridge UI's Install Previous Version feature, or by issuing

sudo npm -g i homebridge-otgw@beta

from the command line.

[PvdGulik]

Thanks, that did the trick. Now its working!

[ebaauw]

Published v1.3.0.