node-zwave-js: bug: heal seems to fail with silicon labs 700 controller

Describe the bug

When i perform a heal it doesn’t appear to work based on the logs…

Device information

All devices and all node IDs. What are the node IDs?

Last Known Working Configuration

• New device
• Previously working device (node-zwave-js)
  • zwavejs2mqtt with razberry pi hat zwave controler - multiple versions
  • swapped to the silicon labs SLUSB001A

Installation information How did you install node-zwave-js?

• zwavejs2mqtt (latest) docker image
• zwavejs2mqtt (dev) docker image
• ioBroker.zwave2 adapter
• Pkg
• Manual Docker build
  • node-zwave-js branch: master
  • zwavejs2mqtt branch: master
• Manually built (as described in the docs)
• [] Other:

To Reproduce Steps to reproduce the behavior:

1. Go to ‘.ontrol pane;’
2. Click on ‘heal network’
3. See error in logs

Additional context App Version 1.1.1+94ff7ed.94ff7ed

Zwavejs Version 6.3.0-8f22052

Logfile:

00:38:45.842 CNTRLR » [Node 002] refreshing neighbor list (attempt 1)...
00:38:45.853 DRIVER » [Node 002] [REQ] [RequestNodeNeighborUpdate]
                        callback id: 132
00:38:45.854 CNTRLR » [Node 003] refreshing neighbor list (attempt 1)...
00:38:45.860 CNTRLR » [Node 004] refreshing neighbor list (attempt 1)...
00:38:45.864 CNTRLR » [Node 005] refreshing neighbor list (attempt 1)...
00:38:45.867 CNTRLR » [Node 006] refreshing neighbor list (attempt 1)...
00:38:45.871 CNTRLR » [Node 007] refreshing neighbor list (attempt 1)...
00:38:45.874 CNTRLR » [Node 008] refreshing neighbor list (attempt 1)...
00:38:45.881 CNTRLR » [Node 009] refreshing neighbor list (attempt 1)...
00:38:45.884 CNTRLR » [Node 010] refreshing neighbor list (attempt 1)...
00:38:45.888 CNTRLR » [Node 011] refreshing neighbor list (attempt 1)...
00:38:45.891 CNTRLR » [Node 012] refreshing neighbor list (attempt 1)...
00:38:45.895 CNTRLR » [Node 013] refreshing neighbor list (attempt 1)...
00:38:45.900 CNTRLR » [Node 014] refreshing neighbor list (attempt 1)...
00:38:45.904 CNTRLR » [Node 015] refreshing neighbor list (attempt 1)...
00:38:45.907 CNTRLR » [Node 017] refreshing neighbor list (attempt 1)...
00:38:45.911 CNTRLR » [Node 018] refreshing neighbor list (attempt 1)...
00:38:45.914 CNTRLR » [Node 019] refreshing neighbor list (attempt 1)...
00:38:45.920 CNTRLR » [Node 020] refreshing neighbor list (attempt 1)...
00:38:49.396 DRIVER « [REQ] [RequestNodeNeighborUpdate]
                        callback id:   132
                        update status: UpdateStarted
00:39:26.956 DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                      └─[ClockCCReport]
                          clock setting: Tuesday, 01:00
00:39:26.959 CNTRLR   [Node 020] detected a deviation of the node's clock, updating it...
00:39:26.995 DRIVER « [Node 020] [REQ] [BridgeApplicationCommand]
                      └─[ClockCCReport]
                          clock setting: Tuesday, 01:00
00:39:26.998 CNTRLR   [Node 020] detected a deviation of the node's clock, updating it...
00:39:54.419 DRIVER » [Node 003] [REQ] [RequestNodeNeighborUpdate]
                        callback id: 133
00:39:54.420 CNTRLR   [Node 002] refreshing neighbor list failed: Timeout while waiting for a callba
                      ck from the controller
00:39:54.421 CNTRLR » [Node 002] refreshing neighbor list (attempt 2)...
00:39:57.324 DRIVER « [REQ] [RequestNodeNeighborUpdate]
                        callback id:   133
                        update status: UpdateStarted
00:41:02.338 DRIVER » [Node 004] [REQ] [RequestNodeNeighborUpdate]
                        callback id: 134
00:41:02.340 CNTRLR   [Node 003] refreshing neighbor list failed: Timeout while waiting for a callba
                      ck from the controller
00:41:02.340 CNTRLR » [Node 003] refreshing neighbor list (attempt 2)...
00:41:04.925 DRIVER « [REQ] [RequestNodeNeighborUpdate]
                        callback id:   134
                        update status: UpdateStarted

this continue through all devices and then reports heal failed.