Just for the record I love my Vera and have alot of fun with it (her?) but just tossing out some observations in case they would be helpful to others,
Having previously posted in other threads that my “repair network” worked well (when someone had run it without it finding neighbors correctly) I have had quite a different experience recently, having had my first complete lockup I had to go onsite and reset the dongle (first tried resetting Vera) which seemed to clear things up, then I decided to run a repair network (see components below) just to tune things up, well that mangled my network badly, I had set my HSM-100’s to the minimum (6 min) wakeup (and waited for them to update) then ran the “repair” it ran and reported like all was well and completed, but three of the sensors had no neighbors reported except Vera (each have at minimum 3-4) then after a few more minutes one of those reported neighbors (when I rechecked) and inexplicably the other 2 then changed their display to “generic” devices, no longer having the sensors and device menu options that belong to them, I continued to just wait as I wanted to see the conclusion of all this and after several minutes 1 of the 2 appeared as a new device in the device tab and it was correctly identified but when added never communicated correctly with Vera nor showed it neighbors the third never got recognized correctly and then dissapeared altogether, the final solution (of course) was to nuke the network and start from scratch and (knock on wood) all seems to be working well now …
Other observations: it makes sense that as one adds devices to Vera that the system responds more slowly to commands, but what I hadn’t thought about is the huge impact of Vera being busy with other jobs especially (it seems) with tasks that can not be carried out immediately and so have to be queued (like updates to a battery sensor wating for a wakeup) some informal observation leads me to believe that long delays and errors are much higher during this multitasking so it may be beneficial when making network changes not to throw too many things at “her” at once, (just guessing here) maybe that is the price for not having to run a full up computer to handle the system is (perhaps) the lack of pure horsepower means the system can get overwhelmed at times, no doubt much of what I described here may be related to the particular communication challenges of battery powered sensors of which I have several, … in my latest configuation it takes about 4-5 seconds for Vera to turn on a light (unless it is configured directly “scene capable” of course) but if I make system changes and try to do the same it may take up to 20 seconds or more, quite a difference
I, too, am in love with Vera, but our relationship has its ups and downs :-\
Like you, I have had really bad luck with “Repair my network”. It always takes me days or weeks to get everything back to where it was before, and as far as I can tell, it never really makes things better. So why do I try it? Desperation.
I don’t think I’ll ever do a repair again. If I’m going to have to rebuild things anyway, I just as well rebuild without the “repair”.
The network heal process works fine. Uncheck the Re-configure devices when done and it should work ok!
Thanks, mcvovidiu, for the tip. I had hoped there would be a secret that would solve all my problems.
So now I have a small UI change request: change the label on the “Re-configure devices” check box to something that I can understand. I suggest: “Destroy configuration of all battery operated sensors, and wreak other miscellaneous havoc on random devices and controllers.”
hahahahahaha, too funny … I appreciate the tip mcvovidiu, hope you can appreciate the truth of Rancho’s words!
question - if we are supposed to untick it, why is the default behaviour to have it ticked?
Are there consequences of having it unticked vs ticked?
No problem : ) was a good joke.