Added a Z-Net, now I'm seeing odd things in the GUI.

[ewkearns]

OK, so I have always had problems regarding reaching my workshop reliably so I bit the bullet and added a (2nd) Z-Net-G3, today. That much went without a hitch. I decided to try removing 2 devices from Z-Net-1, which didn't go all that well. I removed a door lock (which I expected to be the biggest challenge) and everything went quite well (I thought). When I included it in Z-Net-2, I realized something wasn't quite right. I went back to Z-Net-1 and found that the lock had NOT been removed from Z-Net-1, even though HS4 reported all was well. I had the same thing happen with the second device (a door sensor) and I, now, have an (incorrect) zombie device on Z-Net-1. Over on Z-Net-2, everything seems to be working OK, but I am not able to change the item or location in the child devices (is that a new "thing"?).

Am I doing something wrong? Are there some best practices I'm unaware of? Is this a botched install? I'm kindova afraid to keep going with these anomalies...

Z-Wave Ver 3.0.10.0; HS4 4.2.16.0

[ewkearns]

AND...... I'm now getting this warning in the logs from the "new" Z-NET:

Z-NET-SHOP-1: Z-Wave PC Controller Library Version: Z-Wave 7.18 (Unknown)

Thoughts?

[randy]

I get this at startup, but it is not a warning.

2/1/2023 12:05:00 PM Legacy-Plugin. Z-Wave. Shed: Controller firmware version: 7.18

Your signature says you are running Z-Wave 3.0.10.0, but I remember 3.0.11.0 is required for the 700 series controllers. If you’re not running the beta, you might try it.

[ewkearns]

Wow, Randy, THANKS! I did see your forum post on this and actually went looking for 3.0.11.0, but concluded that it had been pulled in lieu of some 4.x iteration. It never occurred to me to look for legacy beta ware that is mislabeled 4.0.10.0 and must be "reinstalled," rather than installed. However, 3.0.11.0 appears to have taken care of the warning in the log AND my CT-100 thermostats appear to be polling again, so I get all of the available information. Anyone reading this, and taking the safer 3.x route... I highly recommend taking Randy's recollections seriously and go with version 3.0.11.0.

[randy]

Wow, Randy, THANKS! I did see your forum post on this and actually went looking for 3.0.11.0, but concluded that it had been pulled in lieu of some 4.x iteration. It never occurred to me to look for legacy beta ware that is mislabeled 4.0.10.0 and must be "reinstalled," rather than installed. However, 3.0.11.0 appears to have taken care of the warning in the log AND my CT-100 thermostats appear to be polling again, so I get all of the available information. Anyone reading this, and taking the safer 3.x route... I highly recommend taking Randy's recollections seriously and go with version 3.0.11.0.

Good! WRT your original question about orphaned nodes. Since you are running 3.0.11.0 this is relatively easy. See if there is still a Z-Wave node assigned to each by looking at the Z-Wave tab. If there is no node assigned, just delete the HS parent device. If a node number is assigned, “Test Connectivity”. If it fails, immediately do it again. When it fails a second time, “Remove Bad Node”.

[ewkearns]

I don't think it is going to be that easy, see the screen cap. This was an HST door/window sensor that is now seen as a keypad. Under 3.0.10.0 nothing was removed correctly when I tried to delete it from the original Z-Net. I got rid of the door lock, but this device refused to act correctly in the "remove" operation. I guess today I'll see if .11 removes correctly.

[randy]

That looks like a node that is in your controller but is not an HS device. You should be able to "Import Node info from Controller and Scan Devices" from Controller Management to create the HS devices. Then you will have a Device to go to the Z-Wave tab and remove the node along with the HS Device.

[ewkearns]

Thanks again, Randy! That worked perfectly. Last time I was faced with such a problem I had to edit an x.ini file and I lost my routing table. No biggie, but this was a LOT easier.