Support was able to waive a magic wand and fix mine. Don’t know what they did, but it worked. I didn’t have to start over.
Mine just started working again, no idea why.
Nooo! Don’t do this yet. I am also the other unfortunate guy with similar fault. Z-wave power cycle and module non-functional a couple weeks back.
I find that reboot the hub won’t bring the z-wave back but disable and then Enable Z-wave module will give you enough time to exclude most of your z-wave repeaters.
I still have about 4 ghost z-wave devices when doing a z-wave repair and still waiting for support to remove them but since the z-wave cycling stopped. I am not rushing support.
1 Like
Just had to call out the troops Steve. Now you have a team to work with. I’d be curious to see what you and Ray come away with.
Part the Red Sea and save it.
My guess is that Steve is quick and already pressed the detonator, or maybe just maybe he is taking screenshots of everything before he pulls the trigger 
Nope, not yet. I’m giving support a chance to respond. I doubt I’ll hear from them at all over the weekend.
Cool so can you try what Ray stated in his post? Does that work on your hub?
Perform the Disable / Enable as many times as it takes to exclude / delete everything. So no trace of zwave is there.
And dawz and mopars posts are very promising.
@dawz2 and @mopar_mudder thanks for chiming in and replying.
Think that might give Steve some hope for 2018.
Thanks for trying but unfortunately the module is going to a failed state in under a minute from being enabled. It’s not responding to any commands. Despite having a minute I can’t even get general device exclusion to kick on before the module dies.
How much time before it fails again on yours? How many Z-Wave devices were you excluding?
Guess he’s really not lucky. I have around 30 repeaters and I don’t remember how long before it failed again but more than a couple mins for sure. I excluded 5 at a time for isolation.
Roughly 1:12 with 3 Z-Wave power cycle events in between.
2018-01-05 3:48:30.832 PM EST
moments ago HUB zwStatus module failed Z-Wave module failed
2018-01-05 3:47:18.826 PM EST
moments ago HUB zwStatus ready Z-Wave is ready
I have tried activation exclusion 4-5 times during that period without luck.
My guess is that the failure is tied in with the number of devices and with the butt or boat load of devices he has in his system, this plays into the time it is dying again. Just a guess.
But I’m guessing your module failure stopped at some point as you got through your 5 at a time exclusion, ya?
If that’s the case, Steve I would remove them a couple a time. You have nothing else to do. Get it to a point that the failure / zwave function stops with that error. My guess is that this is not a hardware failure, based on all 3 of what these guys have gone through. support fixed one, the other magically started working and Ray was able to exclude a few at a time and I’m assuming the failure stopped and he now just has zwave repair issues.
I have a feeling support can fix this, getting them to respond has proven difficult. Unfortunately I’m stuck, I can’t get the hub to go into exclusion, so I’m totally dependent on support.
You are in the US right? Get them on chat and give them your ticket number.
My cycling was caused by the Lowes plugs.
Here was my latest z-wave repair and the ghost devices. Haven’t done one lately cause I am scrared 
2017-12-30 1:52:04.666 PM PST HUB zwNwkRepair finished Z-Wave network repair finished
moments ago
2017-12-30 1:51:32.154 PM PST HUB zwNwkRepair failure Network repair for DR frontyard Plug Monoprice [86]: Failed to update route
moments ago
2017-12-30 1:51:20.931 PM PST HUB zwNwkRepair failure Network repair for device [83]: Failed to update route
moments ago
2017-12-30 1:51:08.462 PM PST HUB zwNwkRepair failure Network repair for device [7B]: Failed to update route
moments ago
2017-12-30 1:50:58.355 PM PST HUB zwNwkRepair failure Network repair for device [7A]: Failed to update route
moments ago
2017-12-30 1:50:56.451 PM PST HUB zwNwkRepair failure Network repair for device [79]: Could not assign new route
moments ago
2017-12-30 1:49:20.812 PM PST HUB zwNwkRepair failure Network repair for device [58]: Could not assign new route
moments ago
2017-12-30 1:47:06.286 PM PST HUB zwNwkRepair failure Network repair for device [0D]: Could not assign new route
moments ago
2017-12-30 1:42:10.271 PM PST HUB zwNwkRepair failure Network repair for DR frontyard Plug Monoprice [86]: Failed to update mesh info
moments ago
2017-12-30 1:41:30.345 PM PST HUB zwNwkRepair failure Network repair for device [83]: Failed to update mesh info
moments ago
2017-12-30 1:40:18.251 PM PST HUB zwNwkRepair failure Network repair for device [7A]: Failed to update mesh info
moments ago
2017-12-30 1:39:42.299 PM PST HUB zwNwkRepair failure Network repair for device [79]: Failed to update mesh info
moments ago
2017-12-30 1:34:20.735 PM PST HUB zwNwkRepair failure Network repair for DR UDW Light/Motion Monoprice [77]: Failed to update mesh info
moments ago
2017-12-30 1:30:40.348 PM PST HUB zwNwkRepair failure Network repair for device [58]: Failed to update mesh info
moments ago
2017-12-30 1:12:22.860 PM PST HUB zwNwkRepair failure Network repair for device [0D]: Failed to update mesh info
moments ago
1 Like
You should never fear doing a Z-Wave repair. This points to a major flaw in the SmartThings Z-Wave stack. Z-Wave network repairs are often done automatically by some controllers as a means to keep the network healthy.
I’m not sure why Z-Wave is so difficult for SmartThings. I do know they’re working on improvements but I don’t know if they’ll help.
What time zone are you in Steve?
Get on Live chat and they will help you immediately version waiting for the email side.
Update: All fixed. Support pushed a newer firmware update to the Z-wave module in the hub which has eliminated the constant power cycling and has improved the responsiveness of all devices. My testing continues but so far I’ve been able to re-add 10 devices that became orphaned over the past couple days.
1 Like
Whallah…