Z-Wave issues - Numerous Power Cycles, Sluggish, Lost Devices

Developer Programs
1

My system is seeing extreme sluggish behavior often accompanied by numerous device time out/Z-Wave power cycle events. They occur randomly, but cluster around times when multiple devices are being controlled. In the hub event log devices will show as timing out, however they will respond quickly following the reboot and work fine when controlled the next time.

Z-Wave association mode isn’t reliably working either. I have to reboot the hub after each device is added in order to be able to add another one.

This is just from turning on a hall light and unlocking the front door. Both devices work fine when controlled on their own.

2017-10-15 9:17:01.562 AM EDT
10 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-15 9:16:57.995 AM EDT
10 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-15 9:16:57.992 AM EDT
10 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Lights in Front Hall [20])
2017-10-15 9:16:41.518 AM EDT
10 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-15 9:16:37.995 AM EDT
10 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Lights in Front Hall [20])
2017-10-15 9:16:37.970 AM EDT
10 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-15 9:15:42.066 AM EDT
11 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-15 9:15:40.740 AM EDT
11 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Front Door Lock [CD])
2017-10-15 9:15:40.736 AM EDT
11 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-15 9:15:40.326 AM EDT
11 minutes ago	HUB		index:17, mac:000420F3C826, ip:C0A80716, port:201E, requestId:f44ce6e9-dcd4-4005-8941-a535ac72ec63,	index:17, mac:000420F3C826, i...		index:17, mac:000420F3C826, ip:C0A80716, port:201E, requestId:f44ce6e9-dcd4-4005-8941-a535ac72ec63, headers:SFRUUC8xLjEgMjAwIE...
2017-10-15 9:14:54.103 AM EDT
12 minutes ago	HUB		index:17, mac:000420F3C826, ip:C0A80716, port:201E, requestId:08650234-6420-40c5-b245-9f3f07970acd,	index:17, mac:000420F3C826, i...		index:17, mac:000420F3C826, ip:C0A80716, port:201E, requestId:08650234-6420-40c5-b245-9f3f07970acd, headers:SFRUUC8xLjEgMjAwIE...
2017-10-15 9:14:30.107 AM EDT
12 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-15 9:14:27.797 AM EDT
12 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Front Door Lock [CD])
2017-10-15 9:14:27.798 AM EDT
12 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started

As I was posting this, I refreshed the log and saw another power cycle. Nobody was accessing or controlling the lock. When I tried to manually control it just now it unlocked fine.

2017-10-15 9:27:38.110 AM EDT
moments ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-15 9:27:35.938 AM EDT
moments ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Side Door Lock [CE])
2017-10-15 9:27:35.937 AM EDT
moments ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2
2

Contact ST support, it may be possible you have a defective chip, rare but it happens. Are you on the BETA firmware?

3

Hi Steve,

I am sorry you are experiencing issues. I am going to look at hub logs, and be in touch with you. I am seeing some network repair failures currently happening, but would like to know what has led to power cycle issues (we power cycle the Z-Wave chip if the Z-Wave chip becomes unresponsive to commands).

Thanks for your patience,
Kianoosh

4

After looking at the hub logs (only a limited amount of logs available and for a given period), it seems about 7 Hours ago, a network repair was initiated, and it was just finished. When network repair is in progress, it restricts lots of functionality such as sending packets to the nodes on the network.

I suggest re-cycling your hub (thus causing a reset on the z-wave chip) and reporting if similar issues occur.

I will be watching your hub closely for any sign of issues in the meantime.

5

Now that the repair has finished I am still seeing numerous Z-wave power resets, often without any device co troll activity occurring. Would you like me to reboot the hub now or will that wipe any logs?

6

Let me pull the logs before you do any reset.

As of right now, I am not sure if resetting the chip through a power cycle will help with this issue you are experiencing.

Hopefully once i get to the office tomorrow, I can try to reproduce this issue and find a work around. I am not too worried about the resets if the chip is hung up, the only thing i’d like to avoid is having to drop messages as a result of reset.

7

Just looked through the available hub logs in the past 30 minutes (did you do a power reset 30 minutes ago?) and all looked good. I will keep an eye out.

8

Yes I had to do a power cycle, sorry. Z-wave was acting up really badly.

