Jump to content

Recommended Posts

Posted (edited)

I just replaced my BE469 locks with the Zwave Plus models from Schlage. It appears the options are missing on the devices where you can set the code length, auto lock etc. I installed two and they both show up the same way. Is this is expected, and are the settings now manipulated through the binary config parameters?

I found this parameter guide for the BE469 - https://www.schlage.com/content/dam/sch-us/documents/pdf/installation-manuals/24352403.pdf

I set param #10 to a value of 7 - (7 digit user codes) - and set my user code to a seven digit number and it doesn't seem to take effect. I'm either entering the parameter wrong or there is a different set of parameters for this model, which I cannot seem to find. 

Any direction is appreciated!

Edited by broneil
Posted

From your admin console click on "Help" then click on "About" and make sure the "UI" and "Firmware" versions are the same.

Posted (edited)

This is what I get from event viewer when I attempt to write Parameter 10 value 7

Sun 09/27/2020 10:12:22 AM : [ZWAVE-TE        ] [70/04] CC=0x70 cmd=0x04 [0A0107] ACK,AUTO,EXPLORE To=0x1E

Sun 09/27/2020 10:12:22 AM : [ZWAVE-TX ZW030_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x1E

Sun 09/27/2020 10:12:23 AM : [ZWAVE-RX ZW030_1] [98/80] Security Nonce Report - nonce=[7FE7A86EBB92E93E] ACK,AUTO,EXPLORE From=0x1E

 

And I can write and verify 4 digit user codes successfully. After which I deleted all the user codes, tried the parameter update again, assigned user 1 a 7 digit code and the lock still won't accept anything past 4 digits on the keypad.

Edited by broneil
Posted

Do you not have an "Options" button to the left of the "Users" button on the admin console?

Posted

I do not. And I have two BE469ZP locks added at different times, neither has the options button like the BE469 did. I excluded and then re-added one and I still did not get the options button. 

lock.jpg

Posted

I have a newer schlage BE469ZP and V 5.016 on my ISY.  Mine is working fine with the options and the ability to change the code length etc.

Sounds like it could be an issue or something they changed with 5.20.0 ?

Posted (edited)

When you are setting the parameters, it looks like the admin console is using decimal and the Schlage manual is in HEX.  0x10 would be 16 in decimal.  When you are in the "Parameter Number" field, you can type in 0x10 and it will auto convert to 16.

Edited by DaveF
Posted
15 hours ago, broneil said:

Steps to set parameter = Enter 10 in the parameter number box, Enter 7 in the Value box, hit Set Configuration.

Have you tried pressing the "Write Changes" button?

  • Like 1
Posted (edited)

I did a third unenroll\enroll for the lock one last time to make sure I'm not missing anything, below is the output of the lock.

While it seems to be responding to config changes, lock\unlock commands and battery level, it is not reporting user numbers when the pin is entered. (and I still don't get the options UI) The enrollment process also looks like something is off with lots of failed lines. This process was done with the lock less than a foot away from an unobstructed ISY. 

Mon 09/28/2020 02:13:45 PM : Listening for Z-Wave devices to add to the network

Mon 09/28/2020 02:13:48 PM : Z-Wave device detected, retrieving info 2

Mon 09/28/2020 02:13:48 PM : Z-Wave device detected, retrieving info 3

Mon 09/28/2020 02:13:56 PM : Z-Wave device detected, retrieving info 5

Mon 09/28/2020 02:13:56 PM : Adding Z-Wave devices stopped

Mon 09/28/2020 02:13:57 PM : Z-Wave device detected, retrieving info 6

Mon 09/28/2020 02:13:57 PM : Exchanging data with secure Z-Wave device 35 of type 4.64.3

Mon 09/28/2020 02:13:57 PM : Adding secure Z-Wave device

Mon 09/28/2020 02:14:09 PM : Adding ISY node(s) for new Z-Wave device 35 type 4.64.3

Mon 09/28/2020 02:14:18 PM : Adding additional nodes for new Z-Wave device 35

Mon 09/28/2020 02:14:59 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:15:06 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:15:13 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:15:26 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:15:33 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:15:41 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:15:48 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.01 NOTIFICATION

Mon 09/28/2020 02:15:54 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.01 NOTIFICATION

Mon 09/28/2020 02:16:01 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.01 NOTIFICATION

Mon 09/28/2020 02:16:08 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:16:15 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:16:23 PM : [ZW-TX-FAILED] enc=Ok uid=35.0 cmd=0x71.04 NOTIFICATION

Mon 09/28/2020 02:16:51 PM : [     ZW035_1]   BATLVL 100 (uom=51 prec=0)

 

Edited by broneil
  • 2 weeks later...
Posted

I just upgraded to the 5.3.0 Release from 5.0.16 and have noticed the same change (or loss in GUI)

I have FOUR Schlage BE469ZP locks and All made this change.

I too see quite a few "[ZW-TX-FAILED]" in the detailed event viewer during Queries and Writes.

I did not move my z-wave network to a different controller before upgrading.

I am also not a power user in that while I may have broad knowledge, my depth is still in the kiddie pool level. ut I do have 399  device nodes, and too many scenes and programs for one with my experience 

/Bill

  • 2 weeks later...
Posted

Same here I bought a new ISY with the new Z-Wave module and 5.3 installed and my z-wave Schlage locks no longer work.  Hooked up my old ISY with the old modules re-added all the z-wave devices and re-synced the networks and it works great.  There is a issue with firmware 5.2 and above I guess.   So I removed all my z-wave devices factory reset all of them and tried the new ISY again and still same results.  I even put the ISY much closer to the door and had the same results.  I did the same process to my old device and it works great.

For now I would stay away from 5.2 and 5.3.

 

-JP

Posted
2 hours ago, Michel Kohanim said:

@JPaul,

I am so very sorry for the trouble. This is being fixed as we speak.

With kind regards,
Michel

I never use them for yale but I looked at mi e and it's missing too

Posted (edited)
11 hours ago, Michel Kohanim said:

@JPaul,

I am so very sorry for the trouble. This is being fixed as we speak.

With kind regards,
Michel

NP I figured you guys would.  Still an awesome product.  No complaints here.

Edited by JPaul
  • Like 1
  • 2 weeks later...
Posted
On 10/22/2020 at 8:49 AM, Michel Kohanim said:

@JPaul,

I am so very sorry for the trouble. This is being fixed as we speak.

With kind regards,
Michel

Awesome to hear Mike, I've got the same problems with my Schlage locks on 5.2/3, rebuilt the z-wave network today and now 2 of the 3 locks added but 1 of them came down with 6 entries while the other one only added 1 like it used to in the past, they also seem to be trying to write updates but keeps failing that too.

image.png.9bc8337bbb026f940f1bb949f308863c.png

Posted
2 hours ago, wingman1487 said:

Awesome to hear Mike, I've got the same problems with my Schlage locks on 5.2/3, rebuilt the z-wave network today and now 2 of the 3 locks added but 1 of them came down with 6 entries while the other one only added 1 like it used to in the past, they also seem to be trying to write updates but keeps failing that too.

image.png.9bc8337bbb026f940f1bb949f308863c.png

After rebuilding my 5.3.0 Z-Wave Network, all four of my BE469ZPs have the six nodes and no options.  But working reliably!

/Bill

Guest
This topic is now closed to further replies.

×
×
  • Create New...