Danfoss Living Connect LC03 with Aeon Z-Stick Gen5

[LouiS22]

[L2v2P]

Hi Guys,

Ik have the same Z-Stick connected to a Danfoss Living Connect LC-13. Once I have the LC-13 paired it starts submitting messages to the Z-Stick/Controller at a rate of about once every second:

Code: Select all

2016-11-17 06:40:59.175  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:00.226  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:01.454  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:02.694  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:03.563  (P1) P1 Smart Meter (Elektriciteit)\
2016-11-17 06:41:03.924  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:05.164  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:06.394  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:07.634  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:08.864  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:10.094  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:11.334  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:12.567  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:13.663  (P1) P1 Smart Meter (Elektriciteit)\
2016-11-17 06:41:13.804  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:15.034  (Z-stick) Thermostat (Verwarming keuken - klein)\
2016-11-17 06:41:16.274  (Z-stick) Thermostat (Verwarming keuken - klein)\

After fifteen minutes or so the LC-13 freezes: it doesn't respond to any button presses, the screen remains off and it stops sending messages to the controller. If I take out the battery and put it back it starts working again, but only for approximately 15 minutes. A factory reset of both the LC-13 and Z-stick do not make it any better. I've seen the exact same behavior in Indigo by the way.

Any suggestions as to what might be the problem?

[L2v2P]

Also, when I enable debug logging I continuously get this:

Code: Select all

