I’ve been struggling for the past month trying to migrate from V1 to V2. Unfortunately, my Z-Wave mesh keeps getting corrupt and I now get the dreaded “Err 101: ZW module not responding” every five minutes.
The first time this happened, support sent me a new hub assuming it was a z-wave radio issue. So I have been sloooowwwwllly adding one device at a time and doing a repair after each. I got up to 100 and boom, it went corrupt again. Tying to fix dropped devices individually once it gets to this point is like playing Whac-A-Mole; another one or two drops in the next repair.
I’ve looked though all the other threads and it seems the best I can do is remove everything and add them back again. One thing I noticed that others did not mention is a “Failed to read protocol info” error showing up in the log randomly before a ghost device. However, I’m to the point it is not worth it and just junk it.
There is obviously a bug. It is frustrating that SmartThings is not able to manage the routing tables. Why don’t they expose them to the user? We could then help diagnose on our own and help repeat and/or isolate the bug. We need to be able to create a snapshot of the tables before and after including, excluding or repairing. If they go corrupt, then we should be able to just roll back to the previous. If corrupt, we can compare the differences and help determine the issue. In fact, why not automatically keep snapshots that can automatically roll back when corruption is recognized?
I’ve always advocated that if we could see signal strength in routing tables we could better understand where to place devices or repeaters or what may be causing interference.
Please tell me an engineer is working on this now.