question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

bug: heal seems to fail with silicon labs 700 controller

See original GitHub issue

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.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:27 (25 by maintainers)

github_iconTop GitHub Comments

2reactions
scytocommented, Feb 17, 2021

updated controller FW to 7.15 and raised gain to +4

Do you have a reference on how to perform the update?

high level only:

  • install simplicity studio and zwave tools (why do they make that so hard)
  • do a backup of the stick
  • when in the controller top level UI click OTW icon
  • navigate to C:\SiliconLabs\SimplicityStudio\v5\developer\sdks\gecko_sdk_suite\v3.1\protocol\z-wave\Apps\bin\gbl
  • choose (for US) ZW_SerialAPI_Controller_7.15.2_214_EFR32ZG14_REGION_US.gbl (the LR version won’t buy you anything unless you have some LR devices, and i don’t think they exist yet?)
  • wait, and its done

For gain:

  • install simplicity studio and zwave tools
  • on the controller top level menu pick the ‘transmit settings’
  • change the first box to +4 image
0reactions
scytocommented, Feb 28, 2021

It is in direct range of all four locks in a 3000 sq ft house.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Z-Wave PC based Controller v5 User Guide - Silicon Labs
A non-responding node can be replaced by another node from the node list in the Z-Wave network by activating the button 'Replace Failed'....
Read more >
Question - Silicon Labs Community
Until recently, 700 series Z-Wave Controllers had a bug that could cause the mesh to be flooded on some networks and the controller...
Read more >
Z-Wave 700 ZGM130S Long Range Radio Board User's Guide
If the board controller is unable to locate the RTT Control Block, it will return an error message on the same connection. For...
Read more >
EFR32ZG14 Long Range Wireless Starter Kit User's Guide
The Wireless Starter Kit Mainboard contains an on-board J-Link debugger with a Packet. Trace Interface and a virtual COM port, enabling application ...
Read more >
Z-Wave Getting Started for End Devices - Silicon Labs
Front page Removed 700 ... Figure 8: PC Controller, Command Classes View―Send Switch On Command . ... To get the latest news of...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found