OTGW and Orange Pi Zero one device.

[cyril]

Hi, Annope! It's very strange behavior. Can you show otmonitor log file? Also is there errors in otmonitor?

[anoppe]

Let me turn on logging again and I'll get back in a few hours so the logs contain some data. (I disabled it to increase my sd-cards lifespan )

[anoppe]

@Cyril I've attached the logfile. AS you can see the OTmonitor receives the wrong values from the boiler...:

Code: Select all

..
09:36:30.035412  T10181473  Write-Data  Room temperature: 20.45
09:36:30.184469  BD0181473  Write-Ack   Room temperature: 20.45
...
09:37:10.297974  T1018011E  Write-Data  Room temperature: 1.12
09:37:10.389887  BD018011E  Write-Ack   Room temperature: 1.12
...
09:37:51.517397  T901802AE  Write-Data  Room temperature: 2.68
09:37:51.675247  B501802AE  Write-Ack   Room temperature: 2.68
...
09:38:31.781551  T9018030A  Write-Data  Room temperature: 3.04
09:38:31.874404  B5018030A  Write-Ack   Room temperature: 3.04
...
09:39:12.049757  T10180400  Write-Data  Room temperature: 4.00
09:39:12.151855  BD0180400  Write-Ack   Room temperature: 4.00
...
09:39:52.310061  T1018147A  Write-Data  Room temperature: 20.48
09:39:52.457198  BD018147A  Write-Ack   Room temperature: 20.48
...


[cyril]

Hi! It looks like OTGW receives this values from thermostat. Try to change mode of the otmonitor to monitor mode, so OTGW will no affects to transmisson between thermostat and boiler.

[anoppe]

Thanks, I've applied your suggestion. Let me see what happens...

[cyril]

Overall, I presume, even if you try to turn back to original OTGW board, you cannot solve your issue. Obviously, this problem occurs after you install new thermostat, so... source of the problem - new thermostat. If you turn to ''Thermostat compatibility'' topic of this forum, you can see that all thermostat working differently and you cannot change this situation without changing OTGW firmware. I cannot help with it, because it require very deep knowing of programming.

[anoppe]

Hey Cyril,

Thank you for your clear and honest answer.
Btw: The adjustment you suggested earlier didn't fix the behaviour.

[bruce_miranda]

Does anyone know what happens to the OT link if the Orange Pi is powered off or hangs. Is there a path through the circuit on the OTGW board to allow the OT messages to go through?
I am concerned about putting a device in between my heating system that ultimately relies on an SD Card, and all the joy that brings with it.

[anoppe]

@bruce_miranda: I've had sd-card issues with my device, however: I discovered that the heatingsystem and its original thermostat keeps functioning fine, als long as the OPI has power...

[bruce_miranda]

I can see how there is very little dependency on the OPI, because it simply acting as the serial port monitor for the OTGW board, which is running it's own PIC. But I guess I will need to think about how I monitor the power of the OPI itself.
Is there a way to run this board in a pure sniffer/monitor mode. So rather than sat in the middle of the OT bus, it is simply listening?

[cyril]

Nor this board nor original OTGW cannot working this way.

[hvxl]

Because the Opentherm protocol uses current levels for the communication from boiler to thermostat, it is not possible to just attach to the bus and monitor it. A monitoring device has to sit in the OT bus. However, in monitor mode the OTGW passes on the signals in both directions completely in hardware. This is not affected by bugs in the firmware. As long as the OTGW has power and is set to monitor mode, it is as close to a pure sniffer as you can get.

[paulockenden]

I could have SWORN I previously had Cyril's board talking to Domoticz, but now I'm getting errors:

2018-10-08 15:22:42.002 Status: OTGW: HTTP/1.1 500 Internal Server Error
2018-10-08 15:22:42.002 Status: OTGW: Content-Type: text/plain;charset=utf-8
2018-10-08 15:22:42.002 Status: OTGW: Content-Length: 428
2018-10-08 15:22:42.002 Status: OTGW: Connection: close
2018-10-08 15:22:42.002 Status: OTGW: *** INTERNAL SERVER ERROR (BEGIN #105) ***
2018-10-08 15:22:42.002 Status: OTGW: port: 8080
2018-10-08 15:22:42.002 Status: OTGW: socket: sock11bc0b8
2018-10-08 15:22:42.002 Status: OTGW: peerhost: 192.168.xx.xx
2018-10-08 15:22:42.002 Status: OTGW: peerport: 44836
2018-10-08 15:22:42.002 Status: OTGW: rawtime: 1539008561
2018-10-08 15:22:42.002 Status: OTGW: time: Mon Oct 08 14:22:41 UTC 2018
2018-10-08 15:22:42.002 Status: OTGW: errorinfo: can't read "uri": no such variable
2018-10-08 15:22:42.002 Status: OTGW: while executing
2018-10-08 15:22:42.002 Status: OTGW: "regexp {^([^?]*)(\?.*)?$} $uri _ path query"
2018-10-08 15:22:42.002 Status: OTGW: (procedure "getrequest" line 7)
2018-10-08 15:22:42.002 Status: OTGW: invoked from within
2018-10-08 15:22:42.002 Status: OTGW: "getrequest $port $socket $peerhost $peerport"
2018-10-08 15:22:42.002 Status: OTGW: *** INTERNAL SERVER ERROR (END #105) ***
2018-10-08 15:22:42.002 Status: OTGW: Connection reset!

I'm probably doing something stupid. Anyone got more of a clue that me?

Within Domoticz I've simply used the IP address of the Orange Pi Zero, and port 8080.

I could swear I had this all working a couple of weeks ago.

Ta.

P.

[paulockenden]

Don't worry - sussed it - I was being a muppet!

[bruce_miranda]

So what was it? How are you connecting Domoticz to this?