[120] opentherm gateway

[roblom]

Note that the OTGW only supports full-speed serial interfacing via the USb interface. If the Raspberry has a high speed USB interface, this will likely cause issues similar to your findings (it seems to work, but only for a limited time (minutes to hours). Same happens when using an TP-Link WR703N router to make the OTGW LAN/Wireless accisble. Solution is to put an inexpensive USB hub in between the OTGW and WR703N. Dont know is the same problem applies to a Raspberry. (reference: http://www.domoticz.com/forum/viewtopic ... &start=180 )

I used the cheapest USB I could find at home and it seems that it is working now. Domoticz hasn't crashed yet and the data from the OTGW keeps updating.

According to the RPi website.

GENERAL LIMITATIONS

The OTG hardware on Raspberry Pi has a simpler level of support for certain devices, which may present a higher software processing overhead. The Raspberry Pi also has only one root USB port: all traffic from all connected devices is funnelled down this bus, which operates at a maximum speed of 480mbps.

The USB specification defines three device speeds - Low, Full and High. Most mice and keyboards are Low-speed, most USB sound devices are Full-speed and most video devices (webcams or video capture) are High-speed.

Generally, there are no issues with connecting multiple High-speed USB devices to a Pi.

The software overhead incurred when talking to Low- and Full-speed devices means that there are soft limitations on the number of simultaneously active Low- and Full-speed devices. Small numbers of these types of devices connected to a Pi will cause no issues.

The Pi is full speed only splitted. That explains why I have trouble using the OTGW and the serial cable to my Inverter at the same time.
I only do not completely understand why the cheap hub solution works....

[JeroenK]

I've Domoticz installed on my nas. For the connection to the Opentherm Gateway I use a Raspberry Pi.
In Domoticz I see a lot of devices. Including my room setpoint. I add this one. It appears under utility. I checked the favorite icon, so now it's visible under dashboard. When I click on the flame-icon I see the history not the menu where I can change the temp.

Does anyone know the solution?

[trie]

OTGW (fw: 4.2.3) with Domoticz (2.2313) does not work for me. It does not create any devices.

Log says (snippet):

Code: Select all

2015-03-12 17:23:03.377  OTGW: Using serial port: /dev/ttyUSB1
2015-03-12 17:23:04.456  OTGW: SC: 17:23/4
2015-03-12 17:23:30.460  OTGW: SC: 17:23/4
2015-03-12 17:24:00.464  OTGW: SC: 17:24/4
2015-03-12 17:24:30.469  OTGW: SC: 17:24/4
2015-03-12 17:25:00.473  OTGW: SC: 17:25/4
2015-03-12 17:25:30.478  OTGW: SC: 17:25/4

Any ideas? My self written software works fine with this OTGW but I can't get it to work with Domoticz...

-- FIXED: "Allow new hardware devices" in Settings was disabled. After enabling the devices appeared immediately!

[jvandenbroek]

Somehow I only get these kind of lines in the Domoticz log (continuously at the rate as shown here) and it won't update any OTGW devices:

Code: Select all

2015-03-18 17:57:35.942 OTGW: T80000200
2015-03-18 17:57:35.942 OTGW: B40000200
2015-03-18 17:57:36.943 OTGW: T10010600
2015-03-18 17:57:36.943 OTGW: BD0010600
2015-03-18 17:57:37.944 OTGW: T00110000
2015-03-18 17:57:37.944 OTGW: BC0110000
2015-03-18 17:57:38.945 OTGW: T80190000
2015-03-18 17:57:38.945 OTGW: BC01926DE
2015-03-18 17:57:39.946 OTGW: T001B0000
2015-03-18 17:57:39.946 OTGW: B601B0000
2015-03-18 17:57:40.947 OTGW: T80000200
2015-03-18 17:57:40.949 OTGW: B40000200
2015-03-18 17:57:41.950 OTGW: T10010600
2015-03-18 17:57:41.950 OTGW: BD0010600
2015-03-18 17:57:42.951 OTGW: T00110000
2015-03-18 17:57:42.951 OTGW: BC0110000
2015-03-18 17:57:43.952 OTGW: T80190000
2015-03-18 17:57:43.952 OTGW: BC01926DE

This has worked before, I've only changed the serial connection with an ESP8266 directly connected to it. However, otmonitor works fine and does get valid values from the boiler over TCP, so there must be something wrong in Domoticz. Restarted/rebooted the system, no luck. Any ideas? Running the latest beta of Domoticz and OTGW 4.2.3. Thanks!

- SOLVED -
I figured out that I couldn't send any data to OTGW, only retrieve. Some reference voltage wasn't correct, after fixing this, all is fine!

[Rodio]

I figured out that I couldn't send any data to OTGW, only retrieve. Some reference voltage wasn't correct, after fixing this, all is fine!

How did you do this?
I've got the same problem, see a lot in onfo in de log, but no data in Domoticz.
I use a NAS with USB-OTGW.

Thanks

[jvandenbroek]

I figured out that I couldn't send any data to OTGW, only retrieve. Some reference voltage wasn't correct, after fixing this, all is fine!

How did you do this?
I've got the same problem, see a lot in onfo in de log, but no data in Domoticz.
I use a NAS with USB-OTGW.

Thanks

First you should try disabling OTGW in Domoticz and connect to it with a serial program (e.g. minicom). If you see the same output, try sending 'PS=1' , which should give a summary of values on one line. If that works, than all is fine with and somehow Domoticz isn't communication well. Maybe removing and re-adding it will help. Also make sure no other app is using the serial at the same time.

I don't think you should have to change the voltage reference, I had to because I'm using the same power supply of OTGW for the ESP8266 (which unfortunately doesn't work stable yet, because of some excessive current bursts this device generates).

[Rodio]

Ok, thanks.

I know the OTGW is working, because the OTmonitor is giving the info.
I'm gonna try it and keep you posted.

[Rodio]

Hi,

It took sometime, busybusybusy
I tried your suggestions, with PS=1 I get useful info: tapwater temp etc.
If I connect the OTGW to my laptop and start OTmonitor I get all the info I want, so the OTGW is working.

Uninstalled Domoticz, install, old version, older version, same problem every time.
I tried the onboard USB2 and USB3 of my NAS, same problem.
I'm gonna borrow a powered USB2 hub tomorrow.

[hneel]

I have setup a slave RPi connected with opentherm. (My master device is a RPi too). I see the devices on the slave and I can share them on the master.
However, when I change the setpoint on the master, a new thermostat device with the same ID will be created on the slave. They have different Idx numbers, though. This way I can't controll the setpoint from my master device, but only from the slave.

[franzelare]

I have the same issue, I have the opentherm gateway to a slave Pi and when I set a temperature from the slave, all works fine
when I set a tempetature on the master I see in the log file: "Sending SetPoint to device...."
on my slave I see the setpoint coming in: "(OpenTherm) Thermostat (Unknown)"
but my slave creates a new device with a new idx and doesn't change my thermostat setpoint

I think it can be solved with a lua script using otherdevices_lastupdate when you add the new idx that is generated when sending a new temperature from the master and monitoring a status change of the second thermostat. use the new value to update the thermostat setpoint of the open therm gateway on the slave....

I will give it a try later and let you know!

[hneel]

I have changed my configuration. Instead of working with master/slave, I have the 2nd rpi set up as a LAN interface for the OTGW. I have installed ser2net and it works fine.
I only have trouble accessing the own webserver of the OTGW but that's an unrelated issue.
All devices are now directly visible in Domoticz.

[franzelare]

I solved the issue to add the setpoint sent by the slave and named it WoonkamerSetpoint
than I run a lua script named script_device_WoonTempNew
the setpoint of my opentherm gateway is at Idx 22 so I need to transfer the new setpoint 'WoonkamerSetpoint' to Idx 22 with there is an update:


commandArray = {}
if devicechanged['WoonTempNew'] then
current = otherdevices_svalues['WoonkamerSetpoint']
new = otherdevices_svalues['WoonTempNew']
-- print ('huidig:' .. current)
-- print ('new:' .. new)
set = "22|0|" .. new
-- print ('set:' .. set)
commandArray['UpdateDevice'] = '22|0|' .. new
-- commandArray['Tempchange'] = 'on'
end
return commandArray

[Rodio]

Finally found some time.
Re-attached the USB and guess what? now he's working, got feedback

Just shoot me, I've tried this many times, and now ......
Mixed feelings, glad its working, but for how long......

Anyway, just enjoy the moment, and see what we can do now with it

[jvandenbroek]

I've also struggled with it in the beginning, especially when switching between otgw monitor and domoticz things were not working as expected. Good to hear it works for you now

[Rodio]

Thanks,

When the temperatuur drops a bit I'll start playing with the OTGW

GrR

[sincze]

I have the following setup

- OT compatible CV
- TPLINK 703 (ser2net)
- OTGW.

This setup has been working for over a year untill recently.

The display of my room was completely blank.

So I installed OTMonitor on my windows machine directly attaching the OTGW to the USB port.
This system runs without a problem for over a week.

Now back to setup: OTGW -> USB-HUB -> TP-LINK 703.
As soon as I open a minicom session it will start to run
However the display of the thermostat in the livingroom shows an error.

I did not change anything on the TP-LINK

Ser2net.conf:

Code: Select all

10001:raw:0:/dev/ttyUSB0:9600,NONE,1STOPBIT,8DATABITS

.

Minicom_conf

Code: Select all

# Machine-generated file - use "minicom -s" to change parameters.
pu port                /dev/ttyUSB0
pu baudrate         9600
pu bits                 8
pu parity             N
pu stopbits         1

First I thought Domoticz was at fault however as Domoticz is not using the serial connection & minicom also creates problems something else must be wrong.

As soon as I unplug the USB cord from the TPLINK (via the USB HUB) the display in the livingroom functions normally again.
Beats me

Suggestions??

[sincze]

And suddenly it was working..
And after 4 days.... we have the same issue as described above.

Well beats me

[stingone]

I ordered an usb hub, so that I can connect the gateway to my raspberry.
I have already P1 meter and rfxcom connected to usb.
Then I can share the rpi with you. (later this week,I hope)

I have a Remeha Tzerra and a (buggy) iSense thermostat.
Running beta firmware 4.0a11.hex in the gateway.
I modified my gateway with 4 status LEDs (and a power LED) on the outside, using an 8 display.


P.s. My OTgateway is on the second floor, next to the boiler. My Pi is on ground level, next to the energie meters. I used an UTP connection (3wires) between the OTgateway and the USB connector. That is working fine.
I noticed that I had to connect the USB to the raspberry and then restart the OTgateway.

How can i connect the leds / display to the 5 pins on the board???

[sincze]

Nice.

For our soldering heroes maybe have a look ath http://otgw.tclcode.com/peripherals.html

[hneel]

Somehow I only get these kind of lines in the Domoticz log (continuously at the rate as shown here) and it won't update any OTGW devices:

Code: Select all

2015-03-18 17:57:35.942 OTGW: T80000200
2015-03-18 17:57:35.942 OTGW: B40000200
2015-03-18 17:57:36.943 OTGW: T10010600
2015-03-18 17:57:36.943 OTGW: BD0010600
2015-03-18 17:57:37.944 OTGW: T00110000
2015-03-18 17:57:37.944 OTGW: BC0110000
2015-03-18 17:57:38.945 OTGW: T80190000
2015-03-18 17:57:38.945 OTGW: BC01926DE
2015-03-18 17:57:39.946 OTGW: T001B0000
2015-03-18 17:57:39.946 OTGW: B601B0000
2015-03-18 17:57:40.947 OTGW: T80000200
2015-03-18 17:57:40.949 OTGW: B40000200
2015-03-18 17:57:41.950 OTGW: T10010600
2015-03-18 17:57:41.950 OTGW: BD0010600
2015-03-18 17:57:42.951 OTGW: T00110000
2015-03-18 17:57:42.951 OTGW: BC0110000
2015-03-18 17:57:43.952 OTGW: T80190000
2015-03-18 17:57:43.952 OTGW: BC01926DE

I got the same today after restarting the device. My solution was to just recycle the device.

But I have another problem. I have linked my OTGW to my network with a raspberry pi running ser2net and including a usb wifi module. This has run fine for months, but recently it is getting instable. Now after just a couple of days, it will stop sending data. In those cases I can still log in to the device.
I've tried the command "sudo service ser2net restart", but this has no effect. Rebooting helps, but like I said, only for a couple of days.

This is the (relevant) contents of my ser2net.conf file

Code: Select all

BANNER:banner:\r\nser2net port \p device \d [\s] (Debian GNU/Linux)\r\n\r\n

1001:raw:0:/dev/ttyUSB0:9600 8DATABITS NONE 1STOPBIT banner

What could be the problem here?