Hubitat Z-Wave Exclusion not working

🛎️ Get Help
1

I've been trying to move back over to Hubitat from SmartThings.

I first went around the house with the Hubitat (and long power/network cable) in hand. I went to every device with the Hubitat in Z-Wave Exclude mode and went through the button presses, etc on the devices to exclude them. It turns out, they didn't exclude and I couldn't discover them in Hubitat!

I had to open the SmartThings app and go to the General Exclude there, then the Z-Wave devices excluded. By the way, the SmartThings General Exclude gives you feedback that at least something was excluded. I do not see this with Hubitat so I just keep hitting the Z-wave buttons,etc on the devices that they require to be put in include/exclude mode.

So it seems to me that the Hubitat generalized exclude mode doesn't work.

2

I include, exclude and force exclude quite a number of devices to both of the hubs I have for development and testing. I can tell you that general exclusion in Hubitat works. When I moved my devices over from st, I didn't even bother to exclude them. I just factory reset each one, then included them in hubitat.

1 Like
3

I put the Hubitat in its 30 seconds exclude mode and did all the things needed for each device to exclude (there's no feedback from Hubitat that it excluded anything). I had the Hubitat in hand so it was within a foot of each device. When I couldn't get Hubitat to discover a device, I went to SmartThings and put it in general exclude mode and with each devices exclude procedure, ST told me it removed an unknown device.. Generally afterwards the device was then discoverable in Hubitat but there were still several things it just wouldn't discover (mainly almost all of my Jasco Zwave switches)

4

I've seen this aswell. If I need to exclude something I use the ST app, even if it's not paired with ST, and I get an exclusion message. I never see anything with HE.

1 Like
5

Thats what I did as well ... except for a picky GE Wall Outlet that refused to pair until excluded ... but the other 2 I have worked like a charm ... I moved this one to my daughter's room as she's picky too :smile:

The GE Switches are (IIRC) are Jasco as well... most of mine worked, but the one above just refused until I tried excluding a bunch of times

1 Like
6

I also prefer to use ST for exclusion because it gives you an indication that something was excluded. No guesswork.

1 Like
7

that would be a good feature request for down the line. Get some kind of a successful exclusion message so you know if something is excluded. I just assumed the ST gives the message and not HE because the device currently existed in the ST hub so it can "see" that something is gone , whereas the HE has no knowledge of the device ever existing? I don't know, just throwing out some logic straws there.

1 Like
8

The exclusion process doesn't necessarily need to know the device's info to exclude it.

The HE notification exists but is far from ideal. If you open your logs while doing the exclusion, it will display a confirmation there. If the device is not being excluded from the HE database, it should say "excluded unknown device" or something similar. Otherwise it will display the device name along with the confirmation.

2 Likes
10

Thank god for this thread. I literally sat here for 30 minutes trying to get stupid Schlage BE469 paired (many many exclude/include cycles and factory resets). Finally grabbed my old disconnected ST hub, put it in exclude, the Lock immediately excluded, showed it was excluded (no interior LED flash on power connect), and then I got the lock included in HE.

Something is seemingly not right with the Exclude mode in HE. =/

11

Yup. can't seem to successfully remove any zwave device at the moment. I added a HomeSeer Zstick+ and I can't get it removed (I'm not sure if it's causing zwave mesh instability). =(

But it won't remove via normal exclude. =(

Just removed and re-added the schlage lock again. had to do it the exact same way. it wouldn't exclude successfully from HE (had to force remove), so I had to plugin ST hub, do exclude on it, it immediately excluded, then do an include in HE which got it paired, but it's non-responsive...

12

I just added an Aeon Zstick yesterday and later removed it. The software I was using had a remove command and I did an Exclude in HE. After the exclude process had been active for a period of time, HE gave me the option to force remove, which I selected.

13

Force remove isn't the same as remove. Force remove leaves ghost/empty devices in your z-wave database, and should be avoided when possible. A few ghost items usually don't mess anything up, but a lot definitely can.

Also, make sure you do a zwave repair any time you remove a repeating z-wave device to update the route tables.

14

Sounds odd, but if you do a Hub shutdown (not reboot) and unplug the power after red light for 30 seconds, then reboot the hub, I had much better luck getting my Schlage locks to exclude.

15

That's typically how you force a rebuild of the Zigbee routing.

1 Like
16

cries I can't get this damn BE469 working again. It's paired. It thinks it's paired. HE thinks it's paired, but it won't respond at all, doesn't update to physical interaction, etc.

Got an email into support, but given others having issues with these locks, I wouldn't be surprised if it's just confirmation stuff isn't working.

17

Do the logs show any activity when you hit "Configure" in the Device Settings?

18

oddly, yes. So... it seems like Reliable Locks may be causing some issue. I unpaired the one I had for the front door from it, and the lock started responding...

Though, only briefly, it's back not responding again....

19

You do know you have to have the hub literally beside EACH lock when pairing, right?

20

Did it pair securely?

image
image.png794×174 4.74 KB

21

It did. Interesting your says "Schlage".

deviceType: 25409
zwaveSecurePairingComplete: true
inClusters: 0x22,0x72,0x7A,0x98,0x86
deviceId: 20548
manufacturer: 59