Getting Danfoss living connect Z-Wave radiator thermostat to work

[jakob...@gmail.com]

Hi,

I have a Danfosslem "living connect z" Z-Wave radiator thermostat that I would like to control via openHAB.  I'm using an Aeon Labs USB Z-Stick S2 as my Z-Wave controller.  The basic setup seems to work (3 zwave nodes are found), but there is some problem during initialization so that I'm not able to read or write any information from/to the zwave thermostat node(s).

I have put my zwave.log and the node1.xml (the z-stick controller) into a gist here:  https://gist.github.com/jhilden/10601115

I'm using the stable release of openHAB 1.4.0 together with the current master version of HABmin from GitHub and the zwave binding that comes with it.

In HABmin the Z-Stick controller (node 1) is displayed with status green and complete manufacturer/product information, while the other two nodes (nodes 2 & 4) are grey and have no information.

I understand that I might need to add the device to Z-Wave Product Database https://github.com/cdjackson/HABmin/wiki/Z-Wave-Product-Database, especially since its a quite new firmware version of that thermostat.  It has software version 1.00 and SDK 4.55, released January 2014.  It should be slightly newer version of this one:  http://www.pepper1.net/zwavedb/device/489.

However, I'm not quite sure how and where exactly I would add the device to the product database.

Also, I'm not quite sure if my Z-Wave network is correctly setup,  If anybody has some tips for it would be highly appreciated.  It seems as if Z-Wave is a quite complicated protocol and I'm even thinking whether Homematic might be the currently better solution for controlling your radiators with openHAB (even though its more proprietary).  Does anybody here have an opinion on that?

Thanks in advance for the great work on openHAB,

Jakob

[daniel....@gmail.com]

Hi,

can you control them from OZWCP?

Possible the devices have new ID's which have to be added to the database first to get them correctly in HABmin.

Can you post your .items file or the relevant lines of it?

Regards,

Daniel

[Chris Jackson]

I wonder how long you left your network to start up? The Danfoss are battery devices, and they will only wake up very occasionally (I dont know how often). From your log I don't see anything being received from the node.  I just had a quick look at the manual, and it says you can press the 'select' button to wake it up for 5 seconds.  So, you might need to do this at least once to get the device talking.

If that starts communications, then the next thing you will need to do is configure the WAKEUP class. In HABmin, this should (hopefully) be displayed under the respective node (but note that this will only show up AFTER the initial communications above is complete). You should be able to change the wakeup period - again, you will probably need to press the select button to wake the device up so that this configuration is actually set.

Once the wakeup is configured, you won't need to keep pressing the select button, but you should be aware though that any communications to the device will only happen at the wakeup period (this is 'control' type comms - other communications such as sending thermostat status might happen at different times - I'm not familiar with this device).  This also means that if you restart the binding, the 'light' in HABmin will show grey until after the wakeup is received - don't worry about this - it's just the way battery devices work in zwave (and this is quite confusing, I know).

I hope this helps...

Chris

[Marc Sauveur]

Hi Jakob ,

 

 

have you found solution of your problem ,

i have buy living connect and don't controle from openhab

if it's working for you can you pst your item?

thx.

 

Br's

 

 

Marc

[Samuel Lorette]

Hello,

I just bought a Danfoss Living Connect (LC13) and I also have some difficulty to use it.

When I wake up the Living Connect, then in habmin start a Heal Process, I see this into the logs :

22:10:29.674 DEBUG o.o.b.z.i.c.ZWaveConfiguration[:259]- NODE 6: No database entry: Danfoss [ID:4,Type:5]

This line repeat many many times.

I looked at this place http://www.pepper1.net/zwavedb/device/489 and the devise seems to be documented but I ask me if the XML is good there. If I'm correct, Habmin use this database when it include a new node.

Can you help me to use this devise with Openhab?

Thanks a lot in advance,

Samuel

[Jakob Hilden]

Hi Marc, Hi Samuel,

I did get it mostly to work in the end, but I haven't worked on it since, because I didn't need thermostat control over the summer.  However, I'm planning to get back to it soon, as winter is approaching, then I will share my complete config with you.

Cheers,  Jakob

--
You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/oG58xAdvcx8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.
For more options, visit https://groups.google.com/d/optout.

[Samuel Lorette]

Hi Jakob,

Thank you in advance!

[Jakob Hilden]

Hi,

I'm back at it now and I put my configuration on GitHub here:  https://github.com/jhilden/openhab_config/   Maybe it can become helpful for somebody at some point.

I also do see the "NODE 6: No database entry: Danfoss [ID:4,Type:5]" entries in my zwave.log, but I don't think that this is a serious problem.  In general the thermostats do  work anyway.

The only big issue I'm facing right now is that the thermostats are waking up far too infrequently.  I still have to figure out how to send the required WAKE_UP_INTERVAL_SET command to the device.  Any help with that would be appreciated.

Greetings,

--Jakob

[universal...@googlemail.com]

Hi All,

I had quite some problems with these thermostat myself.

Apparently the major issue is that they do not initialise properly. I got around it by resetting openhab multiple times and then during startup pressing the middle button (to wake them up several times) sometimes I deleted the corresponding xml file (if the file contained errors) in the end I got all of them to talk to openhab.

Now my remaining problem is that the batteries drain really fast. I think I have to replace them almost every two weeks or so, While they used to last for a year using z-wave.me (the software that came with the razberry module I'm using.

The wake-up interval can be set through cabman (I have mine currently set to 300 sec). 

this is how I have them configure in the item file:

Number  thermostat6setpoint  "Thermostat Kitchen [%.1f C]"   <heating>   (g_heating,g_kitchen)  { zwave="41:1:command=THERMOSTAT_SETPOINT, repond_to_basic=true" }

[Chris Jackson]

Now my remaining problem is that the batteries drain really fast. I think I have to replace them almost every two weeks or so, While they used to last for a year using z-wave.me (the software that came with the razberry module I'm using.

The wake-up interval can be set through cabman (I have mine currently set to 300 sec). 

I don't think the binding should impact the battery life since that is mostly set (I think) by the wakeup period - ie the binding can only talk to the device when it wakes up. 300 seconds is quite fast, although I don't know how much difference it makes to battery life versus using a slower time (eg I have most of my devices set to 1 hour).

One possible exception, and something to check is that the device does go back to sleep after it wakes up. Normally this should happen 2 seconds after wakeup. Maybe the binding is continuously sending data that is keeping it awake - it's worth checking just to be sure.

Chris

[universal...@googlemail.com]

Hi Chris,

thanks for answer. the 300 secs was the default value of the thermostat. If I set it to 3600secs then if openhab wants to send a new set_point value to the thermostat it would take 1hour in the worst case - This would be very impractical since the heating should react somewhat fast to things like opening a window or me feeling cold while reading etc....

[Chris Jackson]

Fair point - I thought the device was meant to be (sort of) autonomous and ran its own schedule... I guess you're overriding this from other sensors...

Anyway, if you can grab a log of the zwave debug file for 5 or 10 minutes that ought to capture at least one wakeup cycle and I'm happy to take a look at what's happening - just to make sure the binding isn't sending stuff it shouldn't which might keep the device awake.

Cheers

Chris

[universal...@googlemail.com]

not really from other sensors. The device runs on its own once set to a certain temperature. But I might not be happy with that temperature a couple of times, in which case I need to change the set point. Thats not often per day, but when I want the room to be 23°C instead of 20°C I want it to happen fast and not an hour later. 

I have also set up a window contact to shut down the radiator when the window is open and that also needs to react faster than on an hours notice ;-)

I attched a log file of the last 5 minutes or so. The interesting devices are 2, 8, 33, 35, 40, 41, 42

[universal...@googlemail.com]

Hi Chris, 

could you spot anything irregular in the log?

thanks

steffen

[Chris Jackson]

Strange - I did send a response to this, but it's not made its way onto the list. Unfortunately I can't access my home email from work :( so I'll dig out my response when I get home tonight.

Chris

[Chris Jackson]

Hi,

I found my message stuck in the drafts! :(

I took at look at the log and can't see anything out of the ordinary. The binding isn't sending lots of data that could keep the node alive, and it is telling it to go to sleep, and I then see a wakeup 5 minutes later. So, as best as I can tell, there's nothing that should be affecting battery life.

If I pick on one node, we can see this below... The device is only sending one message (a multi_cmd with all of its information). It's awake for 2 seconds (also correct) and then goes back to sleep.  The next wakeup after this is just less than 300 seconds later - at 11:54:33, so all looks fine (at least I think so).

Chris

2014-11-05 11:49:41.330 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:37]- NODE 8: Application Command Request (Stage Node Complete)

2014-11-05 11:49:41.333 DEBUG o.o.b.z.i.p.s.ApplicationCommandMessageClass[:55]- NODE 8: Incoming command class MULTI_CMD (0x8f)

2014-11-05 11:49:41.342 DEBUG o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:56]- NODE 8: Received Multi-Command Request

2014-11-05 11:49:41.344 DEBUG o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:93]- NODE 8: Calling handleApplicationCommandRequest.

