Since Locks, while battery powered, are two way devices they do report neighbors. Messages to update Neighbors will be queued and when the Lock wakes it will get the queued commands. Here are the logs from my BE469 using external tools.
2020-03-02 16:11:21.018 Detail, Node035, Queuing (Command) Get Routing Info (Node=35): 0x01, 0x07, 0x00, 0x80, 0x23, 0x00, 0x00, 0x03, 0x58
2020-03-02 16:11:21.018 Detail, Node035, Queuing (Query) Query Stage Complete (Neighbors)
2020-03-02 16:11:21.018 Info, Node035, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=35): 0x01, 0x07, 0x00, 0x80, 0x23, 0x00, 0x00, 0x03, 0x58
2020-03-02 16:11:21.057 Detail, Node035, Received: 0x01, 0x20, 0x01, 0x80, 0x25, 0x85, 0xc8, 0x00, 0x02, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x34
2020-03-02 16:11:21.057 Info, Node035, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2020-03-02 16:11:21.057 Info, Node035, Neighbors of this node are:
2020-03-02 16:11:21.057 Info, Node035, Node 1
2020-03-02 16:11:21.057 Info, Node035, Node 3
2020-03-02 16:11:21.057 Info, Node035, Node 6
2020-03-02 16:11:21.057 Info, Node035, Node 9
2020-03-02 16:11:21.057 Info, Node035, Node 11
2020-03-02 16:11:21.057 Info, Node035, Node 16
2020-03-02 16:11:21.057 Info, Node035, Node 20
2020-03-02 16:11:21.057 Info, Node035, Node 23
2020-03-02 16:11:21.057 Info, Node035, Node 24
2020-03-02 16:11:21.057 Info, Node035, Node 34
If you really want to understand your network and perhaps try and figure out what and where may be causing problems, you should get an extra Zwave stick and one of the software tools.