2016-11-17 20:09:44.617 Detail, Node002,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x80, 0x03, 0x3a, 0x4a
2016-11-17 20:09:44.617 Detail, 
2016-11-17 20:09:44.617 Info, Node002, Received Battery report from node 2: level=58
2016-11-17 20:09:44.617 Detail, Node002, Refreshed Value: old value=58, new value=58, type=byte
2016-11-17 20:09:44.617 Detail, Node002, Changes to this value are not verified
2016-11-17 20:09:44.617 Detail, Node002, Notification: ValueChanged
2016-11-17 20:09:44.638 Detail, Node002,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x02, 0x06, 0x43, 0x03, 0x01, 0x42, 0x08, 0x34, 0xcc
2016-11-17 20:09:44.638 Detail, 
2016-11-17 20:09:44.638 Detail, Node002, Refreshed Value: old value=21.00, new value=21.00, type=decimal
2016-11-17 20:09:44.638 Detail, Node002, Changes to this value are not verified
2016-11-17 20:09:44.638 Info, Node002, Received thermostat setpoint report: Setpoint Heating 1 = 21.00C
2016-11-17 20:09:44.638 Detail, Node002, Notification: ValueChanged
2016-11-17 20:09:44.639  (Controller) Thermostat (Heating 1)
2016-11-17 20:09:44.659 Detail, Node002,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 0x02, 0x04, 0x46, 0x08, 0x00, 0x7f, 0xc6
2016-11-17 20:09:44.659 Detail, 
2016-11-17 20:09:44.659 Info, Node002, Received climate control schedule override report:
2016-11-17 20:09:44.659 Info, Node002,   Override State: None:
2016-11-17 20:09:44.659 Detail, Node002, Refreshed Value: old value=0, new value=0, type=list
2016-11-17 20:09:44.659 Detail, Node002, Changes to this value are not verified
2016-11-17 20:09:44.659 Detail, Node002, Refreshed Value: old value=127, new value=127, type=byte
2016-11-17 20:09:44.659 Detail, Node002, Changes to this value are not verified
2016-11-17 20:09:44.659 Detail, Node002, Notification: ValueChanged
2016-11-17 20:09:44.659 Detail, Node002, Notification: ValueChanged
2016-11-17 20:09:44.679 Detail, Node002,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x02, 0x02, 0x84, 0x07, 0x70
2016-11-17 20:09:44.679 Detail, 
2016-11-17 20:09:44.679 Info, Node002, Received Wakeup Notification from node 2
2016-11-17 20:09:44.679 Info, Node002,   Node 2 has been marked as awake
2016-11-17 20:09:44.679 Detail, Node002, Queuing (WakeUp) WakeUpCmd_NoMoreInformation (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x84, 0x08, 0x25, 0xaa, 0xe6
2016-11-17 20:09:44.679 Detail, Node002, Notification: Notification - Node Awake
2016-11-17 20:09:44.679 Detail, 
2016-11-17 20:09:44.679 Info, Node002, Sending (WakeUp) message (Callback ID=0xaa, Expected Reply=0x13) - WakeUpCmd_NoMoreInformation (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x84, 0x08, 0x25, 0xaa, 0xe6
2016-11-17 20:09:44.687 Detail, Node002,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2016-11-17 20:09:44.687 Detail, Node002,   ZW_SEND_DATA delivered to Z-Wave stack
2016-11-17 20:09:44.705 Detail, Node002,   Received: 0x01, 0x07, 0x00, 0x13, 0xaa, 0x00, 0x00, 0x02, 0x43
2016-11-17 20:09:44.705 Detail, Node002,   ZW_SEND_DATA Request with callback ID 0xaa received (expected 0xaa)
2016-11-17 20:09:44.705 Info, Node002, Request RTT 26 Average Request RTT 26
2016-11-17 20:09:44.705 Info, Node002,   Node 2 has been marked as asleep
2016-11-17 20:09:44.705 Detail,   Expected callbackId was received
2016-11-17 20:09:44.705 Detail,   Expected reply was received
2016-11-17 20:09:44.705 Detail,   Message transaction complete
2016-11-17 20:09:44.705 Detail, 
2016-11-17 20:09:44.705 Detail, Node002, Removing current message
2016-11-17 20:09:44.705 Detail, Node002, Notification: Notification - Node Asleep
2016-11-17 20:09:45.720 Detail, Node002,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x02, 0x03, 0x80, 0x03, 0x3a, 0x4a
2016-11-17 20:09:45.721 Detail, 

It seems that the LC-13 continuously sends its settings (setpoint for example) to the controller for some odd reason. Is the LC-13 malfunctioning?

[antares]

Has there been any progress with regards of not being able to set temperature from Blockly scripts directly to the thermostat? Do we still have to use the URL calls?

[L2v2P]

It has been implemented in the current beta:

Code: Select all

Version 3.xxxx (December xth 2016)
[...]
- Implemented: Blockly/Lua Set SetPoint option
[...]

Source: https://github.com/domoticz/domoticz/bl ... istory.txt

[L2v2P]

It seems that the LC-13 continuously sends its settings (setpoint for example) to the controller for some odd reason. Is the LC-13 malfunctioning?

It turned out the unit was defective; I returned it and got a new one.

[antares]

It has been implemented in the current beta:

Code: Select all

Version 3.xxxx (December xth 2016)
[...]
- Implemented: Blockly/Lua Set SetPoint option
[...]

Source: https://github.com/domoticz/domoticz/bl ... istory.txt

Hmmm.... running current beta haven't seen that option, yet in Blockly. I'll have a look whether I can find it. Thanks for the hint!

[Olfer]

Try to look at it via MyDomoticz. I found it there, but not via my local Webview :/
If you use that feature in MyDomoticz, you wont be able to edit it on you local view... Unfortunately

[bickel]

Although this is an older thread..i have the same issue.
I already have 7 danfoss living connects working and i had 2 extra in stock which i want to use now to replace a defected one.
But the inclusion will not succeed for both.
Got the Aeotec Z-Stick S2.
Both devices had never been included, but i also tried to factory reset them without success.
Procedures i tried:
1-
Stop domoticz
Take z-stick to the mounted danfoss
danfoss is in normal operator mode
enable inclusion mode on stick
press shortly the inclusion button on danfoss.
Normally you would see a change of the blinking light but nothing.
If i try the exlusion mode the stick is responding so communication seems to work.

2-enabled 'allow new hardware' in a running domoticz and pressed the inclusion button.

Both methods seems to fail on both devices.

Any ideas how i can troubleshoot this?

Gr,
Ronald