devices generating a lot of log entries...
Ghosts
The log seems to be full of motion events and related rule analysis. 8 motions in all
ALL logs... this includes events, device stats etc.... Likely something is flooding your mesh at this point.
How many associations do you have set? If configured wrong those could possibly be causing issues.
Also, next time when it gets bad before you reboot refresh the zwave stats. Look for anything with a high RTT or a high number of route changes. Also a high PER count could be a clue.
One problematic device can bog the whole thing down and grind it to a hault.
The third party app zwave mesh tool can also show the number of messages and lets you sort by anything to find the worst devices [BETA] A Z-Wave Mesh Tool [C7 and 2.2.4+ Only]
4 switches. Basic direct control loads. All seem to be ok and the problem predates this.
What do these mean and what is considered high?
I have this installed, will have to look.
Heres the latest: I restarted the hub at about 12p and all was still good when I went to sleep. Woke up to find everything bogged down again. I don't see anything weird in the logs, just motions and temp sensors checking in.
Is there something that happens overnight on the hub that would kick this up?
Also, coming from Vera I'm used to seeing commands in the log like attempting to reach the node but unresponsive. Unless I'm missing something all I see here is an on or off command but nothing as to whether it's successfully made it or not. And obviously I am standing at the switch and it did not make it through, or it is delayed by 5 minutes.
Observation: Triggers show up instantly and their associated actions as well. Button trigger recorded, switch off command set instantly, nothing happens at switch. (Just realized that button is zigbee so maybe that's why it's recorded instantly)
I also realized that I have two switches that need to be replaced, one of them is a Jasco that is giving me the click of death, I have that air gapped but I force removed it from hub this morning. I have another micro switch in a hard to reach place that does not seem to be responding to anything so I have to get up there and replace it again. I force removed that one as well.
Restarted the hub and let's see how long we make it now.
When you force removed these, did you do it from the devices page or the z-wave details page?
Device page...and they're back. The micro switch came back and discovered its name, clearly it's communicating but it's not controllable. It's in a very hard to reach place so I have to get up there and physically remove it.
And some other ghost device was created. (Edit, looks like it's a physical device and it's that device that was air gapped, somehow it got pushed back in, I just removed it completely from the wall now)
Force remove from the device page does not remove it from the z-wave radio. So yes sometimes the hub will re-discover it on its own and add the device back again. To totally get rod if it you have to get the node removed from z-wave details.
RTT = round trip time. Anything over 100ms could be considered slow. You are looking for outliers. If one device has a really long RTT it can bog down the entire mesh while that device is taking up air time.
PER is supposed to be "packet error rate" but I don't know what it is a rate of, as it seems to just climb indefinitely. I think it is more like the error count (not a rate). Anything greater than 1-2 should be investigated.
Okay, I'm thinking I found my two culprit devices, one of them I was able to physically remove from the wall but I need to get to the computer to remove it via the stick as it is not removing on the hub. The other device is in a harder to reach place so I will have to get to that, I disabled it so at least it's not part of scenes but it definitely keeps rediscovering itself and shows all its neighbors yet will not respond to commands. I will have to get up there and remove it and then try to exclude it from the hub.
Sometimes if you reboot the device by power cycling it at the breaker they start working again. Might want to give that a shot first.
Ok, I'll try. It is in the Attic and I had similar issues with Vera and this device being unresponsive. Could there be a cold issue? It's a cold attic and it's below freezing outside.
Interesting, that made one ghost come back to life. But I seem to have two of the same switch now, one doesn't work at all but has same device name.
Either way, system seems to be responsive again
Thanks for all your help.