ZIP gateway does not response to broadcasting messages


#1

I have noticed an strange behaviour from ZIP gateway, the broadcasting messages (from the node to node id 255, application Node Info) does not activate device wake up, although the device is up and can consume messages from the mail box zip gateway wont send any messages to the device. the device is a danfoss certified radiator thermostat. and the device does not pick up master node from set wakeup interval call to send the message to a particular node on wake up rather than broadcasting as well.


#2

For battery devices that support the Wake Up Command Class a controller cannot trust that a device is awake based on a Node Information Frame. Only when a Wake Up Notification frame is received you can conclude that the device is awake. Actually the specification for the Wake Up command state that all “other” communication to a controller must be send before the Wake Up Notification is send. This allows the battery device to wake up for a very short period and only send out data and go right back to sleep in order to save power. On the other hand when the Wake Up Notification is send the battery device must stay awake for 10 seconds - or until it gets the Wake Up No More Information
With this rule in mind it would be a problem to assume that a device is awake when receiving a Node Information Frame - trying to send to a “sleeping” device can cause lots of unnecessary traffic in the network, because the Z-Wave protocol will try to deliver the message using all routing options


#3

Agree with Laus. The gateway should only expect the device to be awake when receiving a Wakeup Notification Cmd. The Wakeup Notification Cmd may be send through broadcast and the gateway should accept this. Only the gateway must not send the Wakeup No More Information when receiving the Wakeup Notification through broadcast.

The gateway must configure wakeup interval doing inclusion - is this not done?


#4

thanks for the reply, the device I am working with is z-wave certified so I believe it has passed the tests. it’s quite strange that there is a flaw like that in the device. as you mentioned correctly the device is not sending any wake up notification while pressing wake up button. here is the trace from z-sniffer:

1	18.09.2017	09:54:07.921	9.6Kbit/s	65	1	0	035	255	DC 9C 8C 92	Broadcast	Node Info	DC 9C 8C 92 23 01 01 1F FF 01 01 53 9C 00 08 04 80 46 81 72 8F 75 31 43 86 84 EF 46 81 8F B9

also I have a Danfoss room sensor which works pretty well with the wake up button and here is the trace from that device:

2	18.09.2017	09:54:13.969	40Kbit/s	73	1	6073	033	001	DC 9C 8C 92	Singlecast	Central Scene Notification	DC 9C 8C 92 21 41 01 0F 01 5B 03 03 00 01 94
3	18.09.2017	09:54:13.978	40Kbit/s	78	1	11	001	033	DC 9C 8C 92	Ack		DC 9C 8C 92 01 03 01 0A 21 89
4	18.09.2017	09:54:14.016	9.6Kbit/s	69	1	16	033	255	DC 9C 8C 92	Broadcast	Node Info	DC 9C 8C 92 21 01 01 1E FF 01 01 53 9C 00 21 01 20 72 86 80 8F 84 75 70 31 5B 43 53 87 29
5	18.09.2017	09:54:14.037	40Kbit/s	66	1	27	033	001	DC 9C 8C 92	Singlecast	Multi Cmd Encap	DC 9C 8C 92 21 41 02 1B 01 8F 01 03 03 80 03 61 06 31 05 01 42 08 77 02 84 07 3A
6	18.09.2017	09:54:14.037	40Kbit/s	78	1	13	001	033	DC 9C 8C 92	Ack		DC 9C 8C 92 01 03 02 0A 21 8A
7	18.09.2017	09:54:14.704	40Kbit/s	78	1	670	018	033	DC 9C 8C 92	Singlecast	Wake Up Interval Get	DC 9C 8C 92 12 41 03 0C 21 84 05 5D
8	18.09.2017	09:54:14.710	40Kbit/s	70	1	7	033	018	DC 9C 8C 92	Ack		DC 9C 8C 92 21 03 03 0A 12 98
9	18.09.2017	09:54:14.730	40Kbit/s	72	1	13	033	018	DC 9C 8C 92	Singlecast	Wake Up Interval Report	DC 9C 8C 92 21 41 03 10 12 84 06 00 01 2C 01 6E
10	18.09.2017	09:54:14.734	40Kbit/s	78	1	10	018	033	DC 9C 8C 92	Ack		DC 9C 8C 92 12 03 03 0A 21 98
11	18.09.2017	09:54:15.072	40Kbit/s	78	1	325	019	033	DC 9C 8C 92	Singlecast	Multilevel Sensor Get Supported Scale	DC 9C 8C 92 13 41 04 0D 21 31 03 01 E8
12	18.09.2017	09:54:15.072	40Kbit/s	70	1	7	033	019	DC 9C 8C 92	Ack		DC 9C 8C 92 21 03 04 0A 13 9E
13	18.09.2017	09:54:15.079	40Kbit/s	70	1	12	033	019	DC 9C 8C 92	Singlecast	Multilevel Sensor Supported Scale Report	DC 9C 8C 92 21 41 04 0E 13 31 06 01 00 EE
14	18.09.2017	09:54:15.088	40Kbit/s	78	1	10	019	033	DC 9C 8C 92	Ack		DC 9C 8C 92 13 03 04 0A 21 9E
15	18.09.2017	09:54:15.448	40Kbit/s	78	1	359	020	033	DC 9C 8C 92	Singlecast	Thermostat Setpoint Get	DC 9C 8C 92 14 41 05 0D 21 43 02 01 9D
16	18.09.2017	09:54:15.454	40Kbit/s	69	1	7	033	020	DC 9C 8C 92	Ack		DC 9C 8C 92 21 03 05 0A 14 98
17	18.09.2017	09:54:15.469	40Kbit/s	71	1	14	033	020	DC 9C 8C 92	Singlecast	Thermostat Setpoint Report	DC 9C 8C 92 21 41 05 10 14 43 03 01 22 00 7D DE
18	18.09.2017	09:54:15.479	40Kbit/s	78	1	11	020	033	DC 9C 8C 92	Ack		DC 9C 8C 92 14 03 05 0A 21 98
19	18.09.2017	09:54:15.753	40Kbit/s	81	1	274	021	033	DC 9C 8C 92	Singlecast	Thermostat Setpoint Get	DC 9C 8C 92 15 41 06 0D 21 43 02 02 9C
20	18.09.2017	09:54:15.760	40Kbit/s	70	1	7	033	021	DC 9C 8C 92	Ack		DC 9C 8C 92 21 03 06 0A 15 9A
21	18.09.2017	09:54:15.776	40Kbit/s	71	1	14	033	021	DC 9C 8C 92	Singlecast	Thermostat Setpoint Report	DC 9C 8C 92 21 41 06 10 15 43 03 02 22 00 D2 70
22	18.09.2017	09:54:15.785	40Kbit/s	78	1	11	021	033	DC 9C 8C 92	Ack		DC 9C 8C 92 15 03 06 0A 21 9A
23	18.09.2017	09:54:16.069	40Kbit/s	74	1	284	018	033	DC 9C 8C 92	Singlecast	Thermostat Setpoint Get	DC 9C 8C 92 12 41 07 0D 21 43 02 0A 92
24	18.09.2017	09:54:16.075	40Kbit/s	70	1	6	033	018	DC 9C 8C 92	Ack		DC 9C 8C 92 21 03 07 0A 12 9C
25	18.09.2017	09:54:16.090	40Kbit/s	70	1	14	033	018	DC 9C 8C 92	Singlecast	Thermostat Setpoint Report	DC 9C 8C 92 21 41 07 10 12 43 03 0A 22 00 D2 7E
26	18.09.2017	09:54:16.107	40Kbit/s	78	1	11	018	033	DC 9C 8C 92	Ack		DC 9C 8C 92 12 03 07 0A 21 9C
27	18.09.2017	09:54:16.401	40Kbit/s	81	1	301	019	033	DC 9C 8C 92	Singlecast	Thermostat Setpoint Capabilities Get	DC 9C 8C 92 13 41 08 0D 21 43 09 01 9C
28	18.09.2017	09:54:16.408	40Kbit/s	70	1	7	033	019	DC 9C 8C 92	Ack		DC 9C 8C 92 21 03 08 0A 13 92

so it is obvious that there should be a wake up notification from the device. will contact the manufacturer about this issue.


#5

Hi Ali,

if you have the Zniffer tool from Sigma Designs I expect you also have a DevKit? In this case I suggest you send the question directly to Sigma Designs. They can help examine the Zniffer log and identify the problem.