[120] opentherm gateway

[terrarium]

What kind of opentherm gateway are you using with the TCP domoticz version?
I have the USB version, and using ser2net to make it available via TCP (configure it as RAW and no Banner)
I will monitor what is happening tonight/tomorrow, so far, no issue

Bdw, i am using a WIRED connection on my raspberry pi... you too?

I am using the Assembled gateway - LAN/WIFI. First with only a wifi connection but I heard that sometimes can be unstable.
So I run it wired now.

Code: Select all

1001:raw:15:/dev/ttyUSB0:9600,NONE,1STOPBIT,8DATABITS

For the connection from the DLINK-> USB -> GW. Dlink runs backup-Opentherm-gateway-2013-10-19.tar.gz version

If i run the OTmonitor from a Windows machine and keep it open some time no errors show up.
I am able to set AA=26 to display return temperature (after setting allow external inputs in the menu of the Isense)

I'll let it run for now and see whether or not it will stop reporting over night.

Otherwise i'll setup my 2nd Pi with USB connection directly to make sure that it is not the gateway itself.

Thanks!

Error is still there in the log file.
But it did not stop reporting overnight, so I'm fine with it now.
Maybe the issue will resolve with new firmware for the Dlink or OTGW

[Sappien]

Changing the water temp is not (yet) working





-- edit --

Max_CH Water Setpoint isn't working also

[terrarium]

Managed to get rid of the error.

Was due to a timing error in the ser2net config
I increased the timeout value to 40 and now the error does not show anymore in the log

Code: Select all

root@OTGW:/etc# cat ser2net.conf
1001:raw:40:/dev/ttyUSB0:9600,NONE,1STOPBIT,8DATABITS

[Sappien]

Changing the water temp is not (yet) working





-- edit --

Max_CH Water Setpoint isn't working also

I found the problem.. When I adjus the Max_CH water Domoticz sends SH=50, but SH = maximum central heating setpoint

[gizmocuz]

Okey, so what shall we send?

At the moment:
Room Setpoint -> sends -> TT
DHW Setpoint -> sends -> SH
Max_CH Water Setpoint -> sends -> SW

With kind regards,
Rob

[Sappien]

Room Setpoint -> TT
DHW Setpoint -> SW
Max_CH Water Setpoint -> SH

[gizmocuz]

