Sent you a pm.

That's what I expected. I'm building a binary for rpi3 right now. I will put it tomorrow on my github page. Your OTGW works just fine. It outputs the same as mine. Do you have a rpi2 or rpi3?

Just as soon as you connect the device. You can always switch back with ps=0. And I have spoken to the developer. He thinks our devices will work with ps=1 'mode'. The fact that my OTGW device resets itself from time to time and domoticz will not read the data from the device isn't working ...

Hobbybob wrote: ↑Sunday 23 February 2020 21:14 is there anywhere I could follow this? Like an issue on github or anything?

Yes: https://github.com/domoticz/domoticz/pull/3945

In the domoticz hardware tab of the OTGW you can issue commands. Can try sending ps=1 and see what happens?

I am working on a solution now with the developers. It will take some while though.

I just created an issue on GitHub: https://github.com/domoticz/domoticz/issues/3943. See what happens...

The code never ended up in the development branch. Maybe it is a good idea that I contact the developers about it. I think it is wise to add an extra device (to the source) instead of replacing the current one. Maybe there are people using the code of the "old" device.

I downloaded the files, but I have been looking around on my RPi, and I can't seem to find these files... How do I install these? The are sourcefiles and you need to compile it. Did you install your RPi the easy way or did you compile it from source? If you never done it, maybe I can send you my ...

I attached a screenshot. I connected domoticz via otmanager so there is more to see. Oh forgot to say I changed the devices IDs of the switches and sensors in domoticz to the corresponding OpenTherm message IDs. So you need to delete the OTGW devices from domoticz. It will make new devices with the ...

I think it has got something to do with the serial to lan communication between domoticz and the otmonitor. I think you are right. I just finished rewriting the code (everything works flawless now) and discovered I made a terrible mistake. The good side is that I now know the cause of most problems ...

I don't know if it will solve my problems, but if the other solutions don't work, I'll sure give it a try!

If you only see messages of length 9, mostly starting with a B(oiler) or a T(ermostat) in your domoticz log then it would.

I just bought an OTGW with firmware 4.2.5. I noticed that it reports only messages of length 9 (like BC0090000) to domoticz (it says 2018-05-18 19:26:48.619 OTGW: BC0090000) while the source-code of domoticz seems to want to parse other output. I guess it is more like the messagelog of otmanager ...