Errors when running z-wave repair

hey all,

pretty new to hubitat, migrating from ST and been going room by room and adding my Z-Wave devices. i got to a point where i was seeing some lag in activating some devices and i felt it was a good time to run a z-wave repair to make sure the mesh had decent routing etc, and i'm now seeing Z-Wave Network responded with Busy message. as you can see here in a snip of the logs:

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:39:18.343 pm warnZ-Wave Network responded with Busy message.

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:39:18.333 pm traceZ-Wave Node 3C: Repair is deleting routes

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:39:18.320 pm traceZ-Wave Node 3C: Repair starting

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:38:58.334 pm warnZ-Wave Network responded with Busy message.

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:38:57.291 pm warnZ-Wave Node 3B: Repair failed to delete the routes (timeout)

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:38:17.277 pm warnZ-Wave Network responded with Busy message.

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:38:17.266 pm traceZ-Wave Node 3B: Repair is deleting routes

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:38:17.253 pm traceZ-Wave Node 3B: Repair starting

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:37:57.242 pm warnZ-Wave Network responded with Busy message.

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:37:56.237 pm warnZ-Wave Node 39: Repair failed to delete the routes (timeout)

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:37:16.215 pm warnZ-Wave Network responded with Busy message.

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:37:16.206 pm traceZ-Wave Node 39: Repair is deleting routes

[sys:1](http://hubitat/logs#sys1)2020-09-04 05:37:16.191 pm traceZ-Wave Node 39: Repair starting

i'm on a new C-7 running 2.2.3.142.

did my repair work or not?

-spike

Give it a rest for now. There is a new release coming out very soon with improved Z-Wave repair.

1 Like

hehheh. i just went to do the cold boot bc of the death loop of responded with Busy and lo! 2.2.3.144 is out now with some fixes for z-wave repair etc ... so i'll update that stuff now...

also thanks for the prompt reply on a holiday weekend!

There was a post after .144 was released that they are testing another build after .144 continuing the work on the Z-Wave repair, so you are still probably best advised to wait a bit for that release. :slight_smile:

1 Like

v2.2.3.145 is out

3 Likes
2 Likes

Call me Kreskin, prognosticator of the future!

1 Like

FYI, from what I've seen the advice from HE on C7 hubs lately is to do individual repairs, rather than a global Z-Wave repair.

So after you reboot from the update you can check your devices to confirm what' s working, what isn't, and then run repairs on the troublesome devices.

@bcopeland - that approach still stand?

1 Like

I too had to do the cold boot to bring back the Z-Wave controller from death. Going to apply the fixes this morning and see if it survives the next couple of days. I did validate that the paths to my Z-Wave devices looked good after the cold boot. I may move the Z-wave leak detector and try a repair to that device to see if the route updates.

With my new C-7 woke up to the busy message in my logs and nothing in the Z-Wave device list. Didn't apply the hotfixes yesterday that were posted, good thing I am only testing the migration patterns from C-4 to C-7 with 2 Z-Wave switches, 1 Z-Wave Battery leak sensor, and two Samsung Zigbee devices leak and button. Can't do the other devices or rooms until this thing becomes stable or the wife will have my head and it's long weekend :smiley:

1 Like

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.