So the question, while 9 minutes a repair is great, less than the hour the math suggests.
Can the zwave repair be modified to…
Suppose instead that the repair took twice as long, 18 minutes, but logic is to wait until all devices have no errors.
And the logs could report status as it goes,
Example log messages
all devices contacted successfully
Devices still updating neighbors
5 devices still updating neighbors
4 devices still updating neighbors
All devices updated
Zwave repair done, no errors
Well now we are just asking for more and more functionality lol!!
My guess is that there is a limit to how much the hub knows about why the errors are occurring.
Usually in my case, it is just time, I need to re-run zwave repair enough times over a long enough time, that the devices are all able to find all of their neighbors.
Most of the time in my case, the zwave repair errors does not require me to do anything with the end devices, just re-run zwave repair.
In fact there have been times when the device, lets say a zwave in wall dimmer, in which the device needed to be power cycled to correctly work (air gap or breaker) but the zwave repair for that device was clean!!!
The device did need a power cycle to properly work, but the zwave repair was clean before the power cycle!!
In other words, the zwave repair did NOT detect that the device was not working correctly.
Yeah, that just shows the repair is effective only so much. Just because the device is updated in the routing table, doesn’t mean it transmits the other commands properly.
(www.rboyapps.com - Making SmartThings Easy!)
I had suggested a feature years ago which was being considered but don’t know what happened thereafter. Instead of having the user run zwave repairs manually which can be painful for many, when the hub detects degraded communications it should automatically run a zwave repair. Or automatically schedule a z-wave repair once a month at the dead of night, that should be simple enough to keep things running smoothly.
That’s a great idea! Except that until the system can be enhanced to run a zwave repair and fix all errors in one zwave repair, running zwave repair automatically has the possibility of leaving the mesh in worse shape.
This would be true in my environment as it takes 3 or 4 zwave repairs in a row to get a clean zwave repair.
Anyone having issues with Schlage locks not reporting status or at least taking an incredibly long time?
I am using @ethayer’s DTH and Lock Manager. I remember reading about changes related to locks so I figured I would try using whatever ST proposed as DTH. I excluded the lock and tried including it with the new app… fail… it found it as a Z-Wave Device, told me it did not support security features and the lock itself said the inclusion failed.
I excluded it again and tried to include it using the classic app. It took way less to find it and it proposed the default featureless DTH.
The reporting issue did not improve. The lock seems to report the status change only it you open/close it via the app.
The locks used to report their status way quicker a while back (possibly before this last series of betas). I have lots of beaming devices all around the locks, and I already ran several network repairs (no error related to the locks)
I thought it had already selected the default DTH but it had picked yet another custom DTH. I changed it to Zwave Lock with Codes but it still showed Cloud so I ended up picking Zwave Lock. While it seems to have improved a little, it is still way worse than it used to be.
I keep running repairs and keep getting lots of “errors” reported for varying devices. Things appear to be working however, regardless the number of times I run the repair, the errors do not decrease, they go up or down each time.
Ignore the “Zwave Controller” as it is the HomeSeer USB
Zwave stick I use to update device firmware. The other devices shown keep changing so there doesn’t seem to be a connection with one specific device or area. In the past the behavior was different and issues had a repeating pattern and would tend to decrease by running several repairs.