I cleared the log, then tried 3 times to refresh a node. Actually did this 3 times before I took the screen shot. I see no activity related to trying to remove a ghost... but wow, the Zooz power switches (Ginny Desk and Jac Desk) are sure slamming the hub. Or at least I think that is what I am seeing.
And that's what I meant by over reporting power/energy events. Those surely keep your radio busy. If you are not planning on using power level to automate your home, I would simply turn off the reporting. Or if you use power, you can increase the wattage to report at 30-50 watts or something that is more meaningful to your setup.
While you were typing that, I had unplugged those zooz... get back to that in a minute.
Look at the log now when I tried a remove...
Ok, yes, I like the power reading on the desks. What I use it for is to at night when the power drops below 10 watts to turn off the desk. I have 4 of these. I can turn the power reporting off for two, but the 2 desks ones, (and they seem to be slamming)... wait, thought. I have a rule setup that says when the power drops below 10 watts for 5 minutes, turn off. So is it the rule that is causing the constant checking? How do I get around that? Oh and still got 3 ghosts.
No, it is the power reporting device sending reports. You want to only enable the reports you need. You don't want Power Interval, Power Percentage, Power Power Value, Energy Interval, Current Interval, and Voltage Interval turned on all at the same time. Pick one, and set it appropriately.
Ok, so two pics attached. First shows defulat settings, then the second shows what I changed the devices I don't need a wattage report to. Does it look good to you?
Unplugging a Z-wave device without properly excluding it causes problems as well. Some devices may still attempt to route through those unplugged devices, so that could cause nodes that are further away from the hub to fail. As result, the radio will be "busy" trying to resolve those routing problems, all while you are trying to remove the ghosts.
Ok, now I will just pull my hair out.
Ok, plugged back in... will try and change reporting parameters
For sure leave them plugged in.
For now, I would set them all to off, be sure to "Save Preferences".
When you get the mesh stabilized, you can then turn on "Power Report Value Change" or whichever one you want. At most, you might use two of these, but more isn't better here. And if you aren't using power for automations, leave them turned off.
...and hit "Configure" for good measure, to let the device know that you changed the preferences.
LOL, tape and glue. Can't be too sure.
Current Status.
Still have 3 ghosts. Will wait for Z stick on Thursday
Have the Zooz power things changed to no reporting, so no longer slamming the hub.
Now what?
Do I start adding devices?
or do I setup a group and see if it works?
How do I know my Zwave Mesh is good?
Thanks for all the help guys.
Not until the ghosts are gone.
Got ya.
Thanks
Add Tony Fleisher’s (@tony.fleisher’s) excellent Z-Wave Mesh Tool.
Easiest way to install is to use Dominic Meglio’s (@dman2306’s) excellent Hubitat Package Manager, if you aren’t already using it.
Thanks, but... do you know where I can find a step by step, and I mean every step on how to install something like that? When I setup SmartThings 5 or 6 years ago someone pointed me to a step by step on using that IDE, and everytime after that I pulled them out and followed step by step... except they forgot to say copy the "RAW" and that gave me fits for awhile till I figured that out and wrote "RAW" into my directions. Are you aware of anything like that? Thanks
Sure. We were all there, once. That’s why I suggested to install HPM first - most apps and drivers can then be installed (and updated) easily once HPM is installed.
The steps are at the beginning of the HPM link I posted, but it can be daunting the first time.
The Documentation on how to install user-contributed apps and drivers is here:
https://docs.hubitat.com/index.php?title=How_to_Install_Custom_Apps
https://docs.hubitat.com/index.php?title=How_to_Install_Custom_Drivers
Because it’s a user contributed app, here’s the easy way to install HPM:
-
Copy the following link to the HPM raw code:
https://raw.githubusercontent.com/dcmeglio/hubitat-packagemanager/master/apps/Package_Manager.groovy -
On your hub, go to the Apps Code page (from the drop-down in the upper left corner), click the button at the top right: New App
-
Click the Import button, paste the link to the HPM code that you copied in step 1.
-
Click the Import button below the pasted link, Click OK. The code will appear. Click Save button on top right. After a bit of thinking, the code has been installed.
-
Use the menu at upper left corner, go to the Apps page.
-
You are ready to install the App from the code you loaded. Click the Add User App button, choose Hubitat Package Manager.
It’s pretty self explanatory from there. Configure HPM for your system (security? Etc).
Then, from HPM main menu, choose Match Up. This lets HPM take control of apps and drivers it knows about that you have previously installed
Then, to install Tony Fleisher’s Z-Wave Mesh Tool (which HPM knows about), click Install, search by keywords, search for Fleisher , click outside the search field, click next, up will come Tony’s Z-Wave Mesh Tool. For some reason, the package has a similar but different name than the name shown by the program.
It’s pretty straightforward from here.
Ask if questions.
Thanks;
This will be today's project since I am waiting on the tool for removing the ghosts. (down to 2).
I have copied and pasted your instructions and links into a Word file for future reference.
Yall are the best.
Ginny
Just a caution: Dominic Meglio yesterday verified an issue with Match Up, and is testing a fix that seems to work. The issue is that the current Match Up seems to hang if any one of the multitude of packages managed by HPM has a duplicated package manifest. Apparently, some developer created a duplicate manifest this week. See the tail of the HPM thread for details.
So, until the fixed version is published, skip the Match Up step. Or, you could use the HPM code link for the fixed version at the end of the HPM thread instead of the link to the published released version I gave above.