2014-11-05 11:49:41.346 DEBUG o.o.b.z.i.p.c.ZWaveBatteryCommandClass[:74]- Node 8: Received Battery Request

2014-11-05 11:49:41.353 DEBUG o.o.b.z.i.p.c.ZWaveBatteryCommandClass[:84]- Node 8: Battery report value = 0x3E

2014-11-05 11:49:41.391 DEBUG o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:93]- NODE 8: Calling handleApplicationCommandRequest.

2014-11-05 11:49:41.452 ERROR o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:90]- NODE 8: CommandClass CLIMATE_CONTROL_SCHEDULE (0x46) not implemented.

2014-11-05 11:49:41.455 ERROR o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:90]- NODE 8: CommandClass CLOCK (0x81) not implemented.

2014-11-05 11:49:41.457 ERROR o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:90]- NODE 8: CommandClass CLIMATE_CONTROL_SCHEDULE (0x46) not implemented.

2014-11-05 11:49:41.460 DEBUG o.o.b.z.i.p.c.ZWaveMultiCommandCommandClass[:93]- NODE 8: Calling handleApplicationCommandRequest.

2014-11-05 11:49:41.472 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:128]- NODE 8: Received Wake Up Request

2014-11-05 11:49:41.474 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:181]- NODE 8: is awake

2014-11-05 11:49:41.492 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:403]- NODE 8: Is awake with 0 messages in the wake-up queue.

2014-11-05 11:49:43.494 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:477]- NODE 8: No more messages, go back to sleep

2014-11-05 11:49:43.496 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:210]- NODE 8: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION

2014-11-05 11:49:43.498 DEBUG o.o.b.z.i.p.SerialMessage[:108]- NODE 8: Creating empty message of class = SendData (0x13), type = Request (0x00)

2014-11-05 11:49:43.539 DEBUG o.o.b.z.i.p.c.ZWaveWakeUpCommandClass[:364]- NODE 8: Went to sleep

[universal...@googlemail.com]

Hm... I changed the wake-up time to 600 to see if that maybe makes things better.

Will keep an eye on it...

[Norman Sand]

Hi all,

I also have now a Danfoss Thermostat included and working. But I still need to set the wakeup-interval, but I can't find a way to do this via habmin. In some postings here it is stated that you should be able to do this. Can someone give me a hint, where I can set the wakeup-interval?

In the overview of the node I only have "Status" and "Information". (If I trigger the communication by pressing the button on the thermostat manually I receive updates from or to the thermostat, so the binding works.)

Thank you very much!

Cheers

Norman

[Chris Jackson]

There should be a Wakeup folder, but it sounds like your device isn’t in the database. I’ve just added a new device today, so it might help, but if you can tell me the type/id that HABmin reports and I’ll add it to the database.

Chris

[Norman Sand]

Hi Chris,

I tried already the new addon from today's release, but it doesn't help. HABmin reports "Danfoss [ID:4;Type:5]". I can't tell you how appreciated your help is! This is the second time! 

Norman

[Chris Jackson]

Hi Norman

I only added this yesterday, so it will be in the latest version today, but it is the same id as yours so hopefully it will work if you now grab the latest from cloudbees. 

Cheers

Chris

Sent from Samsung Mobile

--
You received this message because you are subscribed to the Google Groups "openhab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openhab+u...@googlegroups.com.

To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/73e04d44-c2dc-44ae-93ec-203626b9ff8c%40googlegroups.com.

[Norman Sand]

Hi Chris,

I wasn't aware of that repository, I always used the builds on the habmin github-repo. We are talking about this one, right? https://openhab.ci.cloudbees.com/job/openHAB/org.openhab.binding$org.openhab.binding.zwave/

I have problems downloading the last build #804 (which was pushed there indeed only a few hours ago), because it seems to have failed: https://openhab.ci.cloudbees.com/job/openHAB/org.openhab.binding$org.openhab.binding.zwave/lastBuild/

I only get build #803, which is a few days old.

Do I miss something.

Thank you very much!

Norman

[Chris Jackson]

Hi Norman,

Ok - no probs (I’m never sure who is using what version - sorry for the confusion).

I’ll create a new version in a few minutes and put it on the HABmin site - I’m just adding another device to the database, so give me 5 or 10 minutes…

Cheers

Chris

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/52307301-5346-4272-84d3-272dd3396062%40googlegroups.com.

[Chris Jackson]

Ok - that’s now loaded. Let me know if the device is now recognised.

Cheers