Okey, i swapped the two... new version available (#1422)

[pwhooftman]

Hi Gizmocuz, can you make both utility controls to set Setpoints, and temperature sensors to display/log/graph the Setpoints values? The reason i am asking is that my iSense thermostat of course sets Room temperature setpoints also on schedule. By displaying the Room Setpoint along the Room Temperature in a graph of the current day, one can see the warmup time (aanwarmtijd) of the room because Room Temperature rise will lag behind Room Setpoint rise. One can then start adjusting the warmup time by playing with the Max_CH Water Setpoint (higher Max_CH Water Setpoint=lower warmup time).

And, a Modulation Level Sensor would be much appreciated.

[pwhooftman]

Managed to get rid of the error.

Was due to a timing error in the ser2net config
I increased the timeout value to 40 and now the error does not show anymore in the log

Code: Select all

root@OTGW:/etc# cat ser2net.conf
1001:raw:40:/dev/ttyUSB0:9600,NONE,1STOPBIT,8DATABITS

Yes, worked like a treat for me too. Thanks.

[Sappien]

small bug found :



Description is missing.

-- edit --

Changing the setpoint of the DHW and the Max Central Heating Water temp isn't working. After changing the values it reverts after a few seconds to his original value.

[pwhooftman]

Changing the setpoint of the DHW and the Max Central Heating Water temp isn't working. After changing the values it reverts after a few seconds to his original value.

Taken from the beta firmware page of the Opentherm Gateway :

Work-around many of the iSense quirks/bugs/misfeatures:
A remote override setpoint cannot be changed
The gateway will first cancel any existing remote setpoint before setting the new one.
Manual change of a remote override setpoint restarts the schedule
When a manual change is detected, the gateway will continue to send the override setpoint so the iSense doesn't resume the schedule.
Program change does not override a temporary remote setpoint
The iSense uses the previously received remote override function (MsgID 100) bitmap at the time the remote override setpoint (MsgID 9) is set. Just like with the remote override setpoint, it doesn't update the remote override function when it receives a new bitmap. The gateway uses the same trick as with the remote override setpoint: After sending the new remote override function bitmap, it cancels the remote override setpoint and sets it again.
Note that the iSense only requests the remote override function about once every 12 minutes. So it may take that long before a remote override is fully instated.
Note: These work-arounds will only be applied if a Remeha iSense thermostat has been detected. So owners of other thermostats will not suffer the negative side-effects (like temporarily canceling the remote override setpoint) of these work-arounds.
Auto-detect the Remeha thermostat type and apply the relevant work-arounds. There is no more need to use the Remeha-specific TR or TQ commands. In fact, those commands are not accepted anymore.
Note: Detection of the thermostat type (especially with a Celcia20) takes some time, so sending a setpoint command soon after a power failure or reconnecting the thermostat may not work correctly.

You can use the 'PR=R' command to determine which thermostat the gateway thinks is connected. It will report:
D: Default, not a Remeha thermostat
I: Remeha iSense
C: Remeha Celcia20
R: Other Remeha thermostat


Of in het nederlands:
Met hulp van Schelte blijkt dat de Isense thermostaat een 'bug' bevat die niet goed kan omgaan met een override setpoint. De workaround voor dit probleem, en dat is trouwens al eens eerder vermeld op dit forum (domoticaforum.eu), eerst een TT=0 commando te sturen, een minuut te wachten en daarna je definitieve temperatuur door te geven.


Re: Opentherm gateway and script integration into Homeseer
Postby Bwired » Sun Dec 02, 2012 1:34 pm

Klopt ik heb ook gestest samen met Schelte.
Als al TT 0.0 is kun je direct het setpoint sturen.
Maar als TT als een waarde anders dan 0.0 heeft moet je eerst TT=0 sturen en zodra deze door ID9 is ontvangen kun je het nieuwe setpoit sturen.
Nadeel is wel dat als je een TT=0 stuurt de Isense zijn normale programma weer even oppakt en dat kan het zijn dat de verwarming weer even aanspringt

Ander handigheidje is dat als je de Isense weer zijn standaard programma wil laten oppakken je gewoon een TT=0 moet sturen

[gizmocuz]

I am able to set AA=26 to display return temperature (after setting allow external inputs in the menu of the Isense)

How did you set this, allowing external inputs in the menu... i have mine on dutch, and in the settings i could not find such an option?

[Sappien]

Menu - Instellingen - Gebruikers instelling - gebruikers niveau > Uitgebreid en dan bij menu - instellingen - installateur - externe ingang > toestaan

[Sappien]

@pwhooftman

Changing the setpoint is working fine.. Just the max water temp of domestic and central heating isn't working..

[gizmocuz]

Menu - Instellingen - Gebruikers instelling - gebruikers niveau > Uitgebreid en dan bij menu - instellingen - installateur - externe ingang > toestaan

You have read the manual !

Only thing i do not get reported back is the DHW Temperature, the Return Hot Water was already reporting back without the above setting. (AA=26)
No idea what it is, but probably my hot water temperature, which i would like to know

[Sappien]

Which model Remeha do you have?

[gizmocuz]

Remeha Avanta 35C

[Sappien]

I've got the Calenta, so maybe that xplains why I've got to add the AA=26... I will ask the developer what the cause can be (DHT)

[pwhooftman]

Hi gizmocuz,

Great to see continuous improvements on OTGW support in Domoticz. May i suggest something concerning the opentherm gateway?

Is it possible to develop a Utility in which one can enter your own command to send to the OTGW (like "TT=20.0" or "OT=10.0")? That way, you have a very versatile utility which i can use in Blocky to send just about every command possible to the gateway, the result given by the gateway could be logged in the Domoticz log. This would be useful for debugging also, i guess.

Also, reading the contents of OTGWBase.cpp, i see all possible MsgId's being defined. Are all those coming to Domoticz in the near future? ( like flame status, burner starts, modulation levels, etc). I'd like very much to learn to add these myself, but dont know how

[tjoep]

The otgw is working great! Maybe you can also add the possibility to choose for temp temporary (TT) and temp constant (TC) when changing the temp setpoint.