Unable to Skip or Continue on Z-Wave Pairing

Background: I had 2 Aeotec Door/Window Sensor 7 Series devices that had battery failure. Couldn’t get them to respond after replacing the batteries. Did the Exclude Remove (successful), then Include. Pop Up dialog asking Skip / Continue popped up about S2 inclusion, neither button was operable. Believe that the dialog wasn’t in the foreground, and that it was overlaid by the inclusion window, preventing focus on the dialog.

512 GB iPad Pro 10.5 inch with iPad OS 15.0.2 running Safari
Same results on 256 GB iPhone 7 with iOS 15.0.2 running Safari

C-7 running 2.2.9.134

Screenshot:

I was able to fool around with resizing of windows and get it to work, eventually.

By the way, observations on Z-Wave Repair:

All battery devices (except Schlage BE469ZP locks, which are FLiRS) no longer show Repair (node repair) button. Doing a full Z-Wave Repair, which I don’t prefer, but had to do in the absence of node Repair button, failed these two devices on the first pass (I was only able to pair next to hub, which meant neighbor info was wrong), but was successful on the second pass. Seems better at Z-Wave repair than when the C-7 first came out. Good work, Bryan (@bcopeland).

I preferred the old UI with Z-Wave details accessible from menu in upper right corner of all pages. Made it easier when flipping around between device page and Z-Wave details page. This difficulty could be remedied if a Z-Wave Details link button was added beside the Device List button in the upper left corner on each device page. Just a suggestion.

1 Like

The reason sleepy devices don’t have single node repair is because there is no way to accomplish this since they are not listening. They do get their routes updated about once a week during a wakeup cycle.

Looks like we still need to track this bug down..

1 Like

Understood. However, Tony Fleisher’s (@tony.fleisher’s) excellent Mesh Details app does have a Node Repair button even for battery devices - I can get it to work, for example, on the Aeotec DWS7 devices by triggering the Tamper switch to wake up the device.

Guarantee it does nothing.. Can’t repair a sleepy node

1 Like

You would also have to prevent the node from going to sleep, which the driver will do..

BTW if you need to add more devices until we get that UI issue fixed you can use the older UI /hub/scanDevice

1 Like