It would be really helpful to nOObs like myself if after selecting "Zwave Repair" in the Zwave settings, if the screen would automatically go directly to logs, instead of just text saying running zwave repair with no way of verifying that the test is "still" running. During my initial setup of Hubitat (about 2 weeks ago) I would run a wave repair after including a few devices being "used to Vera" those statuses didn't accurately update so I was applying it here too, so I would "assume" it had completed and begin adding more before it had completed, and repeating this cycle.
Later I figured out having two tabs open on the tablet, 1. For device inclusions, and selecting zwave settings, etc. and 2. with the logs running, so I can wait until I see the "zwave repair finished" before adding more.
There is an indication in the tiny notification icon in the upper right corner of the screen.
and when selected
1 Like
After the previous update, "that indication" ALSO said my hub needed registered, when clicking it the screen went to say "Hub is already registered" , yet "that notification" stayed there no matter how many times i did what it stated.......My comment list the reasons as to why it would be helpful, instead of doing as you state in just relying on "that notification" to make visible "the actual activity" of it running for new people especially to verify that notification is actually doing what it states, and not stuck doing nothing and wasting your time waiting for it to change. Especially those from coming from Vera, to where the notifications of the device you were including never changed for hours.
You shouldn't need to constantly run repair. The repair in Vera that ran every night was mostly unnecessary.
1 Like
This is correct. @waynespringer79, just run a repair when you change something in the Z-Wave topology. Otherwise it's not needed on a regular basis.
Open another tab with the log. Run repair and then flip over to the tab with the log open in it.
Very easy for you to infer how "correct" it is being that you are well versed in how the system operates.......I'm referring to NEW people just migrating over (not to mention it would be one less step for existing users), New users WOULD BE changing something repeatedly migrating all their devices over just as I did, and there is no documentation for new people on how the process works, nor is there any way to figure this out without going through many different processes to "learn how it works" My "recommendation" wasn't a debatable topic whether it "works" or not, it was strictly aimed at making the process easier for those who have zero experience in the new platform.
I think that's a good suggestion. If you are building a new system from scratch, it would not be so much of an issue but if you are transitioning from one hub to another you are disassembling one mesh and assembling a new one. I know I struggled when I made the move from SmartThings - the conventional wisdom is to build out from the hub but if I migrated the devices closest to the hub from ST to HE it would have completely messed up the ST mesh. In the end I used this as an opportunity to purchase a few newer smart outlets and I installed them on HE to create the routing core, if you will.
Of course, all my careful planning of a gradual transition went out the window when I accidentally deleted my most important automation from ST by hitting the wrong button. Then it became a panic to move the remaining devices over and get them working. Sort of like what our Iris and Wink alumni have been doing.
1 Like
That was my reason behind the recommendation, as I ended up with my zwave radio locking up from trying to include devices during the repairs still running, thinking it was completed, Then going through a whole process of force removing devices and trying to reset them not knowing my zwave radio had stopped, then after support got the zwave radio back working, I had to redo everything I done when the problem occurred, which ALL would have been prevented had I had this open up as I suggested providing the information to prevent my own errors from happening....Learning about the logs section (which never worked in Vera so I wasn't accustomed to looking at it previously) I "learned" I could actually see when it had completed.
1 Like
https://docs.hubitat.com/index.php?title=How_to_Build_a_Solid_Z-Wave_Mesh
There are documentation links all over this forum. There's a documentation link in the getting started tutorial that's part of the hub setup. There's a documentation link on the hubs home screen. Also, if you click the question mark in built in apps it takes you to documentation for that app.
It's not complete and is still in the process of building, but there is documentation.
ALL of which you must "search" for and new users don't know "what" to search for.
Not sure what you believe the issue you think this would cause having a tab automatically open when selecting zwave repair actually is? You provide ample information as like I previously stated, that an experienced user knows where and what is available, and my suggestion isn't targeted to experience users, nor can I see any issue caused by the recommendation happening.
FYI: Even that link you provided mentions nothing about checking the logs for status of the zwave repairs it states you should run, and making sure they have completed before including any more devices.
It's a good suggestion. If you'd like to add it to the Wiki, you can request access and become a contributor or you can send a note to support@hubitat.com with your suggestion.
It's good to voice your opinion here on the forum, but there's a lot of posts here. You must understand that not everything written is going to be seen by the staff, at least not in a time line you might be expecting.
1 Like
Thanks, but I'm far from being experienced enough to be any way a contributor. Hell I don't even know what "wiki" is.....if this suggestion makes it up to the top good, if not, at least it's here so if anyone else experiences the same learning pains that I've had, may help someone else with a direction to look for..
Technically it's considered browser hijacking when a website (app, whatever) forcibly opens a new page or tab without the user's consent and is often blocked by most modern browsers.
With that said, I wouldn't mind seeing better messaging on the Z-Wave repair progress in the same window. Maybe like a console or something like that that mirrors the status that gets piped to the logs.
If you tag @bravenel, @chuck.schwer or @bobbyD when you have a suggestion for the Wiki, I'm sure they will ensure it gets added if they think it's appropriate.
Wiki is short for Wikipedia. It's online documentation basically that approved editors can contribute to. It keeps record of additions and changes that everyone can view.
https://docs.hubitat.com
is the landing page.
1 Like
Wiki can be short for Wikipedia, but wiki itself is a Hawaiian word for fast/quick. And is the origin of the name Wikipedia. 
3 Likes
