Getting a null exception

🛎️ Get Help
1

I've been trying to pair up a Yale lock and it seems to fail to complete the pairing.

In the logs, this entry showed up a bunch of times:
app:3572019-06-02 01:25:52.331 pm errorjava.lang.NullPointerException: Cannot invoke method isNewDevice() on null object on line 291 (discoverySearchHandler)

I think this happened because I had started to pair it, then the Yale indicated failure, but the Hubitat UI shows initializing. Discovery had finished, and it never completed the pairing, so I had to exclude the device. When I tried to pair it again, the failed pairing shows up with an id, and then a new id shows up for the re-pairing. The Yale indicates pair success immediately, but the UI is stuck at initializing for both device id's (the old failed pairing, and the new pairing). I repaired the z-wave network, I rebooted the hub and tried to pair again, but again it found the device, started initializing, but the Yale failed to pair.

Any suggestions to clear this error?

BTW. It seems you can start device exclusion and device pairing at the same time. I found that out because I was excluding to try to re-pair, but hit start while the exclusion was counting down still. Not sure if that is supposed to be possible.

2

Not sure which Yale lock you have. I have the YRD 256 and it joins very easily. I don't see that you did a factory reset. I would recommend that you first delete the Generic Z-Wave Lock Driver if it exists in your devices list, then do a general exclusion. Then a factory reset. Make sure you are within 10 feet or less from the hub when you attempt to join.

3

This actually seems to be an issue with one of my Hubitat hubs. It actually paired fine before, but then I swapped the radio module between two of the locks (I couldn't exclude one lock due to it's distance). When I swapped them back, the first lock that was originally paired wouldn't respond anymore to my hub commands. I think there must be some type of data corruption with this one lock on this one hub. I'm hoping the hub will do some cleanup or something soon so I can try to pair it again.

4

I should have added to also make sure you are within 10 feet or less when you attempt a general exclusion, as that will not work through repeaters.

5

Yup.

So it looks like there's multiple pending devices to pair on this hub. Every time I do device discovery, it shows "dead" initializing devices for the lock. It then finds the lock, adds a new network id for a new device and then fails to pair. I'm thinking the hub is in a bad state for this particular device, but not sure how to clear it out.

1 Like
6

Sounds like you have zombies. Let it sit like you were suggesting and it will clean them up. Might take two 2am cleanup cycles, but they should all clear. Then try again excluded, reset and close. Should work fine.:+1:

1 Like
7

I've been trying to pair a Yale smartlock and it will not finish the initialization. The device discovery page shows a bunch of zombie z-wave devices now, and every time I try to pair, it just creates a new device in initializing, but never finishes. I know this isn't a Yale lock issue as I've got another one paired and working properly. The state of the hub for this one lock is bad, and I have no idea how to clear the hub out for this lock.

8

It will clear the zombie device by itself after a 2am-3am maintenance it may take two of them.

Let it sit and stop trying to join that lock for now. When you try again, make sure the lock is close to the hub. Do an exclusion, then factory reset, then try join again.

9

I waited 3 days before trying again, but I'll give it a week to see if things clear out.

10

Upgraded the firmware to 2.1.1.114 and was finally able to pair the Yale lock (I have a Schlage that wasn't staying paired also, giving me problems). Before upgrading, the hub was just in a bad state for the Yale lock and would not clear it out (nor all the ghost devices created trying to pair the same Yale lock) after over a week of time.

Also, there is a big difference in pairing time between Hubitat and ST. I paired my locks with ST in a couple of seconds, while the Hubitat was still initializing until the lock timed out (lock beeped as if it failed to pair, but Hubitat finished doing its thing). This may be contributing to the unsuccessful pairing.

Also, the Zwave device exclusion is not reliable compared to ST. Using ST, I can remove all of my zwave devices within seconds, pair and then unpair. I could not remove the locks at all with Hubitat. The locks basically just timed out. Maybe @bravenel has some input? Thanks.