I have an old Schlage BE469 lock that does not register the unlock and lock command all of the time since upgrading the Z-wave board. I am running 5.3.1 firmware and UI. I think about buying the newer Z-wave plus version but the weirdness I see in the event log makes me think it will still have issues. In the logs below ZW002 is a GE motion switch which is near the door and ZW005 is an Aeotec Recessed Door Sensor 7 ZW187. You will notice when the unlock and lock commands are not logged neither is the open and close function of the door sensor. I would like to hear what other peoples thoughts are on this!

 

ZW002_308        ALARM     8         2020/12/22 20:32:29  System    5
ZW002_155        ST        On        2020/12/22 20:32:29  System    5
ZW002_1          ST        On        2020/12/22 20:32:29  System    5
ZW003_1          ST        Unlocked  2020/12/22 20:32:32  System    5
30 10 7D 6       ST        Off       2020/12/22 20:32:32  System    5
30 10 0 6        ST        Off       2020/12/22 20:32:32  System    5
ZW005_306        ALARM     22        2020/12/22 20:32:34  System    5
ZW005_184        ST        Open      2020/12/22 20:32:34  System    5
ZW005_160        ST        On        2020/12/22 20:32:34  System    5
ZW005_251        ST        255       2020/12/22 20:32:34  System    5
ZW005_306        ALARM     23        2020/12/22 20:32:38  System    5
ZW005_184        ST        Closed    2020/12/22 20:32:38  System    5
ZW005_160        ST        Off       2020/12/22 20:32:38  System    5
ZW005_251        ST        0         2020/12/22 20:32:38  System    5
ZW003_1          ST        Locked    2020/12/22 20:32:40  System    5
30 10 7D 6       ST        On        2020/12/22 20:32:41  System    5
30 10 0 6        ST        On        2020/12/22 20:32:41  System    5

ZW002_308        ALARM     8         2020/12/22 17:38:07  System    5
ZW002_155        ST        On        2020/12/22 17:38:07  System    5
ZW002_1          ST        On        2020/12/22 17:38:07  System    5
ZW005_160        ST        On        2020/12/22 17:38:16  System    5
ZW005_251        ST        255       2020/12/22 17:38:16  System    5
ZW005_160        ST        Off       2020/12/22 17:38:16  System    5
ZW005_251        ST        0         2020/12/22 17:38:16  System    5
ZW002_308        ALARM     0         2020/12/22 17:38:36  System    5
ZW002_155        ST        Off       2020/12/22 17:38:36  System    5
n002_5           GV2       2.5 minutes2020/12/22 17:39:06  System    5
ZW002_1          ST        Off       2020/12/22 17:39:18  System    5

 

Thanks

Tom

I am also having issues with 3 x Kwikset locks over the last week.  Everything else Zwave seems ok without communication errors just the locks....

Locks were rock solid before that.  Have not made any changes etc....

Is there a bug with the new 500 board?

 

1 hour ago, firetruk11 said:

I am also having issues with 3 x Kwikset locks over the last week.  Everything else Zwave seems ok without communication errors just the locks....

Locks were rock solid before that.  Have not made any changes etc....

Is there a bug with the new 500 board?

 

I no longer use kwikset locks so I cannot comment on that lock specifically. When it comes to the 500 board, Ive found it works great when the system is 500 devices vs older gen-though it does work with both. My experience with yale locks has been glitchy on 5.3 and atrocious with 5.3.1 so it wouldnt surprise me if the same held true with other brands. 

I have the BE469ZP lock and it works fine with the 500 chip, version 5.3.0 firmware installed.  

The only thing I wish it would do was have the ISY respond to the tamper alarm.  It creates a tamper alarm node in the UI, but that node never triggers anything when the tamper alarm goes off.

did you try to use the node in a scene or program?

1 hour ago, oberkc said:

did you try to use the node in a scene or program?

Yes I have a program to send me a notification if the tamper/intrusion alarm goes off.   The status of the alarm never changes.  You can hear the lock siren going off...

This is a long shot but, if you right click on the device there should be a synchronize call under one of the menu items. That might relate the association.

I guess it is comforting that others are having issues also but it looks like the older devices negatively affect other devices.

On 12/31/2020 at 11:40 AM, lilyoyo1 said:

I no longer use kwikset locks so I cannot comment on that lock specifically. When it comes to the 500 board, Ive found it works great when the system is 500 devices vs older gen-though it does work with both. My experience with yale locks has been glitchy on 5.3 and atrocious with 5.3.1 so it wouldnt surprise me if the same held true with other brands. 

So... I removed the 3 looks and re-added.  Then had an issue with my Siren 6 - no communication.  Reset it etc, then removed it.  Two days now without any issues with the locks.  Perhaps the siren6 was faulty/causing issues....  All other Z wave stuff are normal

Will see, took about 2 weeks after updating to the 500 board for the locks to have issues.