[120] opentherm gateway

[macaidwin]

I like the new options for the OTGW.
I am surprised to see that the outside temperature from the sensor chosen to be the outside temperature of the OTGW, is displayed on my thermostat now.
And the thermostat is even using that temperature for tuning the boiler.

I have a buggy iSense and domoticz seems to send the right codes for it (as mentioned before in this topic).

The max_boiler water temp can not be set, but someone mentioned that also before.
And I would like a graph with the return water temperature, but maybe that is not supported by the boiler (Remeha Tzerra)

Thanks for the good work!! Keep on going!

[gizmocuz]

i am thinking about trading my isense for a honnywell

[macaidwin]

i am thinking about trading my isense for a honnywell

I can imagine that... Most of the bugs are already solved by the new firmware in the OTGW.
The firmware is specially adapted for the iSense. Before that the windows client couldn't also change the settings in a reliable way.

I am running beta gateway-4.0a11.hex

From the OTGW website:

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:
Default, not a Remeha thermostat
Remeha iSense
Remeha Celcia20
Other Remeha thermostat

[CodeItAway]

Everytime i restart my pc running Domoticz with the OTGW attached, some devices are added again.
For example the thermostat setpoint is added again, so it is listed twice after a restart. The old device isnt updated anymore. Does anyone recognize this or has a solution?

[gizmocuz]

I do not have this issue (using raspberry pi, connection via TCP), version #1491

[CodeItAway]

Strange. I am running 1.1485 on Windows 7. The opentherm gateway is connected via a com port.
This is a screenshot after a restart of domoticz:

dubbel.PNG (27.58 KiB) Viewed 5053 times

[gizmocuz]

Just restarted domoticz... i keep the same...

Anyone else have this problem (or not ?

[Sappien]

I had this issue 2 weeks ago... But I didn't happen again.

[CodeItAway]

I think i have found the problem.
In OTGWBase.cpp, function UpdateSetPointSensor, the value of dunit on the _tThermostat struct is not set. This value is used for adding/updating the devicestatus.
I'm setting up my pc to compile domoticz to confirm.

[Slorf]

Today i installed my OTGW, all devices are showing up, and i added the Thermostat Set Point.

Question is how to control is ?, i was hoping for a simple +/- button in the webinterface where i could put the thermostat higher or lower.

AM i missing something ?

/Alex

[Sappien]

Take a look at the utility tab.. You can alter the setpoint from there

[Slorf]

There is a edit function, but it means i have to click on the edit button and then change the setpoint.

Would be nice if there was something like a + / - button where you could quickly change the themperature

/Alex

[Sappien]

@gizmo,

After the last update I've got the issue again (with the opentherm devices)

[gizmocuz]

?? bump.... the dunit is still set.... nothing changed....

[CodeItAway]

?? bump.... the dunit is still set.... nothing changed....

Maybe the dunit value was not set to zero prior to the latest fix. Now it is fixed at zero, but it was nonreferenced, so possibly another (static 'random') value.

What would it take to control the setpoint from LUA/Blockly? I would like to create two virtual switches which set the setpoint value.
Is it possible to call functions from LUA? Like SetSetPoint on the mainworker class?

[Slorf]

Yesterday I tried to change the setpoint, but I was changed by my isense after about 30 seconds, I am using the newest beta firmware on my otgw.

After reading all the previous posts I tought this was solved in the newest beta f/w ?

Alex

[Slorf]

Missed something, let's first try and change my isense this evening.

Will report back

Alex

[Slorf]

Enabled the external access menue on my isense, and updated to the newest domoticz beta version.

I can now set the thermostat, I also noticed that when you change the setpoint the isense first goes back to it's normal schedule and after about 30 seconds the change is done.

Kind of weird to start with, but after some experimenting it looks good !!

Alex

[RMU]

Yes, but how/where to enter the setpoint values.

I do like the way the iSense is doing it...

Create a schedule program, for example 'Normal', or 'Holiday',
Edit the schedule
Monday
07:00 Temp=20
10:00 Temp=15
17:30 Temp=20
22:00 Temp=15

Tuesday
....

Then you need to activate one of the schedule programs, for example when you go on holiday you activate the 'Holiday' program

That nice scheduler you have could work nicely for light/switches

Sounds like a nice way to schedule things, do you have any idea when this is implemented at domoticz?

[RMU]

Is it also possible to implement the following things in Domoticz OpenTherm-Gateway functionality?
- Flame status icon (like: green = on, Red = off or something like that)
- Possibility to see if the status of the boiler is in Hot Water or Central Heating mode?
- Error status of boiler (like: green = OK, Red = Error)

So that i can set notifications on it, or see in a graph when hot water/central heating was active.
And maybe even combine some graphs with each other.

At http://otgw.tclcode.com/firmware.html#cmdps i see some options for this:
F: Flame is on
H: Central heating is on
W: Hot water is on
M: Boiler requires maintenance (not sure if this is the right option for display error state)