Devolo Home Ctrl TRV (Danfoss) - Setpoint not working

[blitzkneisser]

Hi!

I recently made my House a bit smarter with Domoticz on a raspberry Pi with the OpenTherm Gateway, an Aeon Labs Gen5 Z-Stick, some Fibaro switches and motion detectors and a bunch of Devolo Home Control TRVs, which are basically a Clone of the Danfoss LC13 with just slightly different Firmware. They are reported to work fine with the Danfoss settings - at least for the basic stuff like Setpoint & co.

Connecting them worked fine. In the beginning the were labelled as Danfoss unknown, id=xx, type=yy, after modifying the XML i managed to make them use the danfoss Z setup.
After connecting them (either as unknown or danfoss) I have a temperature sensor, a setpoint device and a thermostat clock. In the OpenZWave interface i could set additional stuff like weekly programs but that doesn't work as it is currently not supportet afaik.
The Temp sensor works fine. The setpoint accepts the value in the interface, but does not set it on the thermostat itself, it's stuck to the manual value (which is not reported back). Setting the thermostat clock also does not work, there I get an error "Setting the Clock is not finished yet!"

The only thing I'm really interested is setting the Setpoint from Domoticz. Wakeup interval is 300s. Any clues/help?

[gizmocuz]

if you set the setpoint from the control panel, does that work ?
also try with whole numbers like 19, 20, 21...

[blitzkneisser]

Yep, tried that. What also happens is, that neither the Timer set points nor the control panel set points show up in the protocol view...
I just tried doing it directly in the OZW control panel to see what happens

[blitzkneisser]

That's odd... I just figured out that in the Devices Tab now each of the TRVs has two Thermostat SetPoint devices, they did not appear until now.
I have now 4 Devices for each TRV (x is node number, leading zeroes as in the inteface):

Code: Select all

      x01: Temperature (read)
 0000x001: Thermostat SetPoint*
