Yet Another Schlage FE599 Thread :)

🛎️ Get Help Devices
1

New to Hubitat, coming from Vera Plus. I have read all the other FE599 related threads here. I have a Aoetec Extender next to the lock which was required to get Vera to interact with it reliably.

Migrated 43 Devices from Vera to Hubitat. Mostly straight forward, possible some minor issues with incorrect drivers for some Aeotec Repeater Dimmers and Leviton Scene controllers that I'll come back to later, once I have everything included. However the one device that won't include successfully is my FE599. I'm on an HE-C7 with the latest firmware (2.3.2.140)

After several hours of reading the other threads on this topic and including / excluding and factory resetting the FE5999, this is where I am at.

With the Hub 12" from the lock, and brand new batteries in the lock.

Put hubitate into Z-Wave Exclude Mode
Key in the Lock Program Key. Schlage Button turns 'orange'. Press 'Schalge' button followed by '0'
Schlage Button blinks Green and then stop
Exclude mode reports "Unknown Z-Wave device Excluded"

Logs show

[sys:1](http://192.168.1.133/logs#sys1)2022-07-19 05:44:17.607 pm Unknown Z-Wave device excluded.

[sys:1](http://192.168.1.133/logs#sys1)2022-07-19 05:44:04.394 pm Z-Wave Inclusion timed out, status:7

[sys:1](http://192.168.1.133/logs#sys1)2022-07-19 05:44:04.352 pm Z-Wave Exclude Started for 30 Seconds

[sys:1](http://192.168.1.133/logs#sys1)2022-07-19 05:44:04.296 pm Z-Wave Discovery Stopped

Select Generic ZWave Lock -> Begin Inclusion
Enter program code on lock,
Wait for 3 orange blinks on schlage button,
Press Schlage button. Button blinks orange and then blicks green then turns off
Inclusiion reports "Inclduding Unkown Z-Wave device" - Sorry didn't capture exact message.
and Timer continues running

Logs show

[sys:1](http://192.168.1.133/logs#sys1)2022-07-19 05:46:26.363 pm Z-Wave Discovery Running

Z-Wave Logs show

[8](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:39.738 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:39.638 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:35.424 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:35.224 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:31.118 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:31.018 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:26.511 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:26.411 seqNo: 37, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-78 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:26.211 seqNo: 37, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:26.110 seqNo: 36, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-78 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:26.010 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-78 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:25.810 seqNo: 35, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:25.609 seqNo: 35, routeChanged: true, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [-78 dBm, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[49](http://192.168.1.133/hub/zwaveLogs#zwaveRx49)2022-07-19 17:54:24.508 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: Unknown

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:24.407 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:20.087 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:19.987 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:15.780 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:15.580 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:11.368 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:10.967 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:10.667 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:10.353 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[48](http://192.168.1.133/hub/zwaveLogs#zwaveRx48)2022-07-19 17:54:09.852 seqNo: 35, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:09.752 seqNo: 27, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs, rssi: [N/A, N/A, N/A, N/A, N/A], Ack channel: 1, Transmit channel: 1

[47](http://192.168.1.133/hub/zwaveLogs#zwaveRx47)2022-07-19 17:54:05.444 seqNo: 27, routeChanged: false, transmissionTime: 1ms, repeaters: None, speed: 40 kbs

Eventually the Inclusion process timeouts and reports inclusion failed.

If I look under settings -> zwave details
I have the following entry

0x49 (073)	PER: , RTT Avg: ms, LWR RSSI:
Neighbors: , Route Changes:	OK [REFRESH] [REPAIR]
SPECIFIC_TYPE_SECURE_KEYPAD_DOOR_LOCK
[DISCOVER] S0	01 -> 49 40kbps

Which not appear to be linked to any device unders 'Devices'

Does the log info help identify why the inclusion is failing.

Is there any back door to selecting the (disgraced) 599 Driver.

FWIW I also have a BE469 which I included in the same way that was picked up perfectly and identifed correctly first time

2

That lock has always been problematic from what I've seen. Anything with firmware below 7.10 is a crapshoot. Then depending on the generation of z-wave chip combined, it ends up being a paperweight.

1 Like
3

AFAIK, no one has successfully included a FE599 with a C-7. Although they do work with the older 500-series C-5.

I don't know if locks can be included using a secondary controller, but if they can, it would be worth a shot attempting that as a method to include it.

@bcopeland, @JasonJoel - can locks be included using a secondary controller?

1 Like
4

How do I get the lock firmware version ?

6

Assuming you meant the existing version, it is on a sticker on the backplate of the lock that faces the door. So you'll have to take the lock off the door.

1 Like
7

I was going to chime in and say I had no issues pairing mine and it's pretty old, but it is connected to a C5 not a C7.

1 Like
8

Understand I can't update the firmware. Was wondering how to check the firmware version. Do I need to repair it with Vera ?

9

I no longer have my FE599, but according to zwavealliance, it doesn't even support S0, which may be why it craps out while pairing to the C-7.

Can you check if your lock is paired with S0 security to your C-5?

1 Like
10

Where do you check that on a C5. I tells you on the C7, but all I see on the C5 is a parameter zwaveSecurePairingComplete is true.

1 Like
11

Good question. I thought that information is on the device page. But I guess it isn't. I'm only using my C-5 for zigbee devices .....

1 Like
12

Maybe the in-clusters will include command class 0x98 or 0x9F?

1 Like
13

I see it on the sticker for the BE469NX, but not on the sticker for the FE599

14

Is there a way to disable S0 (at least temporarily) to see if that get's it paired.

15

This piece of device data is also there on the device detail page on the C-5 (and earlier), and since it's all that model supports, if it's there, you know it's S0. :slight_smile:

2 Likes
16

Don't think so - no.

1 Like
17

Assuming I could find a previous generation hub (C5 ?) and could pair the lock with that hub, would I be able to use the hub-link feature to manage the hub as if it were attached to the C7 ?

18

Yes that is that is what I do, using hub mesh.

I have my devices split across three hubs, two C5s and a C7 on each end of the house. One of the C5s is in my detached shop. My 4th hub has all my rules which is a C7.

I mainly split my hubs to each end of the house because of my Schlage locks. I have several of the older BE469s and with one hub the locks on the other end of the house were constantly disconnecting.

1 Like
19

My post should have read all I see on the C5 is zwaveSecurePairingComplete is true. So I figured it was in S0 because I know my old Iris GDO has to pair in S0 and that is all it shows on my C5 as well.

1 Like
20

I do this too. My old C-4 hub is on the wall next to the door with the FE599 in my workshop. I use Hub Mesh to "link" it to the other two (C-7) hubs. It works well. I'll keep running it this way until it dies . . .

1 Like
21

I see one C5 listed on E-Bay. Are they difficult to find ?