Jump to content

Schlage BE469ZP Options missing


BONeil

Recommended Posts

  • 3 weeks later...

I have the same problem. Just added a new BE469ZP, Firmware ver. 0.11.0 I'm running ISY on 5.3.3 I don't have Options showing for the new lock and also, what is most concerning, the status of the lock is showing "unknown". I can control the lock from ISY and I can also change the user password. But I cannot retrieve the status and also see the options to be able to change them. Is there a fix available ?

Link to comment
Share on other sites

1 hour ago, oper8 said:

I have the same problem. Just added a new BE469ZP, Firmware ver. 0.11.0 I'm running ISY on 5.3.3 I don't have Options showing for the new lock and also, what is most concerning, the status of the lock is showing "unknown". I can control the lock from ISY and I can also change the user password. But I cannot retrieve the status and also see the options to be able to change them. Is there a fix available ?

Does your UI match your firmware

Link to comment
Share on other sites

Yes, I have UI and F/W both showing "Insteon_UD994 v 5.3.3". Done more research into the issue and it seems it all about z-wave having communication issues. I have over 20 z-wave devices, including 2 Schlage locks, plus over two dozen Insteon devices all working together. Performance is 99% but with only these odd z-wave issues caused only by the battery powered devices. I just added a AEON repeater but did not see a significant improvement. I'm looking at better ways to heal the network, the current ISY version does not have the whole network healing feature as before. I'm also looking at more advanced ways to troubleshoot communication issues. I hope a newer ISY version might address this. I love ISY and want to continue to use it but moving more on the z-wave devices and retiring the old INSTEON items.

Link to comment
Share on other sites

More on this. Not only that "Options" are no longer available in the new 5.3.3 but there is something wrong in terms of communication. I have two locks fairly close to each other, one that was installed with the previous 5.0.16 version, showing Options and all and no comm. errors. The second lock was recently installed under 5.3.3, I'm missing "options" and showing some strange comm. errors when query. The lock works but it seems unreliable with these errors. I added the Aeotec gen 7 repeater and there is ZERO improvement. Is there any chance the 5.3.3 will be fixed or is there a way to go back to the older 5.0.16 firmware that was working better ? Here is the event viewer log with the errors:

