search

audiovibe / openzwave-control-panel

Automatically exported from code.google.com/p/openzwave-control-panel
0 stars 0 forks source link

I want to define danfoss thermostat set point #16

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
I want to define danfoss thermostat set point
My request is :
wget --post-data='3-THERMOSTAT SETPOINT-user-decimal-1-2=15' 
http://192.168.1.19:1234/valuepost.html
Nothinks apear.

Have you try to use with this module ?
Thanks
Thomas

Original issue reported on code.google.com by thomas.g...@gmail.com on 18 Feb 2013 at 10:24

GoogleCodeExporter commented 8 years ago 
I got a response from the control panel. Seems to work fine. I have included 
the output:

b3cfcb40: POST: "/valuepost.html" conn=b6900738 size=0 *ptr=0
b3cfcb40: POST: "/valuepost.html" conn=b6900738 size=41 *ptr=b5f00480
post: key=5-THERMOSTAT SETPOINT-user-decimal-1-1 data=65 size=2
2013-02-19 00:37:19:263 Node005, Queuing command: Set Thermostat Setpoint 
(Node=5): 0x01, 0x0c, 0x00, 0x13, 0x05, 0x05, 0x43, 0x01, 0x01, 0x09, 0x41, 
0x25, 0x0e, 0xc0
2013-02-19 00:37:19:264 Node005, Queuing command: Request Current Thermostat 
Setpoint (Node=5): 0x01, 0x0a, 0x00, 0x13, 0x05, 0x03, 0x43, 0x02, 0x01, 0x25, 
0x0f, 0x8a
b3cfcb40: POST: "/valuepost.html" conn=b6900738 size=0 *ptr=b5f00480
2013-02-19 00:37:19:264 
2013-02-19 00:37:19:265 Node005, Sending command (Callback ID=0x0e, Expected 
Reply=0x13) - Set Thermostat Setpoint (Node=5): 0x01, 0x0c, 0x00, 0x13, 0x05, 
0x05, 0x43, 0x01, 0x01, 0x09, 0x41, 0x25, 0x0e, 0xc0
2013-02-19 00:37:19:269 Node005,   ACK received CallbackId 0x0e Reply 0x13
2013-02-19 00:37:19:280 Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2013-02-19 00:37:19:280 Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2013-02-19 00:37:19:659 Node005,   Received: 0x01, 0x05, 0x00, 0x13, 0x0e, 
0x01, 0xe6
2013-02-19 00:37:19:660 Node005,   ZW_SEND_DATA Request with callback ID 0x0e 
received (expected 0x0e)
2013-02-19 00:37:19:661 Node005, ERROR: ZW_SEND_DATA failed. No ACK received - 
device may be asleep.
2013-02-19 00:37:19:661 Node005,   WARNING: Device is not a sleeping node.
2013-02-19 00:37:19:663 
2013-02-19 00:37:19:663 Node005, Sending command (Callback ID=0x0f, Expected 
Reply=0x04) - Request Current Thermostat Setpoint (Node=5): 0x01, 0x0a, 0x00, 
0x13, 0x05, 0x03, 0x43, 0x02, 0x01, 0x25, 0x0f, 0x8a
2013-02-19 00:37:19:668 Node005,   ACK received CallbackId 0x0f Reply 0x04
2013-02-19 00:37:19:678 Node005,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2013-02-19 00:37:19:679 Node005,   ZW_SEND_DATA delivered to Z-Wave stack
2013-02-19 00:37:20:020 Node005,   Received: 0x01, 0x05, 0x00, 0x13, 0x0f, 
0x01, 0xe7
2013-02-19 00:37:20:021 Node005,   ZW_SEND_DATA Request with callback ID 0x0f 
received (expected 0x0f)
2013-02-19 00:37:20:021 Node005, ERROR: ZW_SEND_DATA failed. No ACK received - 
device may be asleep.
2013-02-19 00:37:20:022 Node005,   WARNING: Device is not a sleeping node.

If this doesn't work for you I will see to see more output from the control 
panel.

Original comment by glsatz on 19 Feb 2013 at 8:43

GoogleCodeExporter commented 8 years ago 
For me :

