Z-Wave: Danfoss Living Connect thermostat: unable to control them...

[Jones]

Hi guys,
I have bought Danfoss’ new z-wave (Danfoss Type ID 014G0001) thermostats for all my radiators, but I cant control they though LinuxMCE  
The devices has been added successful to LinuxMCE and are shown as Standard Thermostats (based on Device template # 1754), and and data such as battery status is shown just fine in LinuxMCE and a test of my FlexControll Smoke Dector is firering of the Fire scenario, so I think that the basic Zwave is working...

However, I’m unable to set the temperature using the test buttons such as the “72 deg.” Button on the climate device page.

Has anyone had success using this brand new z-wave devices with LinuxMCE 8.10?


Please help me out


Here is a dump of my Z-wave controller log:

_{========== NEW LOG SECTION ==========1   
09/23/11 16:01:58   33 (spawning-device)   Starting... 11   
09/23/11 16:01:59   33 (spawning-device)   Found /usr/pluto/bin/ZWave01   
09/23/11 16:01:59.126      TranslateSerialUSB pci0000:00/0000:00:1d.1+2 result /dev/ttyACM0 <0xb70f26c0>01   
09/23/11 16:01:59.130      ERROR! Out of frame flow!! <0xb68f0b90>05   
09/23/11 16:01:59.131      Creating child 34 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>
05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 77 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 78 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 79 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 80 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 81 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 82 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 4 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 35 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 66 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.131      Creating child 67 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05
09/23/11 16:01:59.131      Creating child 68 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05
09/23/11 16:01:59.131      Creating child 70 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   09/23/11 16:01:59.131      Creating child 71 <0xb70f26c0>05   
09/23/11 16:01:59.131      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05
09/23/11 16:01:59.132      Creating child 72 <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 55 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 55 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.132      Creating child 36 <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>05   
09/23/11 16:01:59.132      Creating child 69 <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb70f26c0>05   
09/23/11 16:01:59.132      Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb70f26c0>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.134      ERROR! Out of frame flow!! <0xb68f0b90>01   
09/23/11 16:01:59.262      ZWave Version: 2.31 <0xb68f0b90>01   
09/23/11 16:01:59.371      Home id: 0x00092a4c, our node id: 1 <0xb68f0b90>01   
09/23/11 16:01:59.483      SerAppV:2,r67,Manf 0,Typ 1,Prod 1 <0xb68f0b90>05   
09/23/11 16:01:59.590      Got reply to GET_SUC_NODE_ID, node: 1 <0xb68f0b90>05   
09/23/11 16:02:00.646      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:02:02.171      Finished building node list: <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 2 basic: 0x1 generic: 0x1 specific: 0x1 pluto: 1945 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 3 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 4 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 5 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 6 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 7 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 8 basic: 0x4 generic: 0xa1 specific: 0x7 pluto: 55 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 11 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 12 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 13 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 14 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 15 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:02.171      Node: 16 basic: 0x4 generic: 0x8 specific: 0x4 pluto: 4 <0xb68f0b90>05   
09/23/11 16:02:32.187      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:04:39.366      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:06:28.654      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:07:11.987      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>05   
09/23/11 16:14:42.770      Error: ZW_SEND failed, removing job after three tries <0xb68f0b90>}

[bongowongo]

Hari wake up
Work to do

http://heating.danfoss.com/PCMPDF/Z_wave_commands_VDFNN202_teamcent.pdf

[hari]

I need a unit for testing..

[Jones]

Hi Hari,

I need a unit for testing..

Can you use my setup for testing? ssh or something?


/Jones

[hari]

ssh should work

[oernii]

Hi, please let us know if there is something ;-) I also desire a remote radiator valve solution. This seems perfect.

[hari]

Enable zwave debug logging, redo the test, send me the
Log and the exact timestamp of your test

[hari]

set temperature command now works, just tested with the unit. Be aware that it sleeps, so the new setpoint is not set until the unit wakes up. It also supports a schedule, but I did not yet test that.

[Domodude]

Waking up an old thread.... Set temp works, does the unit have a way of reading the temperature? And, is there a list somewhere of z-wave codes? Finally, does it work with Dianemo S (Andrew?)?

[totallymaxed]

Waking up an old thread.... Set temp works, does the unit have a way of reading the temperature? And, is there a list somewhere of z-wave codes? Finally, does it work with Dianemo S (Andrew?)?

Yes it does. We provided Hari with a Living Connect TRV to allow him to work directly with the hardware. I believe he is still planning to add some additional support for TRV profiles etc.

Andrew

[hari]

Waking up an old thread.... Set temp works, does the unit have a way of reading the temperature? And, is there a list somewhere of z-wave codes? Finally, does it work with Dianemo S (Andrew?)?

afaicr you can't read out temps, but I'd need to check to say for sure.

[Domodude]

afaicr you can't read out temps, but I'd need to check to say for sure.

It'd be awesome! Please do 
I have a bad feeling about this, though, considering they are marketing a separate temperature sensor....

[hari]

unfortunately it does not seem to support the multilevel sensor command class... so no temp readouts or reports, just the setpoint.

[youen]

I'm trying to get a danfoss unit (014G0002) to work too. I'm new to LinuxMCE and zwave in general. I don't understand how I'm supposed to setup it, but currently it doesn't work.

I'm using an Aeon Labs Z-Stick S2, and I have the Danfoss unit too, and of course a PC where LinuxMCE is installed. Is it sufficient to control the thermostat ? (the wizard girl talks about a "master controller", I'm getting lost at that point). I've tried to include the thermostat with the z-stick button (unplugged the stick, press the button, and then the button on the thermostat). However, the little antenna and bell are still blinking on the thermostat, looks like a bad sign.

And how am I supposed to set things up in LinuxMCE? I see two "standard thermostat" (though I included only one, but multiple times during various tests) in the web page, but any action done there has no result (even after waiting an hour or so). When I try to see the log (in "advanced" section of the thermostat), it says it can't find the file.

Anyone knows what I need to do ?
Thanks in advance,

Youen.

PS: before installing LinuxMCE, I tried with open zwave too, with no success either. People there said it's because the device goes to sleep too soon which prevents communication. Don't know much more :-(

[hari]

to include the unit without "dirty" ticks you need an inclusion controller in addition to a PC dongle and run SIS mode. You'll then use the inclusion controller (usually a hand held z-wave remote) to include the danfoss. The controller will notify the PC dongle about this and LinuxMCE is able to set up the proper configuration/association.

(the dirty trick would be to wake the unit up somehow, e.g by (tripple) pressing the buttons, and so on. I'd need to consult the manual for further instructions)