OK, just checking. Without the zwaveSecurePairing it just sits there - won't do a thing.
Mine is an FE599 but I think they are very similar.
1 Like
Have a feeling my zwave mesh is just flooded with commands at the moment. going to give it a few...
Have you tried srwhite's hack with the driver? I have no way of knowing for sure, as he did it for the FE599, but it may also work on the BE369. I think they are very similar. My lock has worked so much better since I did that. Of course, you have to get it paired first . . .
Same clusters . . .
Yes and all 3 of mine all work fine after I spent an entire day re-pairing/configuring, and nailed down the process that seemed to actually work, which I posted yesterday on the Schlage problems thread.
In case you want to try it and I'm not around, here's a link to the driver swap described by srwhite:
have a link to srwhite's work?
It's not turning up... but I'm also flustered and may not be patient enough to look too hard.
This?
That looks like it, yes. The idea is, once the lock is connected, switch to this driver and hit Configure on the device page. This will send the initialization parameters to the lock (using the ST parameters), then switch the driver back (and don't hit Configure). Your lock will be configured the way the ST driver configured it. There seems to be some value (or values) that are different and make for different (better) performance. You have to install the driver as it is not one of the built-in drivers but that's a pretty easy process and well-documented here.
1 Like
don't want to take over this thread. let's move this over to schlage thread...
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
