[2.2.5.131 C7] - Pairing Difficulties

[rob9]

My door lock busted--so I was replacing it (it's a Schlage ZW/S0 lock--yuck, but it's what I've got atm).

I moved the hub to about 6 feet, line of sight, in clear air to the door lock.

I was able to do the "exclude" part.

Then, I went to "include" the new lock. It recognized the lock and assigned it a nodeid. However, the include never completed. After that, I tried doing an "exclude" and it failed.

I'm going to shutdown then power cycle the hub.

It's almost like the z-wave stack has regressed to before the changes @bcopeland made a while back that spiffed it up.

[rob9]

That allowed me to again exclude the device (it was #33).

I went through the pairing process again and it tried to assign it #34. Again, it got partway through and failed.

I was able to exclude it again.

I then tried to pair it again.

Oddly, this time, the Z-Wave logs showed a mix of activity from node 34 (which was the prior failed pairing nodeid that was EXCLUDED already)--and a bunch of traffic from nodeid 35.

However, it still never paired.

Rebooting and trying again.

[672southmain]

Sure you don’t have a ghost node from the failed pairings?

You might try an exclude on the already-excluded device.

[lawsonad]

I have four of the Schlage Z-wave locks, including one of the non-Plus S0 models. The locks go into a "low power mode" when excluding/including from what I've read online. Either way my experience is the lock needs to be within 1ft (basically sitting right next to) the hub or it will not exclude/include properly. You can take the keypad and back portion off your door, move to the hub location and power up to to the operations. Worked for me many times.

Make sure you have no ghosts from previous attempts and then give that a try.

[rob9]

I'm not seeing any ghosts.

And, I moved the hub. it is now TOUCHING the lock. We'll see what happens.

[rob9]

And, SAME thing.

This would def seem to be a bug with the hub, look at the screen:

1. Despite being "Not in Discovery mode", it has LEFT the "Stop Z-Wave Inclusion" button showing. Somehow, it is simply NOT properly completing some process.

2. I also see quite a bit of traffic in the "Z-Wave Logs" well after the inclusion process has supposedly timed out (but, it seems to be of no matter-as the device doesn't seem to finish pairing).

And, looking at the regular log, you can see the hub entering "Discovery Mode"--but it never exits:

The Z-Wave log:

For grins, I tried just doing a "start inclusion" again--it popped right up with this:

But, I didn't see anything in the logs or z-wave logs--And, again, it timed out and left the "Stop Z-Wave Inclusion" button visible.

[rob9]

It's also interesting that the RSSI value when the hub is touching the back side of the lock is -42. And, I see it at -72 for a Ring Gen 2 contact sensor device that is 3.5' in clear air away from the hub.

[rob9]

So, this is just plain non-sensical.

I excluded my door lock (after another reboot), then went to do an include again.

Suddenly I see THIS pop up:

That was a GE/Jasco S2 Dimmer that has LONG been properly paired to my system.

There was not even a remote CHANCE that this had a "include" performed.

Moreover, that particular device was already in the Device List with nodeid D9.

That is totally confusing.

[rob9]

I tried backing off to 2.2.4.158 -- and it wasn't any better.

[rob9]

BTW, it does appear to create a "ghost node" after I try to pair it and before I get it excluded.

[rob9]

Related to the driver for this lock, I happened to get this doing a "refresh()" on a similar lock: