Domoticz

Strange, don't have this issue here....

I just noticed that my domoticz says its still at 1645. Is this an issue in the update file or is my domoticz really now updating?

PS: I have tried to manually download the update file but the issue remained after that.

I have a Nefit Smartline with Opentherm converter module, and the Honeywell Chronotherm Vision Modulation (TH8110M1003) Thermostat.
Both are connected to the Opentherm Gateway running the latest stable version 3 firmware on it.

In domoticz it all is working just fine!

There is one little detail i noticed and wanted to share: When sharing all the Opentherm devices from a slave domoticz to a master domoticz you cannot change the Room SetPoint from the master, but you can change it from the slave.

Also i would love to see the modulation level and the water pressure details in Domoticz, which doesn't work at this moment.
These values are displayed correctly in the otmonitor application so the nefit converter and the OTGW seem to be working fine.

gizmocuz wrote:

macaidwin wrote:I like the new implementations of the OTGW switches.
I rather have them under Utility, but this is okay for now. And I would like to combine the graphs of various states. For example flame-state, CH_active and DHW_active.

But another thing, I can change the thermostat setpoint by hand, but when I use a blocky event to do this, it doesn't work.
I also can't change the domostic hotwater setpoint and the Max_Ch water setpoint (by hand, I didn't try an event for this).

i am thinking about making a thermostat view with all sensors/switches etc..

Can you change those set points with the opentherm monitor application?

Sorry for the late response. Good question, I had to check that out and indeed, I can't change the setpoints with the windows application. The application is sending commands, but I think my boiler and/or thermostat doesn't support changing these set points.
So it's not strange domoticz can't do it either.

And about the thermostat set point, I can edit it manually in domoticz, working fine. But in Blocky events it's still not working.
I want to make something like: When backdoor is open, set room setpoint to 17 degrees, to avoid the boiler from heating the garden...

gizmocuz wrote:Strange, don't have this issue here....

Running 1657 i still cannot remove the protection from the setpoint device. Its working fine for switches tho.

Using the opentherm nefit converter on the smartline HRC24 with Honeywell chronotherm vision modulation thermostat the system is not working ok as the Control Setpoint switches between the normal temperature for heating the house and a fixed 10 degrees every 5 minutes.

Example:

3/27/2014 13:45 60
3/27/2014 13:50 10
3/27/2014 13:55 59
3/27/2014 14:00 10
3/27/2014 14:05 57
3/27/2014 14:10 10
3/27/2014 14:15 57
3/27/2014 14:20 10
3/27/2014 14:25 56
3/27/2014 14:30 10

Anyone else also has this behaviour ?

Solved:
The Honeywell Thermostat has a feature called low-load/off which was enabling and disabling the boiler each 5 minutes. Switched this feature off in usermenu and now all is working as expected.

When using Opentherm Gateway with firmware 4.0 beta 3 -> the DHW Setpoint is always 0 in Domoticz. This is the data from the gateway:

00000011/00000010,43.00,00000000/00000000,100.00,0/0,20.00,0.00,1.60,19.90,35.40,54.50,12.20,34.80,0/0,0/0,0.00,70.00,72990,0,0,58340,146460,0,0,0
The sixteenth value is DHW Setpoint, which seems to be reported as 0 in this beta firmware.
(never mind the fourth and fifth last value, the beta seems to add a zero to the end of the numbers in most but not all reports)

Firmware 3 was reporting the DHW setpoint correctly.

Ahhh that explains, i thought it was just my cv... Hope it will be fixed

I noticed another little something:

Changing the Room SetPoint always has to be done twice in a row to make domoticz send TT:<new value> to the OTGW only in the second try.

Also it takes about 2.5 minutes for the thermostat to actually change the setpoint value in its display to the new value.

When using PS:1 to get details from the OTGW like domoticz does, it seems the otgw doesn't report system water pressure, and doesn't report relative modulation level.

When the OTGW is in it's default reporting mode (direct reporting of all OT messages) then these values are reported correctly. Maybe Domoticz can use the OTGW in the default reporting mode and update the domoticz-sensor-values at the moment a new value is received from the otgw? This would make the sensors in domoticz show all values almost in realtime.

DatafoxChris wrote:I noticed another little something:

Changing the Room SetPoint always has to be done twice in a row to make domoticz send TT:<new value> to the OTGW only in the second try.

