Another zwave issue

🛎️ Get Help
1

*Updated title to more accurately reflect issue

I have a similar issue to spartanrob on a C7. The lock would report status changes but would not respond to commands. Rebooted hub, power cycle hub, power cycle lock...no change. Tried to exclude/re-include. Excluded successfully, but upon including it is stuck on "initializing". Tried several combinations of exclude, reboot, include, move hub to within inches of lock...to no avail. Included the lock successfully to my C5, which is across the room. Any ideas?

Checked Z-Wave logs and I get this when including:

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:08:03.287 seqNo: 94, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:08:02.986 seqNo: 94, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:08:02.785 seqNo: 93, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:08:02.385 seqNo: 93, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:08:00.281 seqNo: 92, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:59.980 seqNo: 92, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:59.780 seqNo: 91, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:59.379 seqNo: 91, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:57.274 seqNo: 90, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:56.973 seqNo: 90, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:56.773 seqNo: 89, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:56.372 seqNo: 89, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:54.260 seqNo: 88, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:53.959 seqNo: 88, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:53.759 seqNo: 87, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:53.458 seqNo: 87, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:51.355 seqNo: 86, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:50.954 seqNo: 86, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:50.854 seqNo: 85, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[4A](http://10.10.0.24/hub/zwaveLogs#zwaveRx4A)2021-04-28 11:07:50.453 seqNo: 85, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs
2

Leave it on the C5 and use Hub Mesh?

3

How long has your C7 been in place? I ask because the mesh needs some time to work it’s magic. Initially when I moved my zwave devices from C5 to C7 my older lock wouldn’t pair. Tried a week later and it did. Who knows what changed.

4

That's the purpose of it being on the C7...it is my device host, lol.

5

I have been using HubMesh since they introduced it last year

6

I figured that wasn't going to work.

7

I excluded/reincluded a spare switch, that worked without a problem. Although, that was a S2 not a S0 like the lock is. Restored to yesterday's backup and zwave radio to recover all the device IDs I blew today, lol... Since the device was back in the radio table I tried to "replace" it through the zwave details page (exclude with C5, press 'replace', activate device pairing mode) process showed successful but didn't work. The C5 picks it up almost instantly as I hit "0" on the keypad. With the C7, there is about a 10sec delay before it shows up as "initializing" and doesn't go any further. Lock firmware is 7.1, if that makes any difference.

1 Like
8

@Srt4fun 1st check for ghosts in your z-wave table. Even one can pooch the pairings. If no ghosts, shut down hub from settings menu then unplug power from wall (not hub) for 5 mins. During this 5 mins disconnect the battery in the lock. Power back up. Check z-wave table for ghosts. IF not exist proceed to pairing. Prior to pairing the lock, factory reset the lock (note your programming codes) Factory reset consists of while the battery is disconnected press the schlage button a few times to discharge the caps. Press and hold the schlage button while reconnecting the battery. Keep hold the schlage button until the green check mark on the keypad flashes 3 times. Start normal pairing (hit pair on the c7 first, and this is the most important thing with these locks, pair the lock and the hub within 3 feet of eachother) Once pairing is complete put lock and hub in final home positions and run a z-wave repair (Note: before disconnecting power always shutdown from the settings menu to prevent corruption of the database)

9

Ahh yes, I did come across your solution in my research. No ghost devices. Factory reset on these locks does not clear the zwave settings(but I did do exactly as you describe). Tried with hub about 1.5ft away, next try was with hub within inches, and after that was with hub touching the lock...no success. Also tried removing power to as many of my zwave repeating devices as I could, in case of interference, with no success.

The lock pairs instantly to my C5, which is about 15ft across the room. 3 out of 3 times I included it to the C5 it completed the pairing process on first try and without issue. At this time I am assuming it is an issue with the C7.

1 Like
10

I will revert back to 2.2.5 and see how that goes.

11

Rolled back to 2.2.5. Does not look good for the hub...had issues with zwave repair. Ran it 3 times, no ghost devices, all devices online (except for the door lock)...part way through it times out on different devices then all other zwave devices are "unreachable" yet they still report their status' to the hub and do not respond to commands. It seems more and more that it is not the fault of the lock this time, but of the hub.

10min later the zwave devices are starting to respond to commands again with a delay at first, but now responding normally.

Log of my last zwave repair:

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:05:10.570 am Finished Z-Wave Network Repair

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:05:04.550 am Z-Wave Node 34: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:05:02.353 am Z-Wave Node 34: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:05:02.343 am Z-Wave Node 34: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:05:01.324 am Z-Wave Node 30: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:59.126 am Z-Wave Node 30: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:59.116 am Z-Wave Node 30: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:58.106 am Z-Wave Node 2B: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:55.894 am Z-Wave Node 2B: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:55.880 am Z-Wave Node 2B: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:54.866 am Z-Wave Node 29: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:52.682 am Z-Wave Node 29: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:52.671 am Z-Wave Node 29: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:51.667 am Z-Wave Node 27: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:49.462 am Z-Wave Node 27: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:49.453 am Z-Wave Node 27: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:48.445 am Z-Wave Node 24: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:46.241 am Z-Wave Node 24: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:46.227 am Z-Wave Node 24: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:45.223 am Z-Wave Node 21: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:43.013 am Z-Wave Node 21: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:43.002 am Z-Wave Node 21: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:42.000 am Z-Wave Node 20: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:39.794 am Z-Wave Node 20: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:39.782 am Z-Wave Node 20: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:38.766 am Z-Wave Node 1F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:36.565 am Z-Wave Node 1F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:36.555 am Z-Wave Node 1F: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:35.559 am Z-Wave Node 1E: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:33.346 am Z-Wave Node 1E: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:33.324 am Z-Wave Node 1E: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:32.318 am Z-Wave Node 1A: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:30.118 am Z-Wave Node 1A: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:30.108 am Z-Wave Node 1A: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:29.110 am Z-Wave Node 18: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:16.861 am Z-Wave Node 18: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:16.849 am Z-Wave Node 18: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:15.844 am Z-Wave Node 13: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:13.634 am Z-Wave Node 13: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:13.624 am Z-Wave Node 13: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:12.620 am Z-Wave Node 43: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:10.426 am Z-Wave Node 43: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:10.411 am Z-Wave Node 43: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:09.405 am Z-Wave Node 42: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:07.212 am Z-Wave Node 42: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:07.202 am Z-Wave Node 42: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:05.197 am Z-Wave Node 3F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:02.987 am Z-Wave Node 3F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:02.977 am Z-Wave Node 3F: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:04:01.986 am Z-Wave Node 2E: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:59.778 am Z-Wave Node 2E: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:59.768 am Z-Wave Node 2E: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:58.754 am Z-Wave Node 28: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:56.573 am Z-Wave Node 28: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:56.560 am Z-Wave Node 28: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:55.545 am Retrying Failed Nodes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:50.539 am Z-Wave Node 34: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:48.346 am Z-Wave Node 34: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:48.342 am Z-Wave Node 34: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:47.340 am Z-Wave Node 30: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:45.135 am Z-Wave Node 30: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:45.127 am Z-Wave Node 30: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:44.128 am Z-Wave Node 2B: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:41.939 am Z-Wave Node 2B: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:41.928 am Z-Wave Node 2B: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:40.901 am Z-Wave Node 29: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:38.724 am Z-Wave Node 29: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:38.720 am Z-Wave Node 29: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:37.719 am Z-Wave Node 27: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:35.524 am Z-Wave Node 27: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:35.514 am Z-Wave Node 27: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:34.502 am Z-Wave Node 24: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:32.317 am Z-Wave Node 24: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:32.314 am Z-Wave Node 24: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:31.319 am Z-Wave Node 21: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:29.109 am Z-Wave Node 21: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:29.099 am Z-Wave Node 21: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:28.101 am Z-Wave Node 20: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:25.905 am Z-Wave Node 20: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:25.891 am Z-Wave Node 20: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:24.883 am Z-Wave Node 1F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:22.675 am Z-Wave Node 1F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:22.665 am Z-Wave Node 1F: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:21.662 am Z-Wave Node 1E: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:19.461 am Z-Wave Node 1E: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:19.457 am Z-Wave Node 1E: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:18.465 am Z-Wave Node 1A: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:16.265 am Z-Wave Node 1A: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:16.255 am Z-Wave Node 1A: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:15.251 am Z-Wave Node 18: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:03.019 am Z-Wave Node 18: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:03.010 am Z-Wave Node 18: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:03:02.026 am Z-Wave Node 13: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:59.797 am Z-Wave Node 13: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:59.787 am Z-Wave Node 13: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:58.772 am Z-Wave Node 43: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:56.585 am Z-Wave Node 43: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:56.570 am Z-Wave Node 43: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:55.539 am Z-Wave Node 42: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:53.358 am Z-Wave Node 42: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:53.351 am Z-Wave Node 42: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:51.347 am Z-Wave Node 3F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:49.131 am Z-Wave Node 3F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:49.118 am Z-Wave Node 3F: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:48.111 am Z-Wave Node 2E: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:45.910 am Z-Wave Node 2E: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:02:45.900 am Z-Wave Node 2E: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:01:45.862 am Z-Wave Node 28: Repair timed out assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:59:15.775 am Z-Wave Node 28: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:59:15.344 am Z-Wave Node 28: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:55.756 am Z-Wave Node 28: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:53.444 am Z-Wave Node 28: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:53.438 am Z-Wave Node 28: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:51.543 am Z-Wave Node 25: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:51.397 am Z-Wave Node 25: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:51.246 am Z-Wave Node 25: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:51.101 am Z-Wave Node 25: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:50.972 am Z-Wave Node 25: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:50.839 am Z-Wave Node 25: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:50.665 am Z-Wave Node 25: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:42.440 am Z-Wave Node 25: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:40.215 am Z-Wave Node 25: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:40.203 am Z-Wave Node 25: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:38.397 am Z-Wave Node 1D: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:38.066 am Z-Wave Node 1D: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:37.417 am Z-Wave Node 1D: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:37.107 am Z-Wave Node 1D: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:36.787 am Z-Wave Node 1D: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:36.517 am Z-Wave Node 1D: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:35.951 am Z-Wave Node 1D: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:25.179 am Z-Wave Node 1D: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:22.957 am Z-Wave Node 1D: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:22.945 am Z-Wave Node 1D: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:21.051 am Z-Wave Node 1C: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:20.848 am Z-Wave Node 1C: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:20.698 am Z-Wave Node 1C: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:20.559 am Z-Wave Node 1C: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:20.428 am Z-Wave Node 1C: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:20.296 am Z-Wave Node 1C: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:20.194 am Z-Wave Node 1C: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:13.929 am Z-Wave Node 1C: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:10.496 am Z-Wave Node 1C: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:10.492 am Z-Wave Node 1C: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:08.619 am Z-Wave Node 1B: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:07.910 am Z-Wave Node 1B: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:07.201 am Z-Wave Node 1B: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:06.504 am Z-Wave Node 1B: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:05.702 am Z-Wave Node 1B: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:04.896 am Z-Wave Node 1B: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:58:04.091 am Z-Wave Node 1B: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:52.481 am Z-Wave Node 1B: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:50.254 am Z-Wave Node 1B: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:50.243 am Z-Wave Node 1B: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.963 am Z-Wave Node 17: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.824 am Z-Wave Node 17: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.672 am Z-Wave Node 17: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.523 am Z-Wave Node 17: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.373 am Z-Wave Node 17: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.223 am Z-Wave Node 17: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:48.058 am Z-Wave Node 17: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:39.231 am Z-Wave Node 17: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:37.013 am Z-Wave Node 17: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:37.002 am Z-Wave Node 17: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:35.366 am Z-Wave Node 14: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:35.226 am Z-Wave Node 14: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:35.090 am Z-Wave Node 14: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:34.947 am Z-Wave Node 14: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:34.793 am Z-Wave Node 14: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:34.672 am Z-Wave Node 14: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:34.481 am Z-Wave Node 14: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:26.986 am Z-Wave Node 14: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:24.779 am Z-Wave Node 14: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:24.773 am Z-Wave Node 14: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:23.621 am Z-Wave Node 12: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:23.484 am Z-Wave Node 12: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:23.319 am Z-Wave Node 12: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:23.125 am Z-Wave Node 12: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:22.969 am Z-Wave Node 12: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:22.836 am Z-Wave Node 12: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:22.731 am Z-Wave Node 12: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:15.765 am Z-Wave Node 12: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:13.538 am Z-Wave Node 12: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:13.531 am Z-Wave Node 12: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:11.686 am Z-Wave Node 07: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:57:11.538 am Z-Wave Node 07: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:52.689 am Z-Wave Node 07: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:52.248 am Z-Wave Node 07: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:51.856 am Z-Wave Node 07: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:51.506 am Z-Wave Node 07: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:50.159 am Z-Wave Node 07: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:42.515 am Z-Wave Node 07: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:40.322 am Z-Wave Node 07: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:40.319 am Z-Wave Node 07: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:39.101 am Z-Wave Node 40: Repair is done.

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:38.975 am Z-Wave Node 40: Repair assigning route 5

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:38.846 am Z-Wave Node 40: Repair assigning route 4

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:38.718 am Z-Wave Node 40: Repair assigning route 3

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:38.589 am Z-Wave Node 40: Repair assigning route 2

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:38.460 am Z-Wave Node 40: Repair assigning route 1

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:38.397 am Z-Wave Node 40: Repair is assigning legacy routes

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:32.315 am Z-Wave Node 40: Repair is running

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:30.124 am Z-Wave Node 40: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:30.120 am Z-Wave Node 40: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:25.079 am Refreshing Node States

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 10:56:25.073 am Starting Z-Wave Network Repair
12

Probably a dumb question, but just want to make sure...would I be able to backup to cloud, reset zwave radio, test the device, then restore zwave radio from cloud backup and pick up where I left off? Seems a little drastic, but a good way to find out if it is a device on the network causing issues.

13

Right now all of my zwave devices have stopped responding to commands, again... here is a log showing that the hub thinks it is "unreachable", yet in the hub log the device is reporting its state. Device ID 0x3F is the Dining Room Controller. It is an inovelli ceiling fan/light device(lzw36).

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:43:11.087 pm Z-Wave Node 3F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:43:08.883 pm Z-Wave Node 3F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:43:08.879 pm Z-Wave Node 3F: Repair starting

[dev:299](http://10.10.0.24/logs#dev299)2021-04-29 11:43:05.067 pm [info](http://10.10.0.24/device/edit/299)Z-Open Motion is inactive

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:43:03.853 pm Refreshing Node States

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:43:03.849 pm Starting Z-Wave Network Repair

[dev:300](http://10.10.0.24/logs#dev300)2021-04-29 11:43:03.514 pm [info](http://10.10.0.24/device/edit/300)Living Room Motion is inactive

[dev:498](http://10.10.0.24/logs#dev498)2021-04-29 11:42:50.601 pm [debug](http://10.10.0.24/device/edit/498)Dining Room Controller: SwitchMultilevelReport(value: 45, targetValue: null, duration: null) - ep1

[dev:498](http://10.10.0.24/logs#dev498)2021-04-29 11:42:50.596 pm [debug](http://10.10.0.24/device/edit/498)Dining Room Controller: MultiChannelCmdEncap(bitAddress:false, command:3, commandClass:38, destinationEndPoint:0, parameter:[45], res01:false, sourceEndPoint:1)

[dev:498](http://10.10.0.24/logs#dev498)2021-04-29 11:42:49.662 pm [debug](http://10.10.0.24/device/edit/498)Dining Room Controller: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:3) 0

[dev:299](http://10.10.0.24/logs#dev299)2021-04-29 11:42:45.659 pm [info](http://10.10.0.24/device/edit/299)Z-Open Motion is active

[dev:300](http://10.10.0.24/logs#dev300)2021-04-29 11:42:45.294 pm [info](http://10.10.0.24/device/edit/300)Living Room Motion is active

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:45.120 pm Finished Z-Wave Network Repair

[dev:299](http://10.10.0.24/logs#dev299)2021-04-29 11:42:39.068 pm [info](http://10.10.0.24/device/edit/299)Z-Open Motion is inactive

[dev:300](http://10.10.0.24/logs#dev300)2021-04-29 11:42:38.467 pm [info](http://10.10.0.24/device/edit/300)Living Room Motion is inactive

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:38.128 pm Z-Wave Node 3F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:35.911 pm Z-Wave Node 3F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:35.903 pm Z-Wave Node 3F: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:30.883 pm Refreshing Node States

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:30.879 pm Starting Z-Wave Network Repair

[dev:299](http://10.10.0.24/logs#dev299)2021-04-29 11:42:30.014 pm [info](http://10.10.0.24/device/edit/299)Z-Open Motion is active

[dev:300](http://10.10.0.24/logs#dev300)2021-04-29 11:42:24.430 pm [info](http://10.10.0.24/device/edit/300)Living Room Motion is active

[dev:300](http://10.10.0.24/logs#dev300)2021-04-29 11:42:14.150 pm [info](http://10.10.0.24/device/edit/300)Living Room Motion is inactive

[dev:299](http://10.10.0.24/logs#dev299)2021-04-29 11:42:10.138 pm [info](http://10.10.0.24/device/edit/299)Z-Open Motion is inactive

[dev:498](http://10.10.0.24/logs#dev498)2021-04-29 11:42:07.917 pm [debug](http://10.10.0.24/device/edit/498)Dining Room Controller: SwitchMultilevelReport(value: 0, targetValue: null, duration: null) - ep1

[dev:498](http://10.10.0.24/logs#dev498)2021-04-29 11:42:07.900 pm [debug](http://10.10.0.24/device/edit/498)Dining Room Controller: MultiChannelCmdEncap(bitAddress:false, command:3, commandClass:38, destinationEndPoint:0, parameter:[0], res01:false, sourceEndPoint:1)

[dev:498](http://10.10.0.24/logs#dev498)2021-04-29 11:42:06.264 pm [debug](http://10.10.0.24/device/edit/498)Dining Room Controller: CentralSceneNotification(keyAttributes:0, sceneNumber:2, sequenceNumber:2) 0

[dev:299](http://10.10.0.24/logs#dev299)2021-04-29 11:42:04.151 pm [info](http://10.10.0.24/device/edit/299)Z-Open Motion is active

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:42:03.824 pm Finished Z-Wave Network Repair

[dev:300](http://10.10.0.24/logs#dev300)2021-04-29 11:42:03.466 pm [info](http://10.10.0.24/device/edit/300)Living Room Motion is active

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:41:56.781 pm Z-Wave Node 3F: Repair failed node unreachable

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:41:54.565 pm Z-Wave Node 3F: Repair is pinging the node

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:41:54.553 pm Z-Wave Node 3F: Repair starting

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:41:49.514 pm Refreshing Node States

[sys:1](http://10.10.0.24/logs#sys1)2021-04-29 11:41:49.510 pm Starting Z-Wave Network Repair
0x3F (063) 
PER: 0, RTT Avg: 2ms, LWR RSSI: 23dB
Neighbors: 28, Route Changes: 2
OK
in: 0x5E, 0x55, 0x98, 0x9F, 0x6C, 0x26, 0x70, 0x85, 0x59, 0x8E, 0x86, 0x72, 0x5A, 0x73, 0x75, 0x22, 0x7A, 0x5B, 0x87, 0x60, 0x32, out:
[Dining Room Controller](http://10.10.0.24/device/edit/498) 
None 
01 -> 3F 100kbps

The below code shows entries of the zwave log. 1st one is when issue is active. 2nd is when hub operating normally. In both cases I clicked the 'on' button within the edit device page.

Dining Room Controller 2021-04-29 23:58:58.650 seqNo: 112, routeChanged: false, transmissionTime: 0ms, repeaters: None, speed: Unknown, rssi: [0 dBm, 0 dBm, 0 dBm, 0 dBm, 0 dBm], Ack channel: 0, Transmit channel: 0

Dining Room Controller 2021-04-30 00:07:57.480 seqNo: 206, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 100 kbs, rssi: [-77 dBm, N/A, N/A, N/A, N/A], Ack channel: 0, Transmit channel: 0
14

Unsure if anyone still reading this, but I got a replacement BE469ZP lock today. Same result as the plain ol' zwave one... I get the prompt to input the security key --> type it in --> about 5sec later the lock's light blinks green to indicate successful pairing --> about 5-10sec after that, the device shows up under "Found Devices", but remains "initializing". Tried pairing with no security, but the lock says no, lol. But, also like the other one, it works perfectly with the C5 hub.

zwave table entry

0x4C (076)
PER: 0, RTT Avg: 180ms, LWR RSSI:
Neighbors: 23, Route Changes: 4
OK
in: , out:
S2 Access Control
01 -> 4C 40kbps
15

How long did you wait? I have seen some devices take several minutes to complete the S2 inclusion process.

16

After a few tries I had reset everything and started the process. Then went to make dinner. Was at least 30min, Hub staying within 3ft of device, web browser tab left open and undisturbed.

17

I think I may have found the issue. Got an Aeotec Z-Stick Gen 5+ to check under the hood. Found 3 nodes (57,58,59) that do not appear in the C7's radio table. Now the only task is to remove them... tried to mark them as failed but the controller responds that they are not failed... so weird. Sent 'Basic Set ON' and 'Basic Set OFF' commands. Known devices respond, but nothing happens in the log/physically with the 3 suspected orphans. Removed power from all devices after orphaned entries, still responds 'not failed'. My next step is a soft reset...but since that doesn't mess with the zwave radio I am not expecting much. A zwave radio reset then restore zwave radio from backup would, at the least, keep me where I am now, correct? or would I still have to re-pair all my devices one-by-one?

Orphans
Orphans1920×1080 629 KB

Edit: As expected, soft reset did not change anything.

18

So I am not sure how you get rid of "virtual" nodes.. you probably have to get rid of the existing device they refer to which is probably why "is failed" is not working. Hopefully someone a bit more knowledgeable than me can chime in.

Be careful though as HE uses virtual nodes - usually the first five or so.

19

Good idea, After work I will exclude the devices above and below. Maybe powering them off was just not good enough, lol. 56 is a Zooz 4in1 v2 and 63 is an Inovelli fan/light device.

20

So the 4-in-1s definitely have issues... there are a ton of threads about that. Might want check it out but I suspect the virtual devices are associated with the Inovelli in this case. Can that unit be air-gapped easily?