After a brief hiatus, I'm back to trying to get my Schlage FE599 to pair. I was able to get it to pair three times but it shows up as an unknown part number. Under the device, it says no commands available for this device.
Any thoughts?
Have you changed the device type in device settings? If it didn't initially detect that it was a lock, you will need to manually select the device type.
I think that may have done the trick. I use the drop-down and did not see Schlage but used generic Z-Wave lock. It seems like it might be working right now before I mount it back to the door. I may give it a couple of days before I install it after I learn the app and try adding it to my dashboard withSharp Tools. Once I get this one perfected, I still have a Kwikset deadbolt to tackle.
As someone on The Forum mentioned, Iris by Lowe's spoonfed us over the years. There's been a lot of Hoops to jump through with this new system. Albeit, there has been a lot of frustration.
1 Like
Read srwhite's post about using the SmartThings driver to configure the FE599 and then switching back to the generic Z-Wave driver. It dramatically improves performance of this lock.
I'm 61 years old and have no clue on how to change drivers. Would you happen to have a link for the driver I need and is there a video showing exactly how I accomplished loading the driver?
Thanks in advance.
Read through the complete thread for some background.
The driver code is at Schlage FE599 Lock Ignoring Keypad Events - #33 by srwhite
Installing custom drivers
https://docs.hubitat.com/index.php?title=How_to_Install_Custom_Drivers
Not sure what your age has to do with anything. There are likely lots of people here at least your age. I am 71.
3 Likes
You will want to go to the device page for the lock.
I can't fit the whole thing in a screenshot but it looks like this:
Right now your lock should be using the Generic Z-Wave Lock Driver - you will see that in the middle of the page - here's another screen shot:
The driver is in the field called Type*. If you put your cursor on that field you will find that a selection list will pop up. That's how you can select a driver (other than the one the system chose for you automagically when you joined the device to the system). Here's what that looks like:
I've got to go look at the other posts to see if they explain what is needed to create the alternate driver . . .
OK, I'm back. I don't see detailed instructions on creating the driver in srwhite's posting. It's really easy to do.
From srwhite's post, go to the show original link with the driver code (or just click on it here - I have copied it: Hubitat/ST-ZWave_Lock.groovy at master · shackrat/Hubitat · GitHub
Here is the only tricky part - you must copy all the code within the box starting with line 1 /**
through and including line 1868 }
- so you need to highlight all those lines, right click with your mouse, select COPY and click. This puts those 1868 lines of code into the paste buffer of your web browser.
Now open a tab to your Hubitat console and click on Drivers Code.
In the upper right corner, click on +New Driver. My screen shows a couple of drivers, yours will likely be blank.
When you click on +New Driver you will get a nice clean, nearly empty screen. It will have a line number 1 up in the upper left corner. Just put your cursor in the nice clean white area and ric right click - the cursor will position itself next to line number one. Select paste from the right click menu to drop the lines of code in from the paste buffer.
With any luck it should look something like this:
Click on the Save button in the upper right corner. You just created a driver!
So what did you just create? This is the SmartThings driver for the Schlage Z-Wave FE599 lock. We want this for one thing - we want to use the settings that this driver will send to the lock to configure the lock. Once we have accomplished that, we will switch back to the Generic Z-Wave Lock driver that you should be using now.
On your drivers page you should now see the driver named Z-Wave Lock in the list.
I will break here. If you get this far the next step is a piece of cake. Honestly, the hardest part is selecting all the lines of code and not including any extraneous stuff.
2 Likes
Eric, thank you for the very detailed info. One of my problems is that I only use my phone or a tablet at the house. Looks like I'm going to have to dig out the laptop which will make it easier to copy and paste and so forth. It might be a couple of days before I can get in and accomplish this. Once again thank you and everyone on the forum for all of your support. It's actually awesome to get a very quick reply.
I'll keep everyone posted in a few days to a week.
I agree, I don't think this is something to try on a small screen. I'm just a youngster (62) but I can't use a phone for much more than making a phone call. I prefer a real keyboard and a nice big monitor when I actually have to do real work.
The last step will be just to switch the drivers briefly. I can give you a step-by-step for that but first you need to have created that driver. So, I will give my fingers a rest while you work through that part.
I think the community knows enough that this will get fixed and the necessary changes will end up in one of the "official" Hubitat drivers - it just may take a while because (a) they have been really busy with Lowes Iris users who were forced to make an unscheduled migration and (b) they need to get one of the locks on loan for a while so they can watch the traffic and make sure they are using the optimal settings for best performance. Srwhite identified that the locks seemed to work better on SmartThings and came up with the Band Aid temporary fix using the two drivers. It works surprisingly well so I have been recommending it.
FYI..
Importing is a simpler solution to explain... go to the Github page and then click that RAW button you show. Grab the URL (copy) and then on Hubitat, click the Import button and replace (paste over) whatever URL is there with the new one. Click Import, yes, and then click Save
Don't have to worry about missing the 2nd half of the code 
as in: Paste this URL into the Import field and click Import:
https://raw.githubusercontent.com/shackrat/Hubitat/master/Drivers/ST-ZWave_Lock.groovy
Awesome! Thank you!
Some amazing developers are even saving you the click.... by including the Import URL as the first line of their code:
1 Like
FYI that my FE599 was behaving exactly as described here - I got it to pair and it was functional but for whatever reason it began to be randomly unresponsive to commands and consistently failed to provide any status updates or events to the hub sometime later. Repeated exclude and re-pair did nothing. Thankfully I found this thread! Switching briefly to the partially-ported ST driver and simply doing a configure() fixed everything.
I bought my FE599 at Lowes so I assume it's a pretty main-stream product so hopefully this is a priority to research and fix in the generic driver? What kind of help do the devs need from the community? Can I help to debug?
Some one in the community, and I apologize that I'm unable to keep track of whom, is sending me his example of this lock, once in hand I'll be able to see why are current driver isnt working correctly.
2 Likes
After digging out the laptop, I was able get the lock up and running. Lock code manager works as well as Sharp Tools.
I have a Kwikset dead bolt 910/912 next. Should I anticipate the same hoops to jump thru as the FE599?
Thanks again for everyone's help.
No, different hoops. Equally frustrating.
1 Like
Randy.
I'm trying to help a friend pair a scholar lock to his hubitat...but were over the phone and using face time so it gets a little frustrating1
Can you confirm if you enter the programming code then press schlag?
He is telling me that he can't enter a code unless he presses schlag 1st - then enters the code. He is also telling me that if he enters schlag, then the code, if he hits schlag again - he can't enter a 0
these are finicky enough without trying to troubleshoot vis FaceTime!
thanks
Mac
It's been so long I don't remember but here is what it says in the instructions I saved:
- Bridge must be put into enrollment mode before lock for successful enrollment/exclusion.
2 Likes
appreciate it will try thanks
