2.2.7.125 Got an update to the logging for failed node removal. If you have a ghost node that can't be removed can you please post the log from the removal here. It will look like:
Failed node XX remove status: X
Remember when trying to remove a ghost node only click remove, and if it is not showing as failed yet click refresh.
What are the conditions that allow the REPLACE button to show up? I've seen where is shows FAILED without a Replace option and then some time later REPLACE shows up. I may not understand the implications, but feel like it would be nice to have the REPLACE option any time a node appears unresponsive.....or lt least a better understanding of why sometimes REPLACE is there and other times its not
The node has to be in the SDK's failed node list.. If the node is truly down and non responsive, clicking refresh (sometimes more than once) should make it be marked as failed if it does not respond..
I have a stubborn ghost node (device physically dead and pulled) that I can't seem to Remove.
Below is the log output from a Repair attempt, multiple Refresh cycles (have done this process a few times), and failure to ultimately Remove the node.
Node only ever says Pending even after identified as unreachable.
Thanks, but this opens up another can of worms then. I do have that device but I have NEVER tried to pair it with this C7. I use to have it paired to my C3 but didn't have any need to connect it to the new C-7.
So why would it grab it? What if this would have been my neighbors device? Not good that it would randomly grab a device I didn't try to pair.
But problem solved on the node. I can now delete it. Thanks.
@bcopeland Just FYI this is what I was always getting as well when trying to remove ghosts on my C7 (network busy). Then it would basically bring the whole network to a halt if I kept trying and I would have to reboot. Once I got a USB stick I went in with that and two clicks and they were gone. Come to think of it the whole thing has been much more stable since I got rid of them.