9

My hub is logging 4-5 Z-wave power cycle events per hour on average. I haven’t even been home in over 24 hours no nobody is there to tinker with anything.

2017-10-17 4:00:11.430 PM EDT
5 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-17 4:00:11.428 PM EDT
5 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Front Door Lock [CD])
2017-10-17 3:59:39.359 PM EDT
5 hours ago	HUB		zw device: 63, command: 3202, payload: 21 74 00 09 BB D2 00 00 00 00 00 00	zw device: 63, command: 3202,...		zw device: 63, command: 3202, payload: 21 74 00 09 BB D2 00 00 00 00 00 00
2017-10-17 3:59:37.729 PM EDT
5 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-17 3:59:35.586 PM EDT
5 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Front Door Lock [CD])
2017-10-17 3:59:35.584 PM EDT
5 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-17 3:55:42.998 PM EDT
5 hours ago	HUB		ping	ping		ping
2017-10-17 3:51:05.550 PM EDT
5 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-17 3:51:03.380 PM EDT
5 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-17 3:51:03.380 PM EDT
5 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Halloween Lights on Porch [E8])
2017-10-17 3:50:57.421 PM EDT
5 hours ago	HUB		zw device: 69, command: 3202, payload: 01 76 00 05 AF 63 00 00 00 00 00 00	zw device: 69, command: 3202,...		zw device: 69, command: 3202, payload: 01 76 00 05 AF 63 00 00 00 00 00 00
2017-10-17 3:50:57.364 PM EDT
5 hours ago	HUB		zw device: 69, command: 3202, payload: 21 74 00 05 AF 63 00 00 00 00 00 00	zw device: 69, command: 3202,...		zw device: 69, command: 3202, payload: 21 74 00 05 AF 63 00 00 00 00 00 00
2017-10-17 3:50:41.051 PM EDT
5 hours ago	HUB		ping	ping		ping
2017-10-17 3:48:35.573 PM EDT
5 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-17 3:48:33.290 PM EDT
5 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (1st. Floor Stair Door Lock [CC])
2017-10-17 3:48:33.281 PM EDT
5 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
10

I found what is causing this issue, we fixed an issue in 18.22, but that fix exposes an issue that is documented by the Z-Wave Firmware (rarely ran into it because of another issue, interesting how that works, right?). Should have a fix for that pretty much soon, and we will keep you updated when the fix will go out

1 Like
11

Same issue here. Also reported this on the Beta program as you know.
Hope you’ll release this fix soon :upside_down_face:

12

Related?

@nastevens communicated with me some on that back in early September but I never saw a final resolution.

13

No, it appears that was the whole hub resetting, in this thread, we are experiencing Z-Wave functionality resets.

1 Like
14

Thank you for digging into this. I’m happy to advance test any potential fix. The hub is going through some very bad fits right now.

2017-10-18 7:51:34.515 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-18 7:51:32.237 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Front Door Lock [CD])
2017-10-18 7:51:32.231 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:50:53.943 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-18 7:50:49.903 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:50:49.878 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Front Door Lock [CD])
2017-10-18 7:50:18.441 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-18 7:50:16.016 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Lamp on Office Table [D3])
2017-10-18 7:50:16.016 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:50:01.834 PM EDT
3 hours ago	HUB		ping	ping		ping
2017-10-18 7:49:36.240 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:49:36.240 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Christmas Lights on Hutch [BE])
2017-10-18 7:48:48.360 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-18 7:48:46.638 PM EDT
3 hours ago	HUB		index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:15c5d97d-870c-4e16-b236-4fa6ef9bbaf9,	index:15, mac:000420F3C826, i...		index:15, mac:000420F3C826, ip:C0A80716, port:201E, requestId:15c5d97d-870c-4e16-b236-4fa6ef9bbaf9, headers:SFRUUC8xLjEgMjAwIE...
2017-10-18 7:48:46.581 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Lamp on Steve's Desk [D8])
2017-10-18 7:48:46.440 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:48:02.402 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-18 7:48:00.408 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Candles on Back Staircase Landing [B8])
2017-10-18 7:48:00.406 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:44:59.842 PM EDT
3 hours ago	HUB		ping	ping		ping
2017-10-18 7:42:28.425 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-18 7:42:26.019 PM EDT
3 hours ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Lights in Foyer [2F])
2017-10-18 7:42:25.996 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-18 7:39:57.946 PM EDT
3 hours ago	HUB		ping	ping		ping
2017-10-18 7:34:55.968 PM EDT
15