Also it takes about 2.5 minutes for the thermostat to actually change the setpoint value in its display to the new value.

I only have to give in a new setting once. It takes a while, but the new setting is adopted by the thermostat. But this is how opentherm works. This is the same when using the windows application.
I have a buggy isense, so I use beta firmware in the gateway. In this case the gateway first has to send TT=0 to set the thermostat to original thermostat setting after that it can send the wanted setting. This firmware solves the isense bugs in this way

I was looking at a log-window which shows the serial data going back and forth between domoticz and the OTGW, that is how i concluded that domoticz doesn't sent TT command the first time i change the Room Setpoint in the webinterface... However i must admit that i was only actually seeing the data from the transmit-pin of the otgw, so i only see acknowledge messages but not the actual command sent out bij domoticz. I only saw one acknowledge in the form of "TT:21", and that was after my second try.

The OTGW does report the much wanted sensor values when in default reporting mode:

23:25:46.115610 BC0110000 Read-Ack Relative modulation level: 0.00
23:25:49.834102 BC01201B3 Read-Ack CH water pressure: 1.70

DatafoxChris wrote:I was looking at a log-window which shows the serial data going back and forth between domoticz and the OTGW, that is how i concluded that domoticz doesn't sent TT command the first time i change the Room Setpoint in the webinterface... However i must admit that i was only actually seeing the data from the transmit-pin of the otgw, so i only see acknowledge messages but not the actual command sent out bij domoticz. I only saw one acknowledge in the form of "TT:21", and that was after my second try.

I understand, my experience is that when I manually change the setting it just takes a while. I do not have to send it twice.

OTGW firmware 4 supports thermostat-less operation. Domoticz would be able to send Control SetPoint (desired DH water temp) to the boiler based on some simple calculations on room temperature (from any temp sensor connected to domoticz) and the desired room temperature (maybe some thermostat-sensor in utility tab). The OTGW firmware 4 even supports connecting a digital 1-wire temp sensor.

Room Temp = 18
Room SetPoint = 20
20 - 18 = 2 degrees need to be added: Set the Control SetPoint to max DH water temp for about 5 minutes, then lower it as the room temp rises. When Room SetPoint - 0.5 has been reached, stop the heating by sending Control SetPoint to 10 degrees (boiler will stop heating), as the room temp will continue to rise somewhat after the boiler stops heating. Note the average time it takes for one degree to be added, and you can even call it 'Self Learning Thermostat'.

This would essentially turn Domoticz into an autonomous thermostat, and you could add a four-point heating-program as well

I was using The OTG with Domotiga for over a year now but I'm now experimenting with Domoticz instead.

I'm wondering if anyone has tried setting the setpoint from a Lua script or a json URL.

I tried the following:
JSON: http://192.168.178.24:8080/json.htm?typ ... value=17.5
LUA:
if (devicechanged['Thuis schakelaar'] == 'On') then
commandArray['UpdateDevice']='29|0|20.5'
end
if (devicechanged['Thuis schakelaar'] == 'Off') then
commandArray['UpdateDevice']='29|0|16'
end
return commandArray

This changes the value of the device but is does not actually executes the 'TT: 17.50' command.

Waterpressure is reported in PS:1 reports:

00:39:57.617781 00000000/00000000,10.00,00000000/00000000,100.00,0/0,15.00,0.00,1.30,19.76,51.20,48.30,10.90,41.70,0/0,0/0,0.00,70.00,8869,0,0,59136,14684,0,0,0

Could you add this water pressure value to Domoticz as a sensor?

DatafoxChris wrote:Waterpressure is reported in PS:1 reports:

00:39:57.617781 00000000/00000000,10.00,00000000/00000000,100.00,0/0,15.00,0.00,1.30,19.76,51.20,48.30,10.90,41.70,0/0,0/0,0.00,70.00,8869,0,0,59136,14684,0,0,0

Could you add this water pressure value to Domoticz as a sensor?

Lucky you... i do not receive this value (always zero on my Remeha)

I added a new Pressure sensor (Bar) in version #1676, hope all is working well... (beta will be uploaded within an hour)
/Rob

Yes it works perfectly, you rock !

THANKS

Who can change is Hot water or CH water temperature?





When I change it, it reverts immediately back to the original value