Schlage BE469 Z-Wave Locks Started Having Z-Wave Errors

Been running 2 BE469 Z-Wave Locks for several months now, with very few issues.

I am on Indigo Server 7.1.1 and Aeotec Z-Stick Gen 5.

This morning, both locks were not triggering some lights, so looking at the logs, I see some errors show below. Other Z-Wave devices are fine, but they are not encrypted.

To troubleshoot I have tried:

Rebooting the Mac
Moved the Z-Stick to another USB Slot and reselected the interface
Pulling Battery power to the lock and plugging it back in
Running "Optimize Z-Wave Network"

I would like to avoid excluding/including it from the network, as last time I remember I had to setup a lot of stuff again, as I have these devices all over the place in triggers, action groups, custom control pages, etc.

But if that's the next step, I will do it.

Thanks,

Chris

Unlocking/Locking one of the BE469s:

Code: Select all

 
   Z-Wave Error                    RCVD encryptedPacket: unexpected sequence byte 99
   Z-Wave Error                    RCVD encryptedPacket:  full raw packet 01 23 00 04 00 02 1D 98 81 2F 16 4B D3 97 15 2F 32 B4 DF BE AF 0B 1C C0 1D A1 19 24 5C 6C 73 FA 39 71 46 73 08
   Z-Wave Error                    RCVD encryptedPacket: encrypted packet B4 DF BE AF 0B 1C C0 1D A1 19
   Z-Wave Error                    RCVD encryptedPacket: decrypted packet 99 81 2E 6C 52 76 3D 54 0B D6
   Z-Wave Error                    encrypted command received from node ID 002 has invalid CBC-MAC value (ignoring)
   Z-Wave Error                    RCVD encryptedPacket: unexpected sequence byte 23
   Z-Wave Error                    RCVD encryptedPacket:  full raw packet 01 23 00 04 00 02 1D 98 81 62 CD 93 BF 90 F8 7B 36 AD 8B 90 19 C3 25 E7 13 43 A9 C7 DF F0 58 02 69 D1 A0 EE 6B
   Z-Wave Error                    RCVD encryptedPacket: encrypted packet AD 8B 90 19 C3 25 E7 13 43 A9
   Z-Wave Error                    RCVD encryptedPacket: decrypted packet 23 EB DC E7 E9 01 EF 66 1C 28
   Z-Wave Error                    encrypted command received from node ID 002 has invalid CBC-MAC value (ignoring)


Also, when I try to send a status request, I get nothing in the logs but this:

Code: Select all

Z-Wave  sent "Schlage Front Door" status request

However, when I try to Sync again, I actually get something in the logs, but followed by "the device may be asleep":

Code: Select all

   Z-Wave                          Syncing - started for "Schlage Front Door"
   Z-Wave                          Syncing - retrieved module neighbors list: 12
   Z-Wave                          Syncing - assigning return route to "002 - Schlage Front Door"
   Z-Wave                          Syncing - assigned return route
   Z-Wave                          Syncing - retrieved manufacture and model names: Schlage - 003B, Door Lock (BE369/468/469) - 63415044
   Z-Wave                          Syncing - retrieved protocol version 3.42, app version 113.22
   Z-Wave                          Syncing - retrieved class hierarchy: Routing Slave : Entry Control : Keypad Door Lock (04 : 40 : 03, base 62)
   Z-Wave                          Syncing - retrieved command classes: 20v1 22v1 62v1 63v1 86v1 98v1 7Av1 72v1
   Z-Wave                          Syncing - retrieved encrypt commands: 80 20 62 63 85 70 71 5D
   Z-Wave                          Syncing - retrieved capabilities: routing, battery, beaming, security, frequentWaking


Code: Select all

  Z-Wave Error                    Syncing - failed
  Z-Wave Error                    Timeout waiting for "002 - Schlage Front Door". Module might be asleep, or is unreachable.


[matt (support)]

Hi Chris,

I would like to avoid excluding/including it from the network, as last time I remember I had to setup a lot of stuff again, as I have these devices all over the place in triggers, action groups, custom control pages, etc.

Actually try the exclude/re-include (with encryption) again, but do not delete the device. After it has been re-included just re-sync the existing device with the new node ID selected. As long as the device isn't deleted you won't have to redo your Triggers, Action Groups, etc.

That did the trick, I’m going to document this for the future.

Any clue why both locks would start acting up at the same time?

Is it possible the Z-Stick is the culprit?

[matt (support)]

I'm not sure what would have caused that.