Danfoss living connect implementation error?

Discussions about existing Z-Wave device and their usage with Z-Way/Z-Cloud/Z-Box
pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Thank you for the reply.

Post by pz1 » 16 Feb 2012 11:40

Thank you for the reply.
Does this mean that if I have assigned a climate schedule to a zone, and the device (Danfoss Living Connect) in that zone reports under tab "Device Control" "Automatically controlled", this week schedule has been stored in the Danfoss, and it operates autonomically from then on?
Since 29-12-2016 I am no longer a moderator for this forum

User avatar
PoltoS
Posts: 4098
Joined: 26 Jan 2011 19:36

Exactly!

Post by PoltoS » 16 Feb 2012 11:40

Just make sure to apply the climate schedule on a zone (you can have many climate scheduled defined.

pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Does not work for me so far

Post by pz1 » 16 Feb 2012 11:40

Re-reading the specifications an another thread on this site, it should be connected 24/7 to a controller. If not the battery drains to fast I understand.
Apart from that I can't get this to work. I see in the queue list that the climate schedule is sent at every time the DLC is awake. The wakeup period seems to last almost a minute every time. That should not be the case I think if there are no changes in temperature settings, the DLC should be sent back to sleep immediately.
What info do you need to determine where the cause of my problem is?
Since 29-12-2016 I am no longer a moderator for this forum

pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Many error/warning messages in DLC log

Post by pz1 » 16 Feb 2012 11:40

I have run some stability tests over the past month or so with a setup where the controller (z-agent) runs on a Synology DS212+, with the DLC and Duwi plugin switch as nodes. Last week I extended the network with a couple of zwave.me binary wall switches, which are intended as the permanent on mesh network to support the DLC's. In my log below the DLC is device nr 4, the other device numbers are the binary switches.
Where in earlier experiments as was alarmed by the rapid drain of battery power, now I am becoming more and more worried about a battery level that stays on 66% for over a month now.
In my experiment I raised the temperature schedule with 1 degree. The queue says:
n W S D Ack Resp Cbk Timeout NodeId Description Progress Buffer
0 W - - - 3.30 4 Send to device 4, instance 0, Thermostat setpoint set: mode 1, value 19.000000 1 d 0 13 4 6 43 1 1 42 7 6c 5 fb 77
0 W - - - 3.30 4 Send to device 4, instance 0, Thermostat setpoint get 1 a 0 13 4 3 43 2 1 5 fc 58
Queue length: 2

The log before and after the command is
2012-07-16 10:33:02,256 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:33:02,192 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:33:02,110 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:33:02,078 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:33:01,922 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:33:01,911 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:33:01,910 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:33:01,721 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:33:01,679 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:33:01,676 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:33:01,561 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:33:01,560 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:33:01,392 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:33:01,295 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:33:01,292 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:33:01,173 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:33:01,172 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:32:48,444 Z-Wave.INFO Send to device 4, instance 0, wakeup no more information: Dropping command: too much resends
2012-07-16 10:32:48,443 Z-Wave.INFO Send to device 4, instance 0, wakeup no more information: Not delivered to recipient due to no ACK from destination
2012-07-16 10:32:48,354 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:32:48,146 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:32:48,094 Z-Wave.INFO Send to device 4, instance 0, Multi Command with 4 encapsulated commands: Send to device 4, instance 0, Thermostat setpoint set: mode 1, value 19.000000, Send to device 4, instance 0, Thermostat setpoint get, Send to device 4, instance 0, clock report, Send to device 4, instance 0, Schedule Change Report: Callback received - transfered to encapsulated jobs
2012-07-16 10:32:48,094 Z-Wave.INFO Send to device 4, instance 0, Schedule Change Report: Delivered
2012-07-16 10:32:48,094 Z-Wave.INFO Send to device 4, instance 0, clock report: Delivered
2012-07-16 10:32:48,093 Z-Wave.INFO Send to device 4, instance 0, Thermostat setpoint get: Delivered
2012-07-16 10:32:48,093 Z-Wave.INFO Send to device 4, instance 0, Thermostat setpoint set: mode 1, value 19.000000: Delivered
2012-07-16 10:32:48,040 Z-Wave.INFO Send to device 4, instance 0, Multi Command with 4 encapsulated commands: Send to device 4, instance 0, Thermostat setpoint set: mode 1, value 19.000000, Send to device 4, instance 0, Thermostat setpoint get, Send to device 4, instance 0, clock report, Send to device 4, instance 0, Schedule Change Report: Response received - transfered to encapsulated jobs
2012-07-16 10:32:47,935 CmdCls.INFO Node 4:0, CC Wakeup: send node into sleep
2012-07-16 10:32:47,924 CmdCls.INFO Node 4:0, CC Wakeup: send node into sleep
2012-07-16 10:32:47,923 Z-Wave.INFO Running wakeup handler for node 4
2012-07-16 10:32:47,923 CmdCls.INFO Node 4:0, CC Wakeup: Wakeup notification
2012-07-16 10:32:47,922 CmdCls.INFO Node 4:0, CC ClimateControlSchedule: Sending Schedule changed report 78
2012-07-16 10:32:47,922 CmdCls.INFO Node 4:0, CC ClimateControlSchedule: Received Changed Get (( 46 04 ))
2012-07-16 10:32:47,921 CmdCls.INFO Node 4:0, CC ClimateControlSchedule: Received Override Report 127 (( 46 08 00 7F ))
2012-07-16 10:32:47,919 Rules.INFO Event: from 4:0 to 1:0, Report, value: [128, 66]
2012-07-16 10:32:02,260 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:32:02,207 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:32:02,129 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:32:02,086 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:32:01,928 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:32:01,918 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:32:01,916 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:32:01,720 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:32:01,678 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:32:01,676 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:32:01,550 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:32:01,549 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:32:01,365 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:32:01,282 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:32:01,280 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:32:01,164 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:32:01,162 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:31:02,202 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:31:02,140 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:31:02,068 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:31:02,036 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:31:01,877 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:31:01,876 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:31:01,710 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:31:01,658 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:31:01,657 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:31:01,605 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:31:01,593 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:31:01,527 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:31:01,525 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:31:01,298 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:31:01,296 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:31:01,169 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:31:01,168 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:30:02,440 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:30:02,333 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:30:02,272 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:30:02,083 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:30:02,082 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:30:01,809 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:30:01,773 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:30:01,753 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:30:01,627 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:30:01,625 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:30:01,550 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:30:01,539 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:30:01,255 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:30:01,253 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:29:02,190 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:29:02,111 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:29:02,028 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:29:01,994 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:29:01,873 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:29:01,831 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:29:01,830 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:29:01,641 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:29:01,599 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:29:01,592 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:29:01,487 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:29:01,476 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:29:01,474 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:29:01,239 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:29:01,237 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:29:01,125 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:29:01,123 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:28:02,206 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:28:02,120 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:28:02,046 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:28:02,003 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:28:01,865 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:28:01,854 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:28:01,852 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:28:01,618 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:28:01,608 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:28:01,606 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:28:01,504 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:28:01,493 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:28:01,491 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:28:01,250 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:28:01,245 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:28:01,127 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:28:01,125 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:02,602 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:27:02,519 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:27:02,436 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:27:02,404 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:27:02,284 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:27:02,242 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:27:02,240 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:02,007 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:27:01,997 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:27:01,994 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:01,889 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:27:01,878 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:27:01,876 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:01,651 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:27:01,649 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:01,524 Z-Wave.ERROR SendData callback Id is invalid: 0xec! Probably too late
2012-07-16 10:27:01,524 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:01,472 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:27:01,462 Z-Wave.WARNING A response received with no request!
2012-07-16 10:27:01,450 Z-Wave.WARNING ACK received, but no job waiting for ACK
2012-07-16 10:27:01,309 Rules.INFO Event: from 5:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:27:01,308 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:27:01,194 Z-Wave.INFO Send to device 5, instance 0, switch binary get: Delivered
2012-07-16 10:27:01,190 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:26:02,206 Rules.INFO Event: from 8:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:26:02,127 Z-Wave.INFO Send to device 8, instance 0, switch binary get: Delivered
2012-07-16 10:26:02,044 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:26:02,012 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:26:01,851 Z-Wave.INFO Send to device 7, instance 0, switch multilevel get: Delivered
2012-07-16 10:26:01,851 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:26:01,766 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:26:01,665 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:26:01,623 Rules.INFO Event: from 7:0 to 1:0, Report, value: [37, 0]
2012-07-16 10:26:01,621 Z-Wave.WARNING SOF found while awaiting ack...
2012-07-16 10:26:01,547 Z-Wave.WARNING CAN found while no job awaiting ACK...
2012-07-16 10:26:01,506 Z-Wave.INFO Send to device 7, instance 0, switch binary get: Delivered
2012-07-16 10:26:01,504 Z-Wave.WARNING SOF found while awaiting ack...

What is going wrong here? I did reinclude the device a month ago. In the device description record it is said that the interview is complete.
Since 29-12-2016 I am no longer a moderator for this forum

User avatar
PoltoS
Posts: 4098
Joined: 26 Jan 2011 19:36

The log do not contain

Post by PoltoS » 16 Feb 2012 11:40

The log do not contain anything dramatic. Just a typical log with a lot of small timing warnings due to internet delays. We don't see any realy problem here.

What is your problem? Battery level drop? Or you see some other problem?

We had a huge experience with DLC and it was not 100% positive. Unfortunatelly we do not understand well how the device work in critical situations (like no controller found or communication error). Danfoss told us that DLC will panic, but we are not sure what "panic" means. We do not know how fast does it recover after this "panic" state.

pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Well with a battery life

Post by pz1 » 16 Feb 2012 11:40

Well with a battery life expectancy of 2 years, I would expect that the battery level would have dropped at least 1% in the last 4 weeks. It did not, it remained on 66%. If that is fine OK. All the warnings in the log make me nervous. I do test ping z-cloud.z-wave.me on a regular basis. The average varies here from 38 to 44 ms. I remember you mentioned this was too slow. I do not think I can do anything about it unfortunately.
Since 29-12-2016 I am no longer a moderator for this forum

TooDizzy
Posts: 1
Joined: 27 Sep 2012 19:16

What about the new firmaware?

Post by TooDizzy » 16 Feb 2012 11:40

I just learned that the newest thermostats (from August) have removed the standard Z-Wave protocal and they are thereby no longer have the Z-Wave sticker/batch.
What does this actually mean? How compatible are these?

User avatar
PoltoS
Posts: 4098
Joined: 26 Jan 2011 19:36

They should not be compatible at all

Post by PoltoS » 16 Feb 2012 11:40

We have heard that Danfoss finaly decided to make two different products: Z-Wave and Danfoss Connect. We believe it's a good decision, but we do not know when will the Z-Wave version come up.

pz1
Posts: 2053
Joined: 08 Apr 2012 13:44

Have you heard anything about

Post by pz1 » 16 Feb 2012 11:40

Have you heard anything about the distinction between the two versions, that you are allowed to share with us?
Since 29-12-2016 I am no longer a moderator for this forum

User avatar
PoltoS
Posts: 4098
Joined: 26 Jan 2011 19:36

Not yet

Post by PoltoS » 16 Feb 2012 11:40

We have only heard about it. It's quite hard to keep in touch with all manufacturers, since they not always want to share their plans with us.

Post Reply