A couple ways. If you leave that screen up on the phone it will show errors and start/complete messages there. You can also login to the IDE and look at the hub event logs.
I’m not an expert on meshes, but I’m thinking you’d only need one or two to hit the hub and the others to hit those and get repeated.
I logged into the IDE, found the logs, and found this from last night: “Z-Wave network repair started”. I saw nothing beyond that in regards to network repair. Should it have logged a “finished” entry?
yeah, there should be a completed entry
How long does the repair normally take? I did add about 15 devices or so last night. Guess I’ll give it another whirl
They are both certified Z wave plus hubs. They should have the same range.
The issue is almost certainly one that comes up whenever you are moving devices from one hub to another without the option of using controller shift – – you can only add about two dozen devices at a time, and then you need to give the hub time rebuild all the network tables. Preferably about three days.
Meanwhile, your new network doesn’t look exactly like your old network. Not all the repeaters are in the same places, not all the tables are built. And yes, it’s a good idea to run the zwave repair utility to speed up this process, and it’s essential to run that utility if you are using older Z wave classic devices, not zwave plus devices. ( note that vera automatically runs this utility every night. Smartthings only runs it when you manually start it.)
Eventually, after you have all of the devices added to the hub and it has had time to rebuild all of the address tables and communicate the appropriate pieces to all of the individual devices, it should work exactly the same way as the previous one did. But that whole process can take a month or so depending on how many devices you had.
If the two controllers support controller shift, you can bypass all of this, which is what you do when you replace one vera hub with another or one wink hub with another. But that’s an optional feature, and smartthings doesn’t support it. So you’re just left with having to have patience until you get your entire network rebuilt.
The one tip I can give you as a former field tech to speed things up would be to move over all of the repeaters first, adding them in order from closest to the hub to physically farthest, so that you have laid down a good backbone before you start adding the battery powered devices. But that’s up to you. A lot of people prefer to work a room at a time, and there’s nothing wrong with that, it’s just going to take a little longer.
See the following FAQ. Start with post 11 in that thread, then go back up to the top and read the whole thread.
And here’s the FAQ on Z wave error messages:
mine usually takes 10-15 minutes
It’s very different to run one on a well-established network and to run one when you are setting up the devices for the first time. The typical maintenance run for under 100 devices would probably be about 15 minutes. But a typical first time run even with only two dozen devices might take two hours. And even then you might not have all the battery operated devices updated yet.
We always used to tell people before Z wave plus to wait until the next day before testing for improvements.
From Dr. Zwave:
This healing process can take many minutes to even hours depending on the size of the network.
Vera support gives the same timeframe:
Hmm ok. I rebooted the hub and started a new repair. I get this below in the logs. Now to see if it finishes, since the last one didnt after 15+ hrs. FYI I currently have 25 devices, all hard wired except 2. I have about 20-25 more to add, but suppose I should wait before I add anymore.
If this one doesn’t finish after a few hours, try adding just the five hardwired devices that are physically closest to the hub and run a repair on those. That should certainly finish in under an hour. If it doesn’t, I would get in touch with SmartThings support.
By that I assume you mean to exclude and delete the other 20?
Yes. Sometimes you just have to start clean to troubleshoot exactly where the problem is, and by only adding five hardwired devices that are physically closest to the hub, you’ll be able to verify if the zwave radio in the hub is working correctly.
One question about verifying the completion of the repair. Is there a good way to check the logs other than looking at all events? I have about 40 ping events already after the repair event started. By the time it finishes (if it does), it will likely be buried in a mound of events, which would required significant effort to try to determine if it finished. Sorry for being such a noob.
Are you using chrome? on Windows? Can you do a ctrl-f and then type finished?
Yes, I can do that. But i started a repair last night and this morning when i looked through the logs I had hundreds of other events on top of the “started” event. Since 200 is the limit on what it displays, I had to keep scrolling all the way to the bottom, about 10-15 times to get it to display it all. Thats fine if thats what I need to do, but just didnt know if there was a repair status somewhere out there that I could look at instead, or even the ability to download the log and open it in Notepad++ or something. I look at logs all day for my job, and logs in a browser arent as fun to deal with.
Its never taken more than 15 minutes for me.
Maybe reboot hub and try again.
Do you see any zwave module reboots due to exception?
If there was a zwave module reboot the zwave repair would be ended early, maybe without a finished message.
Ahh, maybe thats whats going on. Right after the repair started, it did rejoin a device. Log screenshot below. Also, I started this repair right after a reboot. I rebooted through the IDE, dont know if thats any different than rebooting from the hub itself (through the button on the back, or unplugging it). So should I kick off another repair?
I also have a device thats disconnected from being out of range (hoping this repair stuff fixes it) and one that cycles in and out of being disconnected, dont know how that might impact the repair.
I have a fairly small system by some standards - only about (30) Z-Wave devices ((24) ZigBee), but Z-Wave Repair runs are usually about 4-5 minutes.
that z-wave setup message kills the repair. try excluding that device and running it again.
Edit: Device inclusion/setup does end zwave repair without a finish.
I have 88 devices in all, not sure of breakdown between zwave and zigbee.