August lock pro issues pairing

I am having an extreme amount of issues pairing my august lock.

I have had to force remove my august lock many times which I know may not be right but I have often that my august is saying paired yet my aeotec OZW logs are saying timeout. I went into the zwcfq file and I see the lock come out about 4 times with different node id.

Right now I have the integration showing my august lock but entity unavailable.

All I am trying to do is clean up and force my aeotec to forget my august lock once and for all even in the logs and start once more. Before I was pairing with secure node and didn’t have the network key in my yaml file (don’t remember if I linked it up in the integrations tab).

Can anyone help me understand how I can purge my aeotec? I can’t see a lock in my z wave configuration panel so even tho the zwcfg file has the august lock mentioned with like 4 different nodes ids it doesn’t come up in the UI at all only right now in the integration.

Another thing that happend was that I was able to pair my lock once and then it was saying initializing for a while so I restarted it since I tested out and noticed that the lock entity was not switching from lock to unlock as I was physically moving the lock. Once I restarted that is when I noticed the entities just randomly went to unavailable in the integrations tab and the node went away.

Nodes 24, 21, 22 and I think one more are all tied to my lock if you see it mentions DoorLock. I don’t understand the timeout.

In either case I just want to start once again and purge this, not sure how to do this. Usually with stubbord entities I learned recently I can delete some files in .storage and the db and it will forget them but this is different as I have a usb and don’t want to mess this up.

