How do you do it ? I have not seen anything that clearly says how to do it. But I have seen several post that read "try, that or if that doesnt work try this other thing." It kinda reminds me of holding aluminum foil up to the rabbit ear on our old black and white TV to get crappy reception.
Seriously, near as i can tell this seems be about a 30 to 60 minute process that has to be closely monitored, not like a regular update. So what the correct answer?
How do I recover from a collapsed mesh? I never let my mesh get to that point. I am only using reputable devices and only introduce new devices in the mesh in very small batches or single devices, then monitor them to make sure they are not negatively impacting my mesh. If they are spamming my radio uncontrollably, they go straight to the trashcan. Life is too busy as it is, to spend countless hours trying to make a bad device better.
No. How do you do the firmware update. I've seen lots of tribal rituals posted, but no clear direction. Just clicking update firmware into enough because I just did that and after 20 minutes im still on the old firmware version.
No, the aluminum foil has to go on your head.
Clicking update was a slow process for me. I walked away and took care of other stuff. When I came back, it was done. Sorry, not sure what the exact timing was, but 20+ minutes is not outside of the realm of possibility. I recall seeing a % update, though, which is why I walked away.
Check out this thread:
Seriously, it took me almost 30 minutes, but I didn’t have to start over. It may be because I’ve got a fairly small Z-Wave mesh, about 30 devices, and 8 are repeaters (6 Ring Extenders Gen 2, 2 Aeotec RE7).
From the thread that Bobby pointed to, the key step as recommended by HE was to sit on the Z-Wave page for several minutes (some waited as long as 10) before starting the update. Launching the Z-Wave Details page results in a lot of background actions, and you want those done before you try to start the update. Of course, YMMV.
Not my experience at all...
I have two C-7, both got the ZWave firmware update as soon as I could get it and it went smoothly. Both finished rapidly... probably less than a minute.
Obviously 50% is the download. The actual write to the SOC (Zwave radio) was completely missed the first time since I had never seen the process before and the 2nd time was equally unremarkable and so there was nothing to memorize 
My kept locking the page up when i clicked on firmware update. I waited as long as 5 minutes before deciding to refresh the browser.
I need to sit on page longer?
Using latest Chrome browser
Try keeping a log window open.
It could take over 5 min.
How long did you wait on the Z-Wave details page doing nothing before you tried to start the firmware update.
I didn't wait at all. I went to the page and clicked update. Took around 10 minutes to update. Did both my hubs in the same way. Both my hubs have vastly improved zwave performance now.
Like me, you're one of the lucky majority that is able to update without issue.
I did update the Hubitat Z-Wave firmware a couple of days ago.
it is interesting that I got an email from Inovelli telling me "There have been many problems with the 700 series controller chips that are in several Z-Wave products, but Silicon Labs may have figured it out" and suggested I was sure to have updated the Z-Wave Firmware for the Hub. As mentioned above, I did that. However, the update had the opposite result as many of my Inovelli Red Dimmers got faster, and some much faster, from 9.6 to 100, but 2 of my Fan + Lights, which have 700 chips vs the 500 chips in the Red Dimmers, got much slower going from 100 to 9.6. This seems particularly disturbing to me as one is in the same room as the Hub so I have no idea why it not only slowed down, but also no longer is connecting directly. Here are before and after screen shots:
This is the one in the same room as the hub:
Before:
After:
Here is another Fan + Light that got slower:
Before:
After:
This is a Fan + Light that was, and still is, slow:
Before:
After:
This is not a 700 chip, but is an Inovelli Black with scene control.
Before:
After:
Slow connections are only a problem if you see an actual problem w/device performance - significant delays, etc., that affect your devices/automations. I had a device (light switch) that was a 9.6 for months and months, probably years, never had a single problem w/it not performing normally in automations. Unless you see an actual issue best to ignore what you see on the Z-Wave Details page. Being patient now and waiting several more days would be what I'd do right now.
Options if you are having performance issues w/automations/devices after the update:
If it was me, I'd wait several more days. If then I'm sure I have an actual problem that needs addressing, try 2-4 above.
So 7.17.7 fixed another problem for me today - I had an Aeotec Recessed Door Sensor Gen 5 that refused to report battery percentage. I was going to send it back under warranty as it's just never worked 100%.
Anyway, I replaced it with an Aeotec Recessed Door Sensor 7 today and was just having a play around with the old gen 5. I thought I'd try updating the FW but couldn't flash it with my z-stick. So I re-paired it with my C7 and I was shocked to find it works 100% now! Battery reporting and all! 
WTF, I'd removed and re-paired it several times previously, however, under 7.17.7 now it works perfectly! Bizarre!
That's great. A device saved from the scrap heap is always a nice thing. And now you get to choose another door you want to drill holes into. 
Yep, the external laundry door just got an upgrade! 
Download the Hubitat app
