Running HE 220.127.116.11 on a C-7.
Mid-week last week my neighborhood suffered an extended power outage. After power was restored, my z-wave mesh was catastrophically unstable. Devices kept ending up reported as failed or not responding, and no amount of z-wave repair would keep devices in the OK category for very long. Mostly I have Zooz switches/dimmers, with a few Ecolink contact sensors and one Sensitive Strips Guard contact sensor. It's a new project, and my device count is low at the moment (23 total).
I finally gave up and decided to start from scratch: all devices were factory reset and I wiped the z-wave radio using the "reset" command. After re-including everything, the mesh is better than ever. However, my Sensitive Strips Guard contact sensor would NOT re-include. I followed the instructions for excluding it and factory resetting it using the magnet, and the inclusion process would detect it and let me type in a device name, but then I'd see a timeout error in the logs and the Strips Guard would give me 5 fast blinks for every open/close event (i.e. no communication with the hub). Clearly, the inclusion process was being terminated prematurely for some reason. This behavior was observed with the device approximately 2 feet from my hub. When excluded or factory reset, the Strips Guard correctly indicated demo mode by giving me 2 blinks for open/close events.
I ran two network-wide z-wave repairs, and waited a good couple of hours after each repair before attempting device discovery. After the second z-wave repair / wait period, the device is suddenly working... no idea why. I still saw the inclusion timeout event reported in the log, but this time the inclusion seems to have finished and established communication. I'm pasting the relevant log section here in the hopes that it helps someone working on the next iteration of HE software or z-wave radio code. Note that the timeout event is reported immediately after the HE finds the contact sensor. Hope this helps someone...
The upshot is, my $50 contact sensor can be re-included after a major event, but it takes some effort. Here's the log:
[dev:252] 2020-10-20 11:21:09.557 am [warn] configure...
[sys:1] 2020-10-20 11:21:02.176 am warnZ-Wave Inclusion timed out, status:7
[sys:1] 2020-10-20 11:21:02.165 am infoZ-Wave Discovery Stopped
[dev:252] 2020-10-20 11:21:01.989 am [debug] parsed 'zw device: 34, command: 8003, payload: 64 , isMulticast: false' to [[name:battery, unit:%, value:100, descriptionText:Generic Z-Wave Contact Sensor battery is 100%], 8408]
[dev:252] 2020-10-20 11:21:01.984 am [debug] parsed 'zw device: 34, command: 8003, payload: 64 , isMulticast: false' to [[name:battery, unit:%, value:100, descriptionText:Generic Z-Wave Contact Sensor battery is 100%], 8408]
[dev:252] 2020-10-20 11:21:01.965 am [info] Generic Z-Wave Contact Sensor battery is 100%
[dev:252] 2020-10-20 11:21:01.953 am [info] Generic Z-Wave Contact Sensor battery is 100%
[dev:252] 2020-10-20 11:21:01.802 am [debug] parsed 'zw device: 34, command: 7205, payload: 01 9A 00 03 00 03 , isMulticast: false' to 
[dev:252] 2020-10-20 11:21:01.760 am [debug] msr: 019A-0003-0003
[dev:252] 2020-10-20 11:21:01.567 am [warn] configure...
[dev:252] 2020-10-20 11:21:01.442 am [info] installed...
[sys:1] 2020-10-20 11:20:43.207 am infoZ-Wave Discovery Running