2019-08-14 22:56:26.055 Info, Node020, Sending (Query) message (Callback ID=0x6e, Expected Reply=0x04) - PowerlevelCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x73, 0x02, 0x25, 0x6e, 0xc9
2019-08-14 22:56:26.434 Detail, Node020,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-14 22:56:26.434 Detail, Node020,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-14 22:56:36.056 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:56:36.056 Detail, Node020, Removing current message
2019-08-14 22:56:36.056 Detail, Node020, Notification: Notification - TimeOut
2019-08-14 22:56:36.056 Detail, Node020, Query Stage Complete (Session)
2019-08-14 22:56:36.057 Detail, Node020, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2019-08-14 22:56:36.057 Detail, Node020, QueryStage_Dynamic
2019-08-14 22:56:36.057 Detail, Node020, Queuing (Send) DoorLockCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x62, 0x02, 0x25, 0xf4, 0x42
2019-08-14 22:56:36.057 Detail, Node020, Queuing (Send) BatteryCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x80, 0x02, 0x25, 0xf5, 0xa1
2019-08-14 22:56:36.057 Detail, Node020, Queuing (Query) Query Stage Complete (Dynamic)
2019-08-14 22:56:36.057 Detail, 
2019-08-14 22:56:36.057 Info, Node020, Sending (Send) message (Callback ID=0xf4, Expected Reply=0x04) - DoorLockCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x62, 0x02, 0x25, 0xf4, 0x42
2019-08-14 22:56:36.202 Detail, Node020,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-14 22:56:36.202 Detail, Node020,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-14 22:56:46.058 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:56:46.058 Detail, Node020, Removing current message
2019-08-14 22:56:46.058 Detail, Node020, Notification: Notification - TimeOut
2019-08-14 22:56:46.059 Detail, 
2019-08-14 22:56:46.059 Info, Node020, Sending (Send) message (Callback ID=0xf5, Expected Reply=0x04) - BatteryCmd_Get (Node=20): 0x01, 0x09, 0x00, 0x13, 0x14, 0x02, 0x80, 0x02, 0x25, 0xf5, 0xa1
2019-08-14 22:56:46.065 Detail, Node020,   Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2019-08-14 22:56:46.065 Error, Node020, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-08-14 22:56:56.061 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:56:56.061 Detail, Node020, Removing current message
2019-08-14 22:56:56.061 Detail, Node020, Notification: Notification - TimeOut
2019-08-14 22:56:56.062 Detail, 
2019-08-14 22:56:56.062 Info, Node021, Sending (Query) message (Callback ID=0x6f, Expected Reply=0x04) - PowerlevelCmd_Get (Node=21): 0x01, 0x09, 0x00, 0x13, 0x15, 0x02, 0x73, 0x02, 0x25, 0x6f, 0xc9
2019-08-14 22:56:56.067 Detail, Node021,   Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2019-08-14 22:56:56.067 Error, Node021, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-08-14 22:56:57.156 Detail, Node021,   Received: 0x01, 0x07, 0x00, 0x13, 0x6f, 0x01, 0x00, 0x6d, 0xe8
2019-08-14 22:56:57.156 Detail, Node021,   ZW_SEND_DATA Request with callback ID 0x6f received (expected 0x6f)
2019-08-14 22:56:57.156 Info, Node021, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2019-08-14 22:56:57.156 Warning, Node021, WARNING: Device is not a sleeping node.
2019-08-14 22:56:57.157 Detail, Node001,   Expected callbackId was received
2019-08-14 22:57:04.234 Detail, Node021,   Received: 0x01, 0x07, 0x00, 0x13, 0x6f, 0x01, 0x03, 0x31, 0xb7
2019-08-14 22:57:04.234 Detail, Node021,   ZW_SEND_DATA Request with callback ID 0x6f received (expected 0x00)
2019-08-14 22:57:04.234 Warning, Node021, WARNING: Unexpected Callback ID received
2019-08-14 22:57:06.063 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:57:06.063 Detail, Node021, Removing current message
2019-08-14 22:57:06.064 Detail, Node021, Notification: Notification - TimeOut
2019-08-14 22:57:06.064 Detail, Node021, Query Stage Complete (Session)
2019-08-14 22:57:06.064 Detail, Node021, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Dynamic live=1
2019-08-14 22:57:06.064 Detail, Node021, QueryStage_Dynamic
2019-08-14 22:57:06.064 Detail, Node021, Queuing (Send) DoorLockCmd_Get (Node=21): 0x01, 0x09, 0x00, 0x13, 0x15, 0x02, 0x62, 0x02, 0x25, 0xf6, 0x41
2019-08-14 22:57:06.064 Detail, Node021, Queuing (Send) BatteryCmd_Get (Node=21): 0x01, 0x09, 0x00, 0x13, 0x15, 0x02, 0x80, 0x02, 0x25, 0xf7, 0xa2
2019-08-14 22:57:06.065 Detail, Node021, Queuing (Query) Query Stage Complete (Dynamic)
2019-08-14 22:57:06.065 Detail, 
2019-08-14 22:57:06.065 Info, Node021, Sending (Send) message (Callback ID=0xf6, Expected Reply=0x04) - DoorLockCmd_Get (Node=21): 0x01, 0x09, 0x00, 0x13, 0x15, 0x02, 0x62, 0x02, 0x25, 0xf6, 0x41
2019-08-14 22:57:06.200 Detail, Node021,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-14 22:57:06.200 Detail, Node021,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-14 22:57:16.065 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:57:16.065 Detail, Node021, Removing current message
2019-08-14 22:57:16.065 Detail, Node021, Notification: Notification - TimeOut
2019-08-14 22:57:16.066 Detail, 
2019-08-14 22:57:16.066 Info, Node021, Sending (Send) message (Callback ID=0xf7, Expected Reply=0x04) - BatteryCmd_Get (Node=21): 0x01, 0x09, 0x00, 0x13, 0x15, 0x02, 0x80, 0x02, 0x25, 0xf7, 0xa2
2019-08-14 22:57:16.322 Detail, Node021,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-14 22:57:16.322 Detail, Node021,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-14 22:57:23.223 Detail, Node021,   Received: 0x01, 0x07, 0x00, 0x13, 0xf7, 0x01, 0x02, 0xbe, 0xa1
2019-08-14 22:57:23.223 Detail, Node021,   ZW_SEND_DATA Request with callback ID 0xf7 received (expected 0xf7)
2019-08-14 22:57:23.223 Info, Node021, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2019-08-14 22:57:23.223 Warning, Node021, WARNING: Device is not a sleeping node.
2019-08-14 22:57:23.223 Detail, Node001,   Expected callbackId was received
2019-08-14 22:57:26.067 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:57:26.067 Detail, Node021, Removing current message
2019-08-14 22:57:26.067 Detail, Node021, Notification: Notification - TimeOut
2019-08-14 22:57:26.068 Detail, Node022, Query Stage Complete (Dynamic)
2019-08-14 22:57:26.068 Detail, Node022, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Configuration live=1
2019-08-14 22:57:26.068 Detail, Node022, QueryStage_Configuration
2019-08-14 22:57:26.068 Detail, Node022, QueryStage_Complete
2019-08-14 22:57:26.068 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2019-08-14 22:57:26.068 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2019-08-14 22:57:26.068 Detail, Node022, Notification: NodeQueriesComplete
2019-08-14 22:57:26.068 Detail, 
2019-08-14 22:57:26.069 Info, Node024, Sending (Query) message (Callback ID=0x71, Expected Reply=0x04) - DoorLockCmd_Configuration_Get (Node=24): 0x01, 0x09, 0x00, 0x13, 0x18, 0x02, 0x62, 0x05, 0x25, 0x71, 0xcc
2019-08-14 22:57:26.080 Detail, Node024,   Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-08-14 22:57:26.080 Detail, Node024,   ZW_SEND_DATA delivered to Z-Wave stack
2019-08-14 22:57:36.070 Error, Node024, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:57:36.070 Detail, Node024, Removing current message
2019-08-14 22:57:36.070 Detail, Node024, Notification: Notification - TimeOut
2019-08-14 22:57:36.071 Detail, 
2019-08-14 22:57:36.071 Info, Node024, Sending (Query) message (Callback ID=0x72, Expected Reply=0x04) - UserNumberCmd_Get (Node=24): 0x01, 0x09, 0x00, 0x13, 0x18, 0x02, 0x63, 0x04, 0x25, 0x72, 0xcf
2019-08-14 22:57:36.075 Detail, Node024,   Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2019-08-14 22:57:36.076 Error, Node024, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-08-14 22:57:46.072 Error, Node024, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:57:46.072 Detail, Node024, Removing current message
2019-08-14 22:57:46.072 Detail, Node024, Notification: Notification - TimeOut
2019-08-14 22:57:46.073 Detail, 
2019-08-14 22:57:46.073 Info, Node024, Sending (Query) message (Callback ID=0x73, Expected Reply=0x04) - ManufacturerSpecificCmd_Get (Node=24): 0x01, 0x09, 0x00, 0x13, 0x18, 0x02, 0x72, 0x04, 0x25, 0x73, 0xdf
2019-08-14 22:57:46.078 Detail, Node024,   Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2019-08-14 22:57:46.078 Error, Node024, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-08-14 22:57:56.074 Error, Node024, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:57:56.074 Detail, Node024, Removing current message
2019-08-14 22:57:56.074 Detail, Node024, Notification: Notification - TimeOut
2019-08-14 22:57:56.075 Detail, 
2019-08-14 22:57:56.075 Info, Node024, Sending (Query) message (Callback ID=0x74, Expected Reply=0x04) - VersionCmd_Get (Node=24): 0x01, 0x09, 0x00, 0x13, 0x18, 0x02, 0x86, 0x11, 0x25, 0x74, 0x39
2019-08-14 22:57:56.080 Detail, Node024,   Received: 0x01, 0x04, 0x01, 0x13, 0x00, 0xe9
2019-08-14 22:57:56.080 Error, Node024, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
2019-08-14 22:57:59.515 Detail, Node024,   Received: 0x01, 0x07, 0x00, 0x13, 0x74, 0x01, 0x01, 0x58, 0xc7
2019-08-14 22:57:59.516 Detail, Node024,   ZW_SEND_DATA Request with callback ID 0x74 received (expected 0x74)
2019-08-14 22:57:59.516 Info, Node024, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2019-08-14 22:57:59.516 Warning, Node024, WARNING: Device is not a sleeping node.
2019-08-14 22:57:59.516 Detail, Node001,   Expected callbackId was received
2019-08-14 22:58:02.983 Detail, Node024,   Received: 0x01, 0x07, 0x00, 0x13, 0x74, 0x01, 0x02, 0xb3, 0x2f
2019-08-14 22:58:02.983 Detail, Node024,   ZW_SEND_DATA Request with callback ID 0x74 received (expected 0x00)
2019-08-14 22:58:02.983 Warning, Node024, WARNING: Unexpected Callback ID received
2019-08-14 22:58:06.076 Error, Node024, ERROR: Dropping command, expected response not received after 1 attempt(s)
2019-08-14 22:58:06.076 Detail, Node024, Removing current message
2019-08-14 22:58:06.076 Detail, Node024, Notification: Notification - TimeOut
2019-08-14 22:58:06.077 Detail, Node024, Query Stage Complete (Static)
2019-08-14 22:58:06.077 Detail, Node024, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Associations live=1
2019-08-14 22:58:06.077 Detail, Node024, QueryStage_Associations
2019-08-14 22:58:06.077 Detail, Node024, QueryStage_Neighbors
2019-08-14 22:58:06.077 Detail, Requesting routing info (neighbor list) for Node 24
2019-08-14 22:58:06.077 Detail, Node024, Queuing (Command) Get Routing Info (Node=24): 0x01, 0x07, 0x00, 0x80, 0x18, 0x00, 0x00, 0x03, 0x63
2019-08-14 22:58:06.077 Detail, Node024, Queuing (Query) Query Stage Complete (Neighbors)
2019-08-14 22:58:06.077 Detail, 
2019-08-14 22:58:06.077 Info, Node024, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=24): 0x01, 0x07, 0x00, 0x80, 0x18, 0x00, 0x00, 0x03, 0x63
2019-08-14 22:58:06.085 Detail, Node024,   Received: 0x01, 0x20, 0x01, 0x80, 0x3d, 0x0c, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x6e
2019-08-14 22:58:06.085 Detail, 
2019-08-14 22:58:06.085 Info, Node024, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2019-08-14 22:58:06.085 Info, Node024,     Neighbors of this node are:
2019-08-14 22:58:06.085 Info, Node024,     Node 1
2019-08-14 22:58:06.085 Info, Node024,     Node 3
2019-08-14 22:58:06.085 Info, Node024,     Node 4
2019-08-14 22:58:06.085 Info, Node024,     Node 5
2019-08-14 22:58:06.085 Info, Node024,     Node 6
2019-08-14 22:58:06.085 Info, Node024,     Node 11
2019-08-14 22:58:06.085 Info, Node024,     Node 12
2019-08-14 22:58:06.085 Info, Node024,     Node 17
2019-08-14 22:58:06.085 Detail, Node012,   Expected reply was received
2019-08-14 22:58:06.085 Detail, Node012,   Message transaction complete
2019-08-14 22:58:06.085 Detail, 
2019-08-14 22:58:06.086 Detail, Node024, Removing current message
2019-08-14 22:58:06.086 Detail, Node025, Query Stage Complete (Neighbors)
2019-08-14 22:58:06.086 Detail, Node025, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2019-08-14 22:58:06.086 Detail, Node025, QueryStage_Session
2019-08-14 22:58:06.086 Detail, Node025, QueryStage_Dynamic
2019-08-14 22:58:06.086 Detail, Node025, QueryStage_Configuration
2019-08-14 22:58:06.086 Detail, Node025, QueryStage_Complete
2019-08-14 22:58:06.086 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2019-08-14 22:58:06.086 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2019-08-14 22:58:06.086 Detail, Node025, Notification: NodeQueriesComplete

