Schlage BE469NX Lock communication issue

[Tungsten]

I have 1 Schlage BE469NX lock [ZW 002], 1 Aeotec Z-Wave Smart Switch 6 (Gen 5) [ZW 004], and 1 Aeotec Z-Wave Siren (Gen 5) [ZW 005].

 

When I go to heal the zwave network on the ISY I'm getting the following error in the event viewer:

 

Fri 06/26/2015 12:17:11 PM : [ZWAVE-HEAL     2] Failed to Assign Routes to 'ZW 002 Schlage Door Lock'
Fri 06/26/2015 12:17:11 PM : [ZWAVE-DB        ] Unexpected NULL database for uid=3 0x03

 

This is after 2 retry errors:

 

Fri 06/26/2015 12:16:54 PM : [ZWAVE-TX        ] ZWAVE-WAIT Waiting for retry 1 of 2
Fri 06/26/2015 12:16:55 PM : [ZWAVE-TX ZW002_1] ...
Fri 06/26/2015 12:16:55 PM : [ZWAVE-RX        ] ACK
Fri 06/26/2015 12:16:55 PM : [ZWAVE-RX        ] [0104011301E8]
Fri 06/26/2015 12:16:55 PM : [ZWAVE-TX        ] ACK
Fri 06/26/2015 12:16:55 PM : [ZWAVE-RX        ] [010500137E0196]
Fri 06/26/2015 12:16:55 PM : [ZWAVE-TX        ] ACK
Fri 06/26/2015 12:17:00 PM : [ZWAVE-TX        ] ZWAVE-WAIT Waiting for retry 2 of 2

 

These errors have shown up every time I've done a heal network (about 10 times just today).  All the devices are pretty evenly distributed in the house (each about 10-15ft from each other).  I'm having sporadic communication with the lock and would really like to tighten this up. 

 

I've attached the complete log file for the heal network.   Any idea how to make this more reliable?

 

TIA, Kevin
 

ISY-Events-Log.v4.3.1__Fri 2015.06.26 12.20.15 PM.txt

[fryfrog]

Have you tried excluding and re-including things? I'd start w/ the lock since it is the one giving you trouble. I only have a few zwave devices, but when one acts up that is the first thing I try. You might also consider a few repeaters, remember that locks need repeaters that can do secure repeating, beaming or whatever it is called. I'm pretty sure the siren does it since I've seen that mentioned in a number of posts. Logically, a later generation switch would do it too right?

[Tungsten]

I've excluded and re-added the lock a couple times with the same issue and yes, I'm pretty sure that both devices I have should be repeaters for secure devices.  I can communicate with the lock but it's spotty (works about 70% of the time).  I'm not sure if the NULL database error (and the preceding retries errors) are normal.  If the repeaters are working as expected I don't see how there would be any failures given how close (proximity) everything is to each other.

[andyf0]

I had a NULL database error once, I think it was when doing a Synchronize Nodes which I think might have fixed the problem because I haven't seen it since.

[Michel Kohanim]

Hi Tungsten,

 

Those errors are pretty benign. i.e. ISY tried to get the database from memory, didn't exist, and read from a file.

 

Have you done a Heal Network?

 

With kind regards,

Michel

[Tungsten]

Michel, these errors show up every time I do a heal network (including the two retries) & im getting failure to communicate messages about 30% of the time.

[Michel Kohanim]

Hi Tungsten,

 

Thank you. Can you please upgrade to 4.3.8? We added a little more debugging. 

 

With kind regards,

Michel