00000x001: Thermostat Clock (wrong, can't be set/modified)
 0000x002: Thermostat SetPoint**

* is the newly discovered one, seems to work (can only test it remotely by watching temperature curves as I'm not home yet), changes are also shown in the protocol. It can also be displayed/modified directly in the OpenZWave interface
** is the one I used before. Can be set, but setting has no effect and is not shown in the protocol!

Z-Wave device list

zwavedevices.jpg (164.46 KiB) Viewed 8305 times

And another question... in the 'network' section of the OZW control panel I have the option to create a scene, obviously some heating schedule for standalone operation (these monday, tuesday,... settings are not visible in the configuration itself). This does not seem to work... is there any workaround or is that just not working (yet)? Same applies to setting the day/time...

I already asked Devolo for the setup commands but I guess I won't get anything back...

[mknops]

Hi Blitzkneisser,

I am struggling with the same issue(s) here! However, I only get one device for the set point. And mine is not updating the physical device as you initially experienced. Also rebooting my Pi did not help.

Can you elaborate on the changes you made to the XML. No clue what XML nor what changes you made.

Secondly: you state that one cannot set heating schedules/timers on the Defolo thermostat. Is that correct? How do you know? If so, can I do so on the Danfoss LC13 as fat as you know?

Thanks for helping me out.

Kind rgeards,

Michel.

[blitzkneisser]

Can you elaborate on the changes you made to the XML. No clue what XML nor what changes you made.

Hi!
Sure. As the Devolo TRV is - except for some software changes - the same as the Danfoss 014G0013 I decided to use the same configuration. This can be done by editing the file manufacturer_specific.xml located in the folder Config in the Domoticz-Folder (for a normal installation that would be /home/pi/domoticz/Config).
In that file search for "Danfoss", somewhere near line 188.
Then, below, just copy the line for the 014G0013 and modify it with a new name and the new ID. For the name you can chose whatever you want, the ID has to be 0175. This should look somewhat like this:

Code: Select all

	<Manufacturer id="0002" name="Danfoss">
		<Product type="0005" id="0003" name="Z Thermostat" config="danfoss/z.xml"/>
		<Product type="0005" id="0004" name="Z Thermostat 014G0013" config="danfoss/z.xml"/>
		<Product type="0064" id="0001" name="RA Plus-W Radiator Thermostat"/>
		<Product type="8004" id="2000" name="RXZ3 RF relay Switching Unit"/>
		<Product type="8005" id="0001" name="Living Connect Radiator Thermostat" config="danfoss/living.xml"/>
		<Product type="0005" id="0175" name="Devolo Home Control Thermostat" config="danfoss/z.xml"/>
	</Manufacturer>

After that I think you have either to exclude and re-include the TRV in the z-wave network or the new onfiguration is updated automatically after a while. Waking the device by pushing the middle button should help.
If everything works fine, you should now have 2 Thermostat Setpoint devices. The first one should work in both diretions, setting a temperature via Domozic and setting a temperature on the TRV and reading that value via domoticz. Just be aware that it can take up to 20 minutes (depending on the wakeup interval which is set in the TRV coniguration) for the TRV to get the nre value. Setting a new value on the TRV should be visible in Domozicz after a few seconds.

And be aware, every time you update Domoticz you have to do the XML modification again, a new domoticz version also updates the OpenZWave software which overwrites that manufacturer_specific.xml file

Secondly: you state that one cannot set heating schedules/timers on the Defolo thermostat. Is that correct? How do you know? If so, can I do so on the Danfoss LC13 as fat as you know?

I can't find the posting right now, but the answer is somewhere here in the forum. As I understood it, there are 2 possibilities for scheduling temperatures on the TRV. First one is to set a schedule in the TRV directly (which does not work). Second one is to have a Schedule in domozicz, which is working and gives you much more possibilities. As these two methods are somehow not compatible (the built-in climate schedule uses temperature difference vs. absolute temperature values) the programmer(s) behind domoticz had to chose one of these possibilities and for having more flexibility they decided in favour of the domoticz (not TRV built in) method, which works fine and really offers much more possibilities.

[mknops]

Hi Blitzkneisser,

Mnay thanks for the extended and detailed answer. In short: works like a breeze after adjustment of the XML, restart and re-include of the thermostat! Now, interestingly I just have one set point device for the thermostat, but it works. The only device that does not work is the "clock device"......however....

I found scheduling to work from Domoticz (as you explained, thanks again!, which is exactly what I was looking for. No need for any correct clock in the Thermostat itself.

Regards,

Michel.

[blitzkneisser]

Fine that you got it working.
The only advantage of having the thermostat-internal scheduling would be that the thermostat could also switch if there is no connection to domoticz for whatever reason.
But the huge advantage of the domoticz scheduling variant is, that you can not only use the fixed schedules but also lua skripts, events, etc. - which gives you an endless degree of freedom
Yep, the clock device is not needed for normal operation, just for the internal schedule.

Only thing is, that I've read that the thermostat opens fully for a few seconds for maintenance once a week, always on thursdays around 11 - depending on the internal clock. But it's not a problem if that happens at another time.
There is one way to set the internal clock... completely reset the thermostat and reactivate it on sunday at midnight, that should start the internal clock properly

And regarding that 2nd set point... I just checked and found out that I only have that for the first thermostats I added before the XML change, not for the more recent ones. So this is most likely a "ghost" from the past and one less reason to worry about that.
They don't do any damage or serve any pupropse, but I think I'll clean up my configuration manually to remove them... for the sake of cleanness

[bullrin]

Many thanks for the tip to adjust the xml! Someone created an issue on Openzwave at Github to add this line!

Did you also get the current temperature from the Devolo TRV? Because this is why we bought this one and not the danfoss device

[trollmar]

I get the Temperatur After the XML modification

Gesendet von meinem D5503 mit Tapatalk

[blitzkneisser]

Yep, reading the temperature works fine for me, I have a separate thermometer device in domoticz.
And I added the one-line fix for this issue to open z-wave github, let's hope it is fixed soon...

[Egregius]

I wonder what the difference is between the Danfoss and the Devolo. They seem to be exactly the same.
Reading the temperature is a huge plus for the Devolo, but why isn't that possible in the Danfoss?
Is that because it's other firmware?

[LouiS22]

A bit offtopic, but I've spoken with local Danfoss rep, he mentioned a new DanfossTRV is coming with temp reading sometime in Q1, early Q2. My best guess (could be wrong though) that Danfoss will sell the ones they manufactured for Devolo, just with a different (Danfoss name) and numbering.

[blitzkneisser]

There are 1 or two other brands that sell the Danfoss TRVs under their own name. Only difference is the firmware, as all the other companies also sell their own z-wave controllers, the firmware is adapted to support these.

Gesendet von meinem A0001 mit Tapatalk

[bullrin]

I have also added the one line fix in the xml and then reincluded the thermostats. But I can't see a seperate thermostat...
Look on my Device List.


Also i can't use the thermostats at the event builder. The device can't be used to set the temperature.

[blitzkneisser]

I have also added the one line fix in the xml and then reincluded the thermostats. But I can't see a seperate thermostat...
Look on my Device List.


Also i can't use the thermostats at the event builder. The device can't be used to set the temperature.

When the TRV is successfully included with the new configuration you should have 3 devices:

domoticz-trv.jpg (69.61 KiB) Viewed 7751 times

1x General/Thermostat Clock (obsolete, can be ignored)
1x Thermostat/SetPoint
1x Temp/TFA 30.3133

The Thermostat/SetPoint is the right one to modify for changing Temperature. If it doesn't work the TRV is most likely using the old configuration. Do you have the Temperature device too? I don't see it in the list.

I don't remember how it was in my case, I did not use the control blocks much, I changed to LUA scripts early on - much more possibilities.
But I'm not sure it it worked there. There's one good way of checking the functionality:

First, keep in Mind, that changing the Temperature in Domoticz is not reflected immediately on the TRV. depending on the wakeup-Settings the TRV connects to Domoticz every 10-15 Minutes to get the new Set value. You can shorten that duration in the Z-Wave-Configuration, but this reduces battery runtime if the device wakes up too often.
But for testing:

1) Set a new Temperature value on the Set Point device in Domoticz. Then press the middle button on the TRV to wake it up. It should then connect to domoticz and you should see the new value on the display immediately.
2) Set a new value directly on the TRV. The change should be displayed on Domoticz with only a short delay.

Be aware, when you modify the XML file and update domoticz, that modification is also overwritten! And I modified the OpenZwave-Config on Github and the change has been accepted, so in the next Version of OpenZwave it should no longer be necessary to modify the XML file, the Devolo TRV shoudl work from scratch

[bullrin]

I'm not getting the TFA Device. I tried again today to exclude and include the Device over OpenZwave Interface. It's still not coming... Maybe there is something wrong?

Don't know whats the problem is. My XML file is also correct.

The TRV is working well, i can set the temperature over Domoticz. Only in blockly it can't be set, because it is not recognized as a correct thermostat, i think.
But maybe I will change to LUA. But I like the easy way with blocky

[blitzkneisser]

Ok. Try to make an update via the domoticz interface and keep the TRV awake with the button. Maybe the z-wave interview was not complete...

And are you sure you don't have the TFA device? In the device list the devices are normally not sorted properly when you sort via address as the same address is sometimes displayed with a different number of digits. Go through the list item for item, maybe you already have it.

And start with LUA. It's quite easy and you have so much more possibilities

Gesendet von meinem A0001 mit Tapatalk

[bullrin]

Yes I'm sure, there is no TFA device. The screenshot from my device list, shows all devices.

What do you mean with an update? Is there any button to restart the interview?

[blitzkneisser]

I'm using the lower right update button in the Z-Wave node view in Domoticz.

You can also check what configuration is used for your TRV by checking the zwcfg_0xxxxxxxxx.xml in the domoticz/Config directory
This file should show the new configuration. If this still has old data, the exclude/include did not work. But if settign a temperature works, the config should have been updated properly...