We are releasing a new hub firmware tomorrow 19.13 that should hopefully fix this issue. I will keep a close eye out, thanks for the help and the reports so far.

1 Like
16

19.13 appears to almost have solved the problem. It is much better than it was as the frequency has been reduced. However looking at the event log since the update pushed through I’m still seeing random power cycle events without any explanation.

2017-10-19 5:36:11.350 PM EDT
3 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:5bdff2a4-b5a8-4c61-b928-1c2b1548c239,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:5bdff2a4-b5a8-4c61-b928-1c2b1548c239, headers:SFRUUC8xLjEgMjAwIE...
2017-10-19 5:35:53.593 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-19 5:35:51.368 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-19 5:35:39.010 PM EDT
3 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:9f4cc748-3dc6-4d1e-ae1c-5a93bf1905e5,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:9f4cc748-3dc6-4d1e-ae1c-5a93bf1905e5, headers:SFRUUC8xLjEgMjAwIE...
2017-10-19 5:33:45.211 PM EDT
3 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:aa9cc649-e40f-4c48-8d3c-a3a75c6a2a56,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:aa9cc649-e40f-4c48-8d3c-a3a75c6a2a56, headers:SFRUUC8xLjEgMjAwIE...
2017-10-19 5:33:33.578 PM EDT
3 hours ago	HUB		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:1c56ee2a-d384-4b10-8bd7-205e2741222c,	index:16, mac:000420F3C826, i...		index:16, mac:000420F3C826, ip:C0A80716, port:201E, requestId:1c56ee2a-d384-4b10-8bd7-205e2741222c, headers:SFRUUC8xLjEgMjAwIE...
2017-10-19 5:32:55.044 PM EDT
3 hours ago	HUB		index:17, mac:000420F3C826, ip:C0A80716, port:201E, requestId:368b7c5b-d2b1-4606-be35-c0585b35feb7,	index:17, mac:000420F3C826, i...		index:17, mac:000420F3C826, ip:C0A80716, port:201E, requestId:368b7c5b-d2b1-4606-be35-c0585b35feb7, headers:SFRUUC8xLjEgMjAwIE...
2017-10-19 5:32:05.114 PM EDT
3 hours ago	HUB		ping	ping		ping
2017-10-19 5:30:57.147 PM EDT
3 hours ago	HUB		zbjoin: {"dni":"EB2F","d":"24FD5B00010028C5","capabilities":"80","endpoints":[{"simple":"01 0104 000	zbjoin: {"dni":"EB2F","d":"24...		zbjoin: {"dni":"EB2F","d":"24FD5B00010028C5","capabilities":"80","endpoints":[{"simple":"01 0104 000C 00 05 0000 0001 0003 000...
2017-10-19 5:29:09.505 PM EDT
3 hours ago	HUB		zbjoin: {"dni":"EB2F","d":"24FD5B00010028C5","capabilities":"80","endpoints":[{"simple":"01 0104 000	zbjoin: {"dni":"EB2F","d":"24...		zbjoin: {"dni":"EB2F","d":"24FD5B00010028C5","capabilities":"80","endpoints":[{"simple":"01 0104 000C 00 05 0000 0001 0003 000...
2017-10-19 5:28:33.052 PM EDT
3 hours ago	HUB		index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:04, mac:4C72B9F8B735, h...		index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-19 5:28:23.595 PM EDT
3 hours ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-19 5:28:23.277 PM EDT
3 hours ago	HUB		join	join		join
2017-10-19 5:28:20.950 PM EDT
3 hours ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-19 5:27:03.034 PM EDT
3 hours ago	HUB		ping	ping		ping
2017-10-19 5:22:29.477 PM EDT
3 hours ago	HUB		index:15, ip:7F000001, port:0BB8, requestId:7f58bbe3-3522-474d-893a-b05c10eaaffc, headers:SFRUUC8xLj	index:15, ip:7F000001, port:0...		index:15, ip:7F000001, port:0BB8, requestId:7f58bbe3-3522-474d-893a-b05c10eaaffc, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
17

Sounds good, I will take a look

18

I rebooted your z-wave just now, turned on some extra logging to capture the traffic with the Z-Wave chip.

The issue in 19.12 was that a particular message in a z-wave message transmission was not being sent from the z-wave chip to the application layer in the hub firmware. After digging more, we learned that the message could occasionally be dropped by the z-wave chip (not in our control to change). So we are now accounting for that in 19.13.

However, it looks to me that a subset of those missing messages is followed by the Z-wave chip not responding back, so I am investigating this now.

I am sorry this is frustrating, one because we are not in charge of what the z-wave chip does, we only interface with it, and also some of these issues are almost impossible to reproduce when during development just because different network configuration results in different timing parameters which leads to different behaviors.

2 Likes
19

Thanks for your help! I’m sure one way or another this will get resolved even if it takes cooperation with the chip manufacturer. For what its worth I’ve been experiencing some level of Z-Wave problems since I got into SmartThings 18 months ago. Please feel free to capture whatever data is necessary and let me know if there is any specific testing that you’d like me to perform.

20

It has not been a pretty day today. The last hour in particular has been ugly with 16 power cycle events. Any idea what might be happening?

2017-10-23 12:02:51.223 AM EDT
7 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-23 12:02:49.255 AM EDT
7 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-23 12:02:38.833 AM EDT
8 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-23 12:02:34.880 AM EDT
8 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-23 12:02:21.399 AM EDT
8 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-23 12:02:18.723 AM EDT
8 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-23 12:00:35.317 AM EDT
10 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-23 12:00:32.702 AM EDT
10 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-23 12:00:24.980 AM EDT
10 minutes ago	HUB		zw device: 63, command: 600D, payload: 02 00 32 02 01 74 00 08 EA C6 00 00 08 00 00 00	zw device: 63, command: 600D,...		zw device: 63, command: 600D, payload: 02 00 32 02 01 74 00 08 EA C6 00 00 08 00 00 00
2017-10-22 11:59:51.273 PM EDT
10 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:59:48.701 PM EDT
10 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:58:14.680 PM EDT
12 minutes ago	HUB		ping	ping		ping
2017-10-22 11:55:35.237 PM EDT
15 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:55:32.667 PM EDT
15 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:53:49.300 PM EDT
16 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:53:47.366 PM EDT
16 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:53:12.714 PM EDT
17 minutes ago	HUB		ping	ping		ping
2017-10-22 11:48:10.709 PM EDT
22 minutes ago	HUB		ping	ping		ping
2017-10-22 11:43:08.732 PM EDT
27 minutes ago	HUB		ping	ping		ping
2017-10-22 11:38:06.767 PM EDT
32 minutes ago	HUB		ping	ping		ping
2017-10-22 11:36:59.327 PM EDT
33 minutes ago	HUB		index:15, ip:7F000001, port:0BB8, requestId:590527ec-4e77-4698-9c40-799224005254, headers:SFRUUC8xLj	index:15, ip:7F000001, port:0...		index:15, ip:7F000001, port:0BB8, requestId:590527ec-4e77-4698-9c40-799224005254, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-22 11:36:59.240 PM EDT
33 minutes ago	HUB		index:16, ip:7F000001, port:0BB8, requestId:b9903542-a586-4ee2-b7d2-ce0c0a42308e, headers:SFRUUC8xLj	index:16, ip:7F000001, port:0...		index:16, ip:7F000001, port:0BB8, requestId:b9903542-a586-4ee2-b7d2-ce0c0a42308e, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-22 11:36:59.160 PM EDT
33 minutes ago	HUB		index:15, ip:7F000001, port:0BB8, requestId:e41304f2-be8e-443b-957e-457e827a0da7, headers:SFRUUC8xLj	index:15, ip:7F000001, port:0...		index:15, ip:7F000001, port:0BB8, requestId:e41304f2-be8e-443b-957e-457e827a0da7, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-22 11:36:59.066 PM EDT
33 minutes ago	HUB		index:16, ip:7F000001, port:0BB8, requestId:1e0fad74-e797-4e77-82c0-f5b2b486bd9b, headers:SFRUUC8xLj	index:16, ip:7F000001, port:0...		index:16, ip:7F000001, port:0BB8, requestId:1e0fad74-e797-4e77-82c0-f5b2b486bd9b, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-22 11:36:58.964 PM EDT
33 minutes ago	HUB		index:15, ip:7F000001, port:0BB8, requestId:8cc20e09-a4dc-473d-b9d4-44250a9ee67c, headers:SFRUUC8xLj	index:15, ip:7F000001, port:0...		index:15, ip:7F000001, port:0BB8, requestId:8cc20e09-a4dc-473d-b9d4-44250a9ee67c, headers:SFRUUC8xLjEgNDAwIEJhZCBSZXF1ZXN0DQpT...
2017-10-22 11:33:04.832 PM EDT
37 minutes ago	HUB		ping	ping		ping
2017-10-22 11:32:03.332 PM EDT
38 minutes ago	HUB		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:01, mac:4C72B9F8B735, h...		index:01, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-22 11:31:16.863 PM EDT
39 minutes ago	HUB		index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:04, mac:4C72B9F8B735, h...		index:04, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-22 11:30:48.858 PM EDT
40 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:30:44.821 PM EDT
40 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:30:17.359 PM EDT
40 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:30:14.832 PM EDT
40 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:30:06.844 PM EDT
40 minutes ago	HUB		index:06, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDAN	index:06, mac:4C72B9F8B735, h...		index:06, mac:4C72B9F8B735, headers:UE9TVCAvbW90aW9uIEhUVFAvMS4xDQpIb3N0OiAxOTIuMTY4LjcuMzA6Mzk1MDANCkFjY2VwdDogKi8qDQpDb250ZW...
2017-10-22 11:28:03.124 PM EDT
42 minutes ago	HUB		ping	ping		ping
2017-10-22 11:25:02.831 PM EDT
45 minutes ago	HUB		zw device: 63, command: 600D, payload: 02 00 32 02 21 74 00 0A 81 C2 00 00 00 00 00 00	zw device: 63, command: 600D,...		zw device: 63, command: 600D, payload: 02 00 32 02 21 74 00 0A 81 C2 00 00 00 00 00 00
2017-10-22 11:23:48.830 PM EDT
47 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:23:47.246 PM EDT
47 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:23:47.221 PM EDT
47 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Lamp in Dining Room [09])
2017-10-22 11:23:19.299 PM EDT
47 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:23:17.335 PM EDT
47 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:23:17.334 PM EDT
47 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Air Conditioner In Bedroom [BD])
2017-10-22 11:23:00.832 PM EDT
47 minutes ago	HUB		ping	ping		ping
2017-10-22 11:21:59.348 PM EDT
48 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:21:56.853 PM EDT
49 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:21:48.890 PM EDT
49 minutes ago	HUB		zw device: 7B, command: 600D, payload: 01 00 32 02 21 74 00 09 DD 16 00 00 00 00 00 00	zw device: 7B, command: 600D,...		zw device: 7B, command: 600D, payload: 01 00 32 02 21 74 00 09 DD 16 00 00 00 00 00 00
2017-10-22 11:21:04.914 PM EDT
49 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:21:01.077 PM EDT
49 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:21:01.076 PM EDT
49 minutes ago	HUB		zwBadNode			Err 120: Z-Wave send timed out (Rptr: Clothes Washer [0E])
2017-10-22 11:17:59.197 PM EDT
52 minutes ago	HUB		ping	ping		ping
2017-10-22 11:16:27.314 PM EDT
54 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:16:24.910 PM EDT
54 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:14:57.409 PM EDT
56 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:14:55.005 PM EDT
56 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started
2017-10-22 11:14:54.850 PM EDT
56 minutes ago	HUB		zw device: 2B, command: 3202, payload: 21 74 00 12 38 94 00 00 00 00 00 00	zw device: 2B, command: 3202,...		zw device: 2B, command: 3202, payload: 21 74 00 12 38 94 00 00 00 00 00 00
2017-10-22 11:13:37.349 PM EDT
57 minutes ago	HUB		zwStatus	ready		Z-Wave is ready
2017-10-22 11:13:34.789 PM EDT
57 minutes ago	HUB		zwStatus	power cycle		Z-Wave power cycle started