I am at my wits end with getting a Schlage lock added

Configuration Z-Wave
1

Setup: Unraid running Home Assistant Docker; Aeotec Z-Stick Gen5

I bought a Schalge BE469 back in January and spent a few hours trying to get it added to Home Assistant. At some point, I got it working as I was trying things over and over again and wasn’t sure what ultimately ended up working. At the time, it worked fine once it was added. I’ve only got this one device at the moment in HA.

Yesterday I noticed that the lock was offline and looks like it had been for some time (I don’t use HA a ton right now). I checked the lock and batteries are fine and everything seems to be working on it.

So I’ve spent the last 5 hours scouring this forum, reddit and whatever else I can find trying different solutions. I’ve tried using the button on the stick to add and remove the node, using HA to add and remove the node, used two different Zwave PC controller softwares to no avail. I can get it to kind of work, but it shows up as just a generic lock device where as before, it showed up as “Schlage BE469…”.

It shouldn’t be this hard to get this to work. I’ve completely wiped the docker container and started over, changed my network key, etc.

Here is the OZW log from the first time it successfully added the lock in HA. It seems to have worked, but then near the bottom it seems to get unexpected responses from the node.

2020-04-22 17:41:26.517 Detail, Queuing (Controller) Add Device
2020-04-22 17:41:26.517 Info, Add Device
2020-04-22 17:41:26.517 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2020-04-22 17:41:26.518 Detail, Notification: ControllerCommand - Starting
2020-04-22 17:41:26.518 Detail,
2020-04-22 17:41:26.518 Info, contrlr, Sending (Command) message (Callback ID=0x0a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2020-04-22 17:41:26.520 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x01, 0x00, 0x00, 0xb9
2020-04-22 17:41:26.521 Detail,
2020-04-22 17:41:26.521 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-22 17:41:26.521 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2020-04-22 17:41:26.521 Detail, Node001,   Expected callbackId was received
2020-04-22 17:41:26.521 Detail, Node001,   Expected reply was received
2020-04-22 17:41:26.521 Detail, Node001,   Message transaction complete
2020-04-22 17:41:26.521 Detail,
2020-04-22 17:41:26.521 Detail, contrlr, Removing current message
2020-04-22 17:41:26.521 Detail, Notification: ControllerCommand - Waiting
2020-04-22 17:41:26.521 Info, WriteNextMsg Controller nothing to do
2020-04-22 17:41:48.582 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x02, 0x00, 0x00, 0xba
2020-04-22 17:41:48.582 Detail,
2020-04-22 17:41:48.582 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-22 17:41:48.582 Info, ADD_NODE_STATUS_NODE_FOUND
2020-04-22 17:41:48.582 Detail, Notification: ControllerCommand - InProgress
2020-04-22 17:41:48.745 Detail,   Received: 0x01, 0x11, 0x00, 0x4a, 0x0a, 0x03, 0x03, 0x0a, 0x04, 0x40, 0x03, 0x5e, 0x98, 0x9f, 0x55, 0x6c, 0x8a, 0x22, 0x2b
2020-04-22 17:41:48.745 Detail,
2020-04-22 17:41:48.745 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-22 17:41:48.745 Info, ADD_NODE_STATUS_ADDING_SLAVE
2020-04-22 17:41:48.745 Info, Adding node ID 3 - Secure
2020-04-22 17:41:48.746 Detail, Notification: ControllerCommand - InProgress
2020-04-22 17:41:49.137 Detail,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x05, 0x03, 0x00, 0xbe
2020-04-22 17:41:49.137 Detail,
2020-04-22 17:41:49.137 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-22 17:41:49.137 Info, ADD_NODE_STATUS_PROTOCOL_DONE
2020-04-22 17:41:49.137 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-04-22 17:41:49.137 Detail, Notification: ControllerCommand - InProgress
2020-04-22 17:41:49.137 Detail,
2020-04-22 17:41:49.137 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-04-22 17:41:49.189 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x06, 0x03, 0x00, 0xbd
2020-04-22 17:41:49.189 Detail,
2020-04-22 17:41:49.189 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-04-22 17:41:49.190 Info, contrlr, ADD_NODE_STATUS_DONE
2020-04-22 17:41:49.191 Info, Node003,   Basic device class    (0x04) - Routing Slave
2020-04-22 17:41:49.191 Info, Node003,   Generic device Class  (0x40) - Entry Control
2020-04-22 17:41:49.191 Info, Node003,   Specific device class (0x03) - Secure Keypad Door Lock
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_DOOR_LOCK
2020-04-22 17:41:49.191 Info, Node003,   Mandatory Command Classes for Node 3:
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_BASIC
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_DOOR_LOCK
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_USER_CODE
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_MANUFACTURER_SPECIFIC
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_VERSION
2020-04-22 17:41:49.191 Info, Node003,     COMMAND_CLASS_SECURITY
2020-04-22 17:41:49.191 Info, Node003,   Mandatory Command Classes controlled by Node 3:
2020-04-22 17:41:49.191 Info, Node003,     None
2020-04-22 17:41:49.191 Detail, Node003, Queuing (Security) SecurityCmd_SchemeGet (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x98, 0x04, 0x00, 0x25, 0x0b, 0x54
2020-04-22 17:41:49.191 Info, Node003,   Optional command classes for node 3:
2020-04-22 17:41:49.192 Info, Node003,     COMMAND_CLASS_ZWAVEPLUS_INFO
2020-04-22 17:41:49.192 Info, Node003,     COMMAND_CLASS_SECURITY (Existing)
2020-04-22 17:41:49.192 Info, Node003,   CommandClass 0x9f - NOT REQUIRED
2020-04-22 17:41:49.192 Info, Node003,   CommandClass 0x55 - NOT REQUIRED
2020-04-22 17:41:49.192 Info, Node003,   CommandClass 0x6c - NOT REQUIRED
2020-04-22 17:41:49.192 Info, Node003,   CommandClass 0x8a - NOT REQUIRED
2020-04-22 17:41:49.192 Info, Node003,     COMMAND_CLASS_APPLICATION_STATUS
2020-04-22 17:41:49.192 Detail, Node003, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2020-04-22 17:41:49.192 Detail, Node003, QueryStage_ProtocolInfo
2020-04-22 17:41:49.192 Detail, Node003, Queuing (Query) Get Node Protocol Info (Node=3): 0x01, 0x04, 0x00, 0x41, 0x03, 0xb9
2020-04-22 17:41:49.192 Detail, Node003, Queuing (Query) Query Stage Complete (ProtocolInfo)
2020-04-22 17:41:49.192 Info, Node003, Initializing Node. New Node: true (true)
2020-04-22 17:41:49.192 Detail, Node006,   Expected reply was received
2020-04-22 17:41:49.192 Detail, Node006,   Message transaction complete
2020-04-22 17:41:49.192 Detail,
2020-04-22 17:41:49.192 Detail, contrlr, Removing current message
2020-04-22 17:41:49.192 Detail, Node003, Notification: NodeAdded
2020-04-22 17:41:49.192 Detail, Node003, Notification: NodeProtocolInfo
2020-04-22 17:41:49.193 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.193 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.193 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.193 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.194 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.195 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.195 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.195 Detail, Node003, Notification: ValueAdded
2020-04-22 17:41:49.195 Detail, Notification: ControllerCommand - Completed
2020-04-22 17:41:49.195 Detail,
2020-04-22 17:41:49.195 Info, Node003, Sending (Security) message (Callback ID=0x0b, Expected Reply=0x04) - SecurityCmd_SchemeGet (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x98, 0x04, 0x00, 0x25, 0x0b, 0x54
2020-04-22 17:41:49.206 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:41:49.206 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:41:50.354 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x0b, 0x00, 0x00, 0x73, 0x93
2020-04-22 17:41:50.354 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x0b received (expected 0x0b)
2020-04-22 17:41:50.354 Info, Node003, Request RTT 1158 Average Request RTT 1158
2020-04-22 17:41:50.354 Detail,   Expected callbackId was received
2020-04-22 17:41:50.372 Detail, Node003,   Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x98, 0x05, 0x00, 0x6f
2020-04-22 17:41:50.372 Detail,
2020-04-22 17:41:50.372 Info, Node003, Response RTT 1176 Average Response RTT 1176
2020-04-22 17:41:50.372 Info, Node003, Received SecurityCmd_SchemeReport from node 3: 0
2020-04-22 17:41:50.372 Info, Node003,     Security scheme agreed.
2020-04-22 17:41:50.372 Detail, Node003, Queuing (Security) SecurityCmd_NetworkKeySet (Node=3): 0x01, 0x19, 0x00, 0x13, 0x03, 0x12, 0x98, 0x06, 0x02, 0x6f, 0x77, 0xe3, 0xbf, 0x43, 0xd7, 0x57, 0xf4, 0x99, 0x95, 0x71, 0x17, 0x99, 0x56, 0xcf, 0x25, 0x0c, 0x48
2020-04-22 17:41:50.372 Detail, Node003,   Expected reply and command class was received
2020-04-22 17:41:50.373 Detail, Node003,   Message transaction complete
2020-04-22 17:41:50.373 Detail,
2020-04-22 17:41:50.373 Detail, Node003, Removing current message
2020-04-22 17:41:50.373 Detail,
2020-04-22 17:41:50.373 Info, Node003, Processing (Security) Nonce Request message (Callback ID=0x0c, Expected Reply=0x04)
2020-04-22 17:41:50.373 Info, Node003, Sending (Security) message (Callback ID=0x0c, Expected Reply=0x04) - Nonce_Get(SecurityCmd_NetworkKeySet) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2020-04-22 17:41:50.380 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:41:50.380 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:41:50.402 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x00, 0x00, 0x02, 0xeb
2020-04-22 17:41:50.402 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2020-04-22 17:41:50.402 Info, Node003, Request RTT 29 Average Request RTT 593
2020-04-22 17:41:50.515 Detail, Node003,   Received: 0x01, 0x10, 0x00, 0x04, 0x00, 0x03, 0x0a, 0x98, 0x80, 0x28, 0xb6, 0x2a, 0x95, 0xf8, 0xdf, 0x52, 0x6d, 0xc3
2020-04-22 17:41:50.515 Info, Node003, Received SecurityCmd_NonceReport from node 3
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.515 Info, Node003, Sending (Security) message (Callback ID=0x0d, Expected Reply=0x04) - SecurityCmd_NetworkKeySet (Node=3): 0x01, 0x19, 0x00, 0x13, 0x03, 0x12, 0x98, 0x06, 0x02, 0x6f, 0x77, 0xe3, 0xbf, 0x43, 0xd7, 0x57, 0xf4, 0x99, 0x95, 0x71, 0x17, 0x99, 0x56, 0xcf, 0x25, 0x0d, 0x49
2020-04-22 17:41:50.527 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:41:50.527 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:41:50.555 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x0d, 0x00, 0x00, 0x04, 0xe2
2020-04-22 17:41:50.555 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x0d received (expected 0x0d)
2020-04-22 17:41:50.555 Info, Node003, Request RTT 182 Average Request RTT 387
2020-04-22 17:41:50.555 Detail,   Expected callbackId was received
2020-04-22 17:41:50.581 Detail, Node003,   Received: 0x01, 0x08, 0x00, 0x04, 0x00, 0x03, 0x02, 0x98, 0x40, 0x2a
2020-04-22 17:41:50.581 Info, Node003, Received SecurityCmd_NonceGet from node 3
2020-04-22 17:41:50.581 Info, NONCES: 0x50, 0xab, 0x6c, 0x88, 0xb4, 0x70, 0xa8, 0xfd
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, NONCES: 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
2020-04-22 17:41:50.581 Info, Node003, Sending (Security) message (Callback ID=0x01, Expected Reply=0x04) - Nonce_Report - 0x01, 0x11, 0x00, 0x13, 0x03, 0x0a, 0x98, 0x80, 0x50, 0xab, 0x6c, 0x88, 0xb4, 0x70, 0xa8, 0xfd, 0x05, 0x01, 0x66:
2020-04-22 17:41:50.589 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:41:50.589 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:41:50.612 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x01, 0x00, 0x00, 0x03, 0xe9
2020-04-22 17:41:50.612 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x01 received (expected 0x01)
2020-04-22 17:41:50.612 Info, Node003, Request RTT 239 Average Request RTT 313
2020-04-22 17:41:50.639 Detail, Node003,   Received: 0x01, 0x1c, 0x00, 0x04, 0x00, 0x03, 0x16, 0x98, 0x81, 0x6f, 0x0b, 0xb2, 0x1a, 0xec, 0x41, 0xb2, 0x2d, 0x82, 0x17, 0x4f, 0x50, 0xcd, 0x9b, 0x45, 0x46, 0xed, 0xe9, 0x96, 0x0e, 0x56
2020-04-22 17:41:50.639 Info, Raw: 0x98, 0x81, 0x6f, 0x0b, 0xb2, 0x1a, 0xec, 0x41, 0xb2, 0x2d, 0x82, 0x17, 0x4f, 0x50, 0xcd, 0x9b, 0x45, 0x46, 0xed, 0xe9, 0x96, 0x0e, 0x56
2020-04-22 17:41:50.639 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.639 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.639 Detail, Node003, Decrypted Packet: 0x6e, 0x66, 0xf7
2020-04-22 17:41:50.639 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.640 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.640 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.640 Info, Node001, Setting Up Inclusion Network Key for Secure Communications
2020-04-22 17:41:50.640 Warning, Node003, MAC Authentication of Packet Failed. Dropping
2020-04-22 17:41:50.640 Detail, Node003, Removing current message
2020-04-22 17:41:50.640 Detail,
2020-04-22 17:41:50.640 Info, Node003, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=3): 0x01, 0x04, 0x00, 0x41, 0x03, 0xb9
2020-04-22 17:41:50.642 Detail, Node003,   Received: 0x01, 0x09, 0x01, 0x41, 0x53, 0xdc, 0x01, 0x04, 0x40, 0x03, 0x7f
2020-04-22 17:41:50.642 Detail,
2020-04-22 17:41:50.642 Info, Node003, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2020-04-22 17:41:50.642 Info, Node003,   Protocol Info for Node 3:
2020-04-22 17:41:50.642 Info, Node003,     Listening     = false
2020-04-22 17:41:50.642 Info, Node003,     Frequent      = true
2020-04-22 17:41:50.642 Info, Node003,     Beaming       = true
2020-04-22 17:41:50.642 Info, Node003,     Routing       = true
2020-04-22 17:41:50.642 Info, Node003,     Max Baud Rate = 40000
2020-04-22 17:41:50.642 Info, Node003,     Version       = 4
2020-04-22 17:41:50.642 Info, Node003,     Security      = false
2020-04-22 17:41:50.642 Detail, Node220,   Expected reply was received
2020-04-22 17:41:50.642 Detail, Node220,   Message transaction complete
2020-04-22 17:41:50.642 Detail,
2020-04-22 17:41:50.642 Detail, Node003, Removing current message
2020-04-22 17:41:50.642 Detail, Node003, Query Stage Complete (ProtocolInfo)
2020-04-22 17:41:50.642 Detail, Node003, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2020-04-22 17:41:50.642 Detail, Node003, QueryStage_Probe
2020-04-22 17:41:50.642 Info, Node003, NoOperation::Set - Routing=true
2020-04-22 17:41:50.642 Detail, Node003, Queuing (NoOp) NoOperation_Set (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x00, 0x00, 0x25, 0x0e, 0xcf
2020-04-22 17:41:50.642 Detail, Node003, Queuing (Query) Query Stage Complete (Probe)
2020-04-22 17:41:50.642 Detail,
2020-04-22 17:41:50.642 Info, Node003, Sending (NoOp) message (Callback ID=0x0e, Expected Reply=0x13) - NoOperation_Set (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x00, 0x00, 0x25, 0x0e, 0xcf
2020-04-22 17:41:50.650 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:41:50.650 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:41:50.779 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x0e, 0x00, 0x00, 0x0d, 0xe8
2020-04-22 17:41:50.779 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x0e received (expected 0x0e)
2020-04-22 17:41:50.779 Info, Node003, Request RTT 136 Average Request RTT 224
2020-04-22 17:41:50.779 Detail,   Expected callbackId was received
2020-04-22 17:41:50.779 Detail,   Expected reply was received
2020-04-22 17:41:50.779 Detail,   Message transaction complete
2020-04-22 17:41:50.779 Detail,
2020-04-22 17:41:50.779 Detail, Node003, Removing current message
2020-04-22 17:41:50.779 Detail, Node003, Notification: Notification - NoOperation
2020-04-22 17:41:50.780 Detail, Node003, Query Stage Complete (Probe)
2020-04-22 17:41:50.780 Detail, Node003, AdvanceQueries queryPending=0 queryRetries=0 queryStage=WakeUp live=1
2020-04-22 17:41:50.780 Detail, Node003, QueryStage_WakeUp
2020-04-22 17:41:50.780 Detail, Node003, QueryStage_ManufacturerSpecific1
2020-04-22 17:41:50.780 Detail, Node003, Checking for ManufacturerSpecific CC and Requesting values if present on this node
2020-04-22 17:41:50.780 Detail, Node003, Queuing (Query) ManufacturerSpecificCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x72, 0x04, 0x25, 0x0f, 0xb8
2020-04-22 17:41:50.780 Detail, Node003, Queuing (Query) Query Stage Complete (ManufacturerSpecific1)
2020-04-22 17:41:50.780 Detail,
2020-04-22 17:41:50.780 Info, Node003, Sending (Query) message (Callback ID=0x0f, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x72, 0x04, 0x25, 0x0f, 0xb8
2020-04-22 17:41:50.787 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:41:50.788 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:41:50.808 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x0f, 0x00, 0x00, 0x03, 0xe7
2020-04-22 17:41:50.808 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x0f received (expected 0x0f)
2020-04-22 17:41:50.808 Info, Node003, Request RTT 28 Average Request RTT 126
2020-04-22 17:41:50.808 Detail,   Expected callbackId was received
2020-04-22 17:42:00.780 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-04-22 17:42:00.781 Detail, Node003, Removing current message
2020-04-22 17:42:00.781 Detail, Node003, Notification: Notification - TimeOut
2020-04-22 17:42:00.781 Detail, Node003, Query Stage Complete (ManufacturerSpecific1)
2020-04-22 17:42:00.781 Detail, Node003, AdvanceQueries queryPending=0 queryRetries=0 queryStage=NodeInfo live=1
2020-04-22 17:42:00.781 Detail, Node003, QueryStage_NodePlusInfo
2020-04-22 17:42:00.782 Detail, Node003, Queuing (Query) ZWavePlusInfoCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x5e, 0x01, 0x25, 0x10, 0x8e
2020-04-22 17:42:00.782 Detail, Node003, Queuing (Query) Query Stage Complete (NodePlusInfo)
2020-04-22 17:42:00.782 Detail,
2020-04-22 17:42:00.782 Info, Node003, Sending (Query) message (Callback ID=0x10, Expected Reply=0x04) - ZWavePlusInfoCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x5e, 0x01, 0x25, 0x10, 0x8e
2020-04-22 17:42:00.789 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:42:00.789 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:42:04.417 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x10, 0x01, 0x01, 0x6b, 0x90
2020-04-22 17:42:04.417 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x10 received (expected 0x10)
2020-04-22 17:42:04.417 Info, Node003, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-04-22 17:42:04.417 Warning, Node003, WARNING: Device is not a sleeping node.
2020-04-22 17:42:04.417 Detail, Node001,   Expected callbackId was received
2020-04-22 17:42:10.782 Error, Node003, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-04-22 17:42:10.782 Detail, Node003, Removing current message
2020-04-22 17:42:10.783 Detail, Node003, Notification: Notification - TimeOut
2020-04-22 17:42:10.783 Detail, Node003, Query Stage Complete (NodePlusInfo)
2020-04-22 17:42:10.783 Detail, Node003, AdvanceQueries queryPending=0 queryRetries=0 queryStage=SecurityReport live=1
2020-04-22 17:42:10.783 Detail, Node003, QueryStage_SecurityReport
2020-04-22 17:42:10.783 Detail, Node003, Queuing (Security) SecurityCmd_SupportedGet (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x02, 0x25, 0x11, 0x4a
2020-04-22 17:42:10.783 Detail, Node003, Queuing (Query) Query Stage Complete (SecurityReport)
2020-04-22 17:42:10.783 Detail,
2020-04-22 17:42:10.783 Info, Node003, Processing (Security) Nonce Request message (Callback ID=0x11, Expected Reply=0x04)
2020-04-22 17:42:10.783 Info, Node003, Sending (Security) message (Callback ID=0x11, Expected Reply=0x04) - Nonce_Get(SecurityCmd_SupportedGet) - 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x98, 0x40, 0x05, 0x02:
2020-04-22 17:42:10.794 Detail, Node003,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2020-04-22 17:42:10.794 Detail, Node003,   ZW_SEND_DATA delivered to Z-Wave stack
2020-04-22 17:42:14.307 Detail, Node003,   Received: 0x01, 0x07, 0x00, 0x13, 0x02, 0x01, 0x01, 0x60, 0x89
2020-04-22 17:42:14.307 Detail, Node003,   ZW_SEND_DATA Request with callback ID 0x02 received (expected 0x02)
2020-04-22 17:42:14.307 Info, Node003, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2020-04-22 17:42:14.307 Warning, Node003, WARNING: Device is not a sleeping node.

Thanks!

2

I have a Schlage BE469ZP and it works just fine. Here’s a few things to check/note:

  • The preferred and highly recommended way to add/remove/edit nodes is using the Zwave manager under the frontend configuration menu (may have to go into the currently logged in user on the frontend and enable advanced mode for it to show up). This ensures HA knows anything and everything about your Zwave setup and the node. Do not use the stick or any other piece of Zwave controller software to pair devices.
  • Start by excluding the device. Go to the Zwave manager, click on the “Remove Node” service button and then press the pairing/function button on the lock (I believe this is the Schlage logo on the keypad, maybe it’s under the battery cover, I can’t remember, check the user manual). Restart HA. Go into the entity registry and remove any entity pertaining to the lock and/or unavailable. Restart HA again
  • Add the lock using “Add Node Secure” service button. The lock is a security device and will only work/report properly if added to the Zwave network under secure inclusion. You already have the network key set, so you’re halfway there. Using the normal “Add Node” may allow the lock to report some status info, but may not allow full control. Restart HA and verify node shows up in both the Zwave manager node list and in the entity registry.

Hopefully this helps and gets you on the right track.

EDIT: Looks like you did add this node as secure according to the log you posted and the Zwave controller picked it up as a security device. However this line in the log concerns me:

2020-04-22 17:41:50.640 Warning, Node003, MAC Authentication of Packet Failed. Dropping

How far away are the controller and node? Is it possible there’s interference between the two devices? The log shows generally ok RTT (round trip time) for packet transmission of 28ms to ~350ms. However there are a couple of times very shortly after adding where the RTT was in the 1100s. While ok, it’s a little slow. Thus my thought there may be interference due to distance or building material in-between.

I’d still recommend doing a remove node, possibly factory reset the lock, restart HA, and re-add. I’ve had to use the remove node on light switches a couple times before it was truly ready to be paired again.

3

You might also try rebooting the lock (unhook the battery and then hook it back up). One of mine stopped responding at one point and rebooting it fixed it.

4

Yeah at first I was trying everything in HA only and then resorted to other means. My server that is running HA is 2 rooms over, probably about 40 feet through 2 walls. It is my only device at the moment and with it being battery powered, I’m assuming it doesn’t have a strong transmitter. I had been planning on getting a few on/off switches which I know will act as repeaters, do you think that would help?

I can try moving my server temporarily near the front door to see if that fixes the latency issue.

5

I don’t think it would help actually. My lock and USB stick are separated by sub flooring, hard wood floors, a metal beam, a stainless steel refrigerator with quartz counter tops on either side, solid wood cabinets, and two walls. My last Request and Response RTT were in the low 500ms and my average RTT is in the low 800ms. My failed to total sent packets ratio is 10%. Like suggested above, reboot the lock. However, if the lock isn’t properly paired to or showing up in HA, that may not do anything. I find it a little odd the lock just shows up as generic.

And actually I just realized my lock wasn’t even directly connected to the Zwave stick. It was at least one node and 2 hops away. I think there’s a HA or hardware issue going on with your Zwave network. Unfortunately I’m kinda out of suggestions. :confused: sorry.

6

I’ll probably still try it to rule it out. I feel like I’ve tried everything as it takes a lot for me to post for help online.

I tried resetting the lock to factory defaults a few times too. What is weird is that I will enroll the lock and it will flash red meaning it failed, but it then shows up as an unknown node in HA. If I use the Zwave PC Controller software, I can see it show up in there too. Maybe I will try some other software on my laptop and see if I can successfully enroll it on there vs my HA installation on my server.

Thanks for the suggestions, I appreciate it.

7

Hi everyone,

New to HA and the community. So much information out there it’s been super helpful - but also overloading at times lol.

I have the same BE469 locks (have 2 of them) with Aeotec Z-Stick Gen5 and was able to finally get this working. Here are some things to consider and tips that may help those who are still struggling.

My first issue was not having a network key when I added my Z-stick. I ended up starting all over again, and added z-wave through integrations UI in HA (as opposed to adding it manually in my configuration.yaml) - this set it up correctly, and also generated a network key automatically that gets pulled from my config_entries files under config\storage directory. I felt confident this was the correct way. For reference my in my config_entries files has my Z-stick reference by-id as follows;
“usb_path”: “/dev/serial/by-id/usb-0658_0200-if00” <-- yours may be different so verify what port your USB z-stick is plugged into. I also read that the network key should not have spaces in-between, so I also removed them - not sure if it makes a difference but it’s working so I rather not feel the need to verify this :smile:

When I was ready to add the locks I essentially had to pair it twice oddly enough. First I removed the usb Z-Stick and put it in pairing mode. I then did the steps to put the lock in pairing mode and received the successful green check mark to indicate it’s been paired. When i reinserted the USB stick and restarted HA - nothing showed up.

Scratched my head, and then decided to now add a secure node through Z-Wave interface in HA. So, clicked add secure node, again put the lock in pairing mode - and a second or two later - got the green check mark confirming successful pairing. You may need to restart HA again, but for me it showed up within a minute on my overview. I renamed the friendly name and entity_id (lock.[your_custom_name]) and voila - up and going!

Hope this helps. My next plan is learning how to create some automations and scripts.

Side question/help: if anyone has any links to how people convert their traditional garage door opener to a smart opener please send those along. I keep forgetting and leaving it open - want to be able to have it close through automation/triggers.

Thanks!
-M