Unfortunately, woke up today to 20+ nodes failed.
Tried reboot, turned off and on, soft reset, restore from backup, new positioning of hub, etc. Nothing seems to have worked.
What does this mean:
Has anyone tried to do a zwave repair to see if they have any failed nodes?
If so, is there any alternative to exclude, re-include procedure to get them working again?
Sometimes air gapping the device will cause it to reconnect.
Air gaps exist only on dimmers... most of these are switches...
Have you done a zwave repair lately? Any failed nodes?
Does it make a difference?
Air gapping is just a quick way of removing power to the device, can do the same thing at the breaker box if necessary. ZWave Repair, particularly on the entire mesh, generally isn't the solution, at least on the C7 - better off trying a Refresh on the individual device.
But, have you run a full zwave repair?
And, what does it mean when it calls a node failed or unreachable?
Furthermore, I have tried again to control the device from the device page.
If I can, I've tried to repair just that node. Seems to work now. ????
Not sure why it has changed?
I ran a full mesh repair a couple of times before I really read up on the purpose of it, and discovered that it wasn't doing what I initially thought. A failed or unreachable node is basically one that doesn't respond in the time frame.
Single node repair is generally more effective as the node isn't competing with all of the other nodes to try and determine an effective route to the hub.
Sounds like you may have had a power blip that took a few key nodes out of the mesh and the mesh hadn't recovered when you looked at it.
First of all, just 7 minutes ago:
Then with no changes, 7 minutes later:
Does "repair" have any value?
This was a single node repair.
Guessing here, but it looks like the device is currently at the edge of the mesh (due to physical placement or the failure of other nodes on the mesh) and is losing connection to the hub. May want to ask @bcopeland his opinion though.
Thank you for your thoughts, and assistance, @thebearmay !
I guess it would be appropriate for @bcopeland to weigh in for some questions:
Are there any situations where a full zwave repair is called for?
If the device is responsive from the device details page, does it make a difference if the zwave repair shows that it's unreachable?
Does unreachable make a difference, or does it depend on the current zwave traffic?
When should you exclude and re-include? Does the route make a difference?
Sure.. But your mesh would probably be in really bad shape for me to recommend it, and it may take many attempts to fix it..
If the device is responsive, then it is probably fine and may be showing unresponsive due to some difference in how it handles NOP packets..
It can actually be traffic dependent as there is a timeout on the NOP requests..
If you can no longer control the device
Download the Hubitat app