b3b56b70: POST: "/valuepost.html" conn=996ee58 size=0 *ptr=0
b3b56b70: POST: "/valuepost.html" conn=996ee58 size=41 *ptr=995f508
post: key=3-THERMOSTAT SETPOINT-user-decimal-1-2 data=15 size=2
2013-02-19 09:51:05:338 
2013-02-19 09:51:05:402 Node003, Queuing Wake-Up Command: Set Thermostat 
Setpoint (Node=3): 0x01, 0x0c, 0x00, 0x13, 0x03, 0x05, 0x43, 0x01, 0x02, 0x01, 
0x0f, 0x25, 0x14, 0x99
2013-02-19 09:51:05:408 
2013-02-19 09:51:05:427 Node003, Queuing Wake-Up Command: Request Current 
Thermostat Setpoint (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x43, 0x02, 
0x02, 0x25, 0x15, 0x95
b3b56b70: POST: "/valuepost.html" conn=996ee58 size=0 *ptr=995f508
2013-02-19 09:51:06:147 Node002, Polling: COMMAND_CLASS_SWITCH_BINARY index = 0 
instance = 1 (poll queue has 0 messages)
....

Original comment by thomas.g...@gmail.com on 19 Feb 2013 at 8:50

GoogleCodeExporter commented 8 years ago 
If I recall correctly Danfoss thermostats sleep so the commands will sit in the 
wake up queue pending the device waking up to receive the update. It is working 
like it is supposed to. You can change the wake up interval using the control 
panel to something shorter at the expense of battery longevity.

Original comment by glsatz on 19 Feb 2013 at 8:58

GoogleCodeExporter commented 8 years ago 
There is a change of node id from 003 to 002.
I don't know if this is the problème.
If you want I can send to you acces on Private message.

Thanks
Thomas

Original comment by thomas.g...@gmail.com on 19 Feb 2013 at 9:05

GoogleCodeExporter commented 8 years ago 
If I filter message about Node003. When I send command :
2013-02-19 10:15:17:730 Node003, Queuing Wake-Up Command: Set Thermostat 
Setpoint (Node=3): 0x01, 0x0c, 0x00, 0x13, 0x03, 0x05, 0x43, 0x01, 0x02, 0x01, 
0x0f, 0x25, 0x1c, 0x91
2013-02-19 10:15:17:779 Node003, Queuing Wake-Up Command: Request Current 
Thermostat Setpoint (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x43, 0x02, 
0x02, 0x25, 0x1d, 0x9d

When the thermostat weak-up :
2013-02-19 10:14:08:864 Node003,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 
0x03, 0x03, 0x80, 0x03, 0xff, 0x8e
2013-02-19 10:14:08:871 Node003, Received Battery report from node 3: level=0
2013-02-19 10:14:08:874 Node003, Initial read of value
2013-02-19 10:14:08:894 Node003,   Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 
0x03, 0x06, 0x43, 0x03, 0x01, 0x42, 0x08, 0x34, 0xcd
2013-02-19 10:14:08:941 Node003,   Received: 0x01, 0x0a, 0x00, 0x04, 0x00, 
0x03, 0x04, 0x46, 0x08, 0x00, 0x00, 0xb8
2013-02-19 10:14:08:949 Node003, Received climate control schedule override 
report:
2013-02-19 10:14:08:952 Node003,   Override State: None:
2013-02-19 10:14:08:966 Node003, Initial read of value
2013-02-19 10:14:08:970 Node003, Initial read of value
2013-02-19 10:14:09:022 Node003,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 
0x03, 0x02, 0x84, 0x07, 0x71
2013-02-19 10:14:09:053 Node003, Received Wakeup Notification from node 3
2013-02-19 10:14:09:085 Node003,   Node 3 has been marked as awake
2013-02-19 10:14:09:090 Node003, Queuing command: 
ClimateControlScheduleCmd_ChangedGet (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 
0x02, 0x46, 0x04, 0x25, 0x07, 0x84
2013-02-19 10:14:09:096 Node003, Queuing command: ProtectionCmd_Get (Node=3): 
0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x75, 0x02, 0x25, 0x08, 0xbe
2013-02-19 10:14:09:131 Node003, Queuing command: WakeUpCmd_IntervalGet 
(Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x84, 0x05, 0x25, 0x09, 0x49
2013-02-19 10:14:09:163 Node003, Queuing command: 
WakeUpCmd_IntervalCapabilityGet (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 
0x84, 0x09, 0x25, 0x0a, 0x46
2013-02-19 10:14:09:167 Node003, Queuing Command: Query Stage Complete (Session)
2013-02-19 10:14:09:172 Node003, Queuing command: Set Thermostat Setpoint 
(Node=3): 0x01, 0x0c, 0x00, 0x13, 0x03, 0x05, 0x43, 0x01, 0x02, 0x01, 0x0f, 
0x25, 0x19, 0x94
2013-02-19 10:14:09:198 Node003, Queuing command: Request Current Thermostat 
Setpoint (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x43, 0x02, 0x02, 0x25, 
0x1a, 0x9a
Can you explain me the hexa information in the last line ?

Thanks
Thomas

Original comment by thomas.g...@gmail.com on 19 Feb 2013 at 9:14

GoogleCodeExporter commented 8 years ago 
I don't see anything wrong with the request thermostat setpoint data. It has 
node 3 referenced. There is no issue here I can see. This issue report has been 
closed. Also what you are asking about is regarding the OpenZWave library and 
not the control panel so please move the conversation to OpenZWave 
<openzwave@googlegroups.com>. Only providing snippets makes it harder to see 
what is going on. Also others on that list have experience with this device and 
may be able to help.

Original comment by glsatz on 19 Feb 2013 at 4:10