I also see this in my HA logs. I noticed this node 22 is locked not sure if this means that since I have forced removal many times during one of those times it got locked?

2019-08-14 22:54:53 WARNING (MainThread) [homeassistant.loader] You are using a custom integration for hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you do experience issues with Home Assistant.
2019-08-14 22:55:01 WARNING (SyncWorker_6) [plexapi] BadRequest (401) unauthorized http://192.168.2.59:32400/; <html><head><script>window.location = window.location.href.match(/(^.+\/)[^\/]*$/)[1] + 'web/index.html';</script><title>Unauthorized</title></head><body><h1>401 Unauthorized</h1></body></html>
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 18 not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 18 Switch (node_id: 18) not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 19 not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 19 Switch (node_id: 19) not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 20 not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 20 Locked (node_id: 20) not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 21 not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 21 Locked (node_id: 21) not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 22 not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 22 Locked (node_id: 22) not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 24 not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave entity Unknown Node 24 Locked (node_id: 24) not ready after 30 seconds, continuing anyway
2019-08-14 22:55:31 WARNING (MainThread) [homeassistant.components.zwave] Z-Wave node 25 not ready after 30 seconds, continuing anyway
2019-08-14 23:06:35 WARNING (SyncWorker_3) [homeassistant.components.homekit] HomeKit is not ready. Either it is already running or has been stopped.

OK so i have gone into the options.xml and removed all instances of the lock and restarted and still see the same warnings in my logs for some reason (this is probably because those nodes are actually located inside my controller?)

Then i found this link

If you initially setup zwave using configuration.yaml and did not set a network key, it is likely a “null” value in the config entries storage. Adding the network_key to the config file does not yet override the config entries value, so it’s unset (it will work in a future HA release). If you check the .storage/core.config_entries file and see the network_key set to an empty value, that is the problem.

To fix, you can either a) delete the ZWave integration from the UI and restart (it will auto-import the config settings including the key), or b) stop HA, edit the file .storage/core.config_entries and set the network_key value (be careful of formatting), start HA. Although it will work, I would avoid editing the options.xml file.

Solution

so i went ahead and looked at my config_entries under storage directory and realized that even though i added my network key to my yaml it wasn’t being pulled after a restart so I removed my integration and made sure to have usb_path and my network key correct in my yaml. I restarted and now when i checked again my config_entries it has the correct network key. Yet i still see those node 20, 21, 22, 24, 25 etc all show up with these errors