Chris

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/EA9AD769-B56C-43A1-A9C8-56ABA88DDE22%40cd-jackson.com.

[Norman Sand]

Great! It works like a charm! Thank you very much for your effort! This is very appreciated!!!

Cheers

Norman

[Samuel Lorette]

Hello Normal,

Could you resume me what did you configure (item and sitemap) in order to have the LC13 working?

Thanks in advance,

Samuel

[Phil K.]

Hi Steffen,

Did you see any change? I do have the similiar problem and have changed some to 1800sec to at least have an update every 30min. But I don't really think that it was getting better....

Phil

[hl_at]

Hello Samuel!

LC 13 works with:

Items:

Number Thermostat "Room [%.1f °C]"   <heating> (All,gTemp) { zwave="XX:command=thermostat_setpoint,setpoint_type=1,setpoint_scale=0,refresh_interval=900" }
Number batt_Thermostat "Thermostat Room [%d %%]"  <sewerage> (All, gBattery)  { zwave="XX:command=battery,refresh_interval=3600" }

Sitemap:

Setpoint item=Thermostat minValue=4 maxValue=30 step=0.5
Text item=batt_Thermostat

Regards,

Herbert

P.S.: Same config as for LCZ251

[Samuel Lorette]

Thank you Herbert.

I'll try tonight. I wasn't far from that, but without the setpoint_type AND setpoint_scale.I don't know if that's the reason of my problem (the thermostat not getting the new setpoint behalf if I force the wakeup).

Can you also confirm me that if I change the setpoint on the thermostat, openhab should be informed of this (after the next wakeup)?

As I included the devise into the z-wave network before this devise was usable, I asked me if the devise received a correct wakeup value. Maybe I should rather exclude it, do a factory reset and include it again to be shure.

I'll let you know.

[hl_at]

Can you also confirm me that if I change the setpoint on the thermostat, openhab should be informed of this (after the next wakeup)?

Confirmed! Let us know if it works! 

[Alex Bartiş]

Sorry for hijacking, but maybe someone here can help me with an answer. Can this thermostat be used to report temperature? Meaning, can I use it like a temperature sensor, to report from the room it is?

[Jakob Hilden]

Hi Alex,

no, (as far as i know) this thermostat can not be used to read the temparature of the sensor inside. One can only read/write the "setpoint" temperature.

But even if that would be possible, you would get pretty bad results right next to your radiator.

Hope this helps,

--Jakob

[Alex Bartiş]

Didn't think of that, that is a good point. Thanks!

-- --

"Nu lasa nimic intre tine si visele tale."

--

Alex Bartis, 
iOS Developer @ Fortech

www.alexbartis.com | facebook.com/bartis.alex | twitter.com/alexbartis

--

You received this message because you are subscribed to a topic in the Google Groups "openhab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openhab/oG58xAdvcx8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openhab+u...@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at http://groups.google.com/group/openhab.

To view this discussion on the web visit https://groups.google.com/d/msgid/openhab/b89d9f3d-ce8c-4630-939f-14baa044875d%40googlegroups.com.

[Kaz Librowski]

I have the same problem with my Danfoss. A device that claims 2 year battery life is draining its batteries in 2 weeks. 

I think this is because I get the following errors in my log every 5 minutes (the wakeup period as reported by Habmin is the default 86400, which is way more than 5 mins):

2015-03-10 00:18:38.097 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 5: Unsupported command class CLIMATE_CONTROL_SCHEDULE

2015-03-10 00:18:38.105 [ERROR] [ApplicationCommandMessageClass] - NODE 5: Unsupported command class CLIMATE_CONTROL_SCHEDULE (0x46)

Is it possible that because the Danfoss doesn't receive whatever reply it is expecting from the controller, it keeps asking and hence drains its battery?

As it stands, the device is effectively useless, since having to change batteries every 2 weeks makes it neither convenient nor a money saver.

[Kaz Librowski]

Just following up on my own posting very quickly. I deleted the xml file, restarted openhab, and now the problem seems to have gone away. I also now have a wakeup interval of 300, which I think is 5 mins?

More importantly, the charge level of my battery has stopped plummeting, so hopefully this one will last a bit longer, but it's too soon to tell.

It all seems very hit and miss, and if I'm honest I don't know why I deleted the xml file, other than I dimly remember this being mentioned somewhere in the forum.

Is there some sort of troubleshooting guide for zwave on openhab? 

[Chris Jackson]

Is there some sort of troubleshooting guide for zwave on openhab? 

I can only suggest using the log analyser - it's far from complete, but it tries to detect some common problems.

Chris