Tue 04/13/2021 08:20:43 PM : [ZWAVE-TX        ] ...
Tue 04/13/2021 08:20:48 PM : [ZW-TX-FAILED] enc=Ok uid=36.0 cmd=0x62.02 DOOR_LOCK
Tue 04/13/2021 08:20:48 PM : [ZWAVE-TX-E      ] ZWAVE-WAIT Waiting for retry 1 of 2
Tue 04/13/2021 08:20:48 PM : [ZWAVE-TE        ] [62/02] CC=0x62 cmd=0x02 [] ACK,AUTO,EXPLORE To=0x24
Tue 04/13/2021 08:20:48 PM : [ZWAVE-TX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x24
Tue 04/13/2021 08:20:50 PM : [ZWAVE-RX ZW036_1] [98/80] Security Nonce Report - nonce=[7D51F33F450FF722] ACK,AUTO,EXPLORE From=0x24
Tue 04/13/2021 08:20:50 PM : [ZWAVE-RX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x24
Tue 04/13/2021 08:20:50 PM : [ZWAVE-TX        ] ...
Tue 04/13/2021 08:20:54 PM : [ZW-TX-FAILED] enc=Ok uid=36.0 cmd=0x62.02 DOOR_LOCK
Tue 04/13/2021 08:20:54 PM : [ZWAVE-TX-E      ] ZWAVE-WAIT Waiting for retry 2 of 2
Tue 04/13/2021 08:20:55 PM : [ZWAVE-TE        ] [62/02] CC=0x62 cmd=0x02 [] ACK,AUTO,EXPLORE To=0x24
Tue 04/13/2021 08:20:55 PM : [ZWAVE-TX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE To=0x24
Tue 04/13/2021 08:20:56 PM : [ZWAVE-RX ZW036_1] [98/80] Security Nonce Report - nonce=[AF5601DFC582273E] ACK,AUTO,EXPLORE From=0x24
Tue 04/13/2021 08:20:57 PM : [ZWAVE-RX ZW036_1] [98/40] Security Nonce Get ACK,AUTO,EXPLORE From=0x24

Link to comment
Share on other sites

Sorry Michael, I have to report that I opened a ticket indeed but got nowhere with it. The recommendation that came from your support was to go back to 5.0.16C I'm quite disappointed and I now regret upgrading to 5.3.3 Everything was working fine for me with 5.0.16C. And I don't know if going back to the older ISY firmware will not cause more trouble.... 

Link to comment
Share on other sites

10 minutes ago, oper8 said:

Sorry Michael, I have to report that I opened a ticket indeed but got nowhere with it. The recommendation that came from your support was to go back to 5.0.16C I'm quite disappointed and I now regret upgrading to 5.3.3 Everything was working fine for me with 5.0.16C. And I don't know if going back to the older ISY firmware will not cause more trouble.... 

Sounds like it's a programming issue that needs to be fixed in a future firmware update. Unfortunately not all issues can be solved via troubleshooting steps. In your case,  while it's not the answer you wanted it was the best answer given. 

The same happened to me with my yale locks. I had to go back to 5.0.16 due to issues with 5.3 and 5.3.2. This update seems to allow them to work properly (time will tell once i have time to test)

Link to comment
Share on other sites

Hi lilyoyo1, How did you go back to 5.0.16 ? I installed several new devices since 5.0.16 and my last backup on that version does not have them. Will I have to join them again ? I'm quite nervous about the downgrade, but I would very much want to go back to that version. I really don't like how the z-wave devices are showing with multiple nodes in 5.3.3, lots of things don't make sense, it's all super un-friendly and counter intuitive. 

Link to comment
Share on other sites

Hi lilyoyo1, How did you go back to 5.0.16 ? I installed several new devices since 5.0.16 and my last backup on that version does not have them. Will I have to join them again ? I'm quite nervous about the downgrade, but I would very much want to go back to that version. I really don't like how the z-wave devices are showing with multiple nodes in 5.3.3, lots of things don't make sense, it's all super un-friendly and counter intuitive. 

If you added zwave devices, wait for other advice as I’m less than a novice with them.

Otherwise,Restore your last 5.0.16C backup. Factory reset the devices you’ve added and ten add them again including any scene setup. You will need to recreate any new programs so copy them into a text document to make it easy to create them.
Link to comment
Share on other sites

I will rather wait. Maybe a new version will fix this. So far everything is working with the "crippled" lock, but working. I have at least a dozen new devices added since 5.0.16 and lots of new programs and scenes. It will be almost like rebuilding my entire network. Note for self: never jump in upgrading to bleeding edge new version until all the bugs are identified and fixed.

Link to comment
Share on other sites

  • 2 months later...

I have version 5.3.3 and there is still no options for Schlage Locks like there was in the older versions that had a nice simple screen to allow you to set the pin length and other behaviors.  Sure would like that back.

Link to comment
Share on other sites

I am having similar issues.

The option button is missing.

I have had to factory reset the lock several times to get it to connect.

The first time only the lock populated.  Several attempts later it added "Access Control Alarm", "Home Security Alarm", and "Intrusion Alarm"

Is there any additional documentation regarding Schlage and Configurations?

I also have a Nexia bridge, but cannot use both the ISY and Nexia.  The Nexia interface makes keeping track of user names, codes, etc much easier to manage.

 

Link to comment
Share on other sites

1 hour ago, rchorowitz said:

I am having similar issues.

The option button is missing.

I have had to factory reset the lock several times to get it to connect.

The first time only the lock populated.  Several attempts later it added "Access Control Alarm", "Home Security Alarm", and "Intrusion Alarm"

Is there any additional documentation regarding Schlage and Configurations?

I also have a Nexia bridge, but cannot use both the ISY and Nexia.  The Nexia interface makes keeping track of user names, codes, etc much easier to manage.

 

You can't have 2 controllers. You'll have to choose 1. Documentation for your lock can be found on schlage's website.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

×
×
  • Create New...