Issues with removing a node

🛎️ Get Help
1

C8, running 2.4.3.176, standard Zwave Zip
Is this normal?
I'm trying to remove a node using the zwave controller program, but the zwave network is always busy!

image
image871×730 150 KB

(I've tried to shutdown, wait, then reboot, but that doesn't help).

2

Did you remove power (unplug at the wall)?

3

Yes, I did.
(I've connected my Hubs to a wifi plug, so that I can bring them back, remotely.)
I shutdown the hubs. I waited a few seconds. I turned off the wifi plug. Waited 60-90 secs. Then turned back on the wifi plug.

4

Wild stab, and not supported on non-Pro model, but you could try upgrading to the JS version. You can always go back.

5

I’ve seen similar I think when I had Z-Wave devices go rogue and start spamming my mesh. Unfortunately, resolving is not always straight forward. I thin some cases a power off of all my Z-Wave devices resolved the issue (main house breaker off for several seconds).

6

I suppose that it has something to do with the following:

image
image793×103 15.3 KB

I can't get zwave discovery inclusion working, because after a few seconds I get the error message: timed out, status:7

Does anybody know why that happens continually?

Well, it looks like that's a "last resort" approach.
Since I don't have any other choices, I will try it.
I will try that in the middle of the night - so as not to alarm anyone.
What an alternative!

1 Like
7

According to Chat GPT, Status 7 means that no device responded to the inclusion request…

If I had this occur, I would likely also try @Slate’s suggestion. I did have JS on my C8 hub for a bit, but it was a device hub only - everything else happened on another hub.

8

Hello.
I decided to take the @Slate suggestion, and I switched over to ZwaveJS on my C8.
My initial impressions:

  1. Much easier to manipulate nodes (e.g. removal). It really works in those situations where previously I would have to get a zwave stick out, get zwave controller up and running, get the zwave stick included, etc. This alone is a big plus.
  2. I believe that there is much more info on the "zwave details" page. This allows me to see if there are any zwave nodes that are problematic. It shows the route and the times, and other stuff. This is a positive feature that can help me hone in to find any "recalcitrant" nodes (i.e. scammers).
  3. It does appear that there is less free memory than before, but I'm still in a good zone on this matter (280K).
    It's a long haul to find out and deal with zwave nodes that are scammers, and to fix them, but at least I now know which ones they are.
    Thanks for the suggestion.
3 Likes