For some reason every time I update my hub it seems to hang on “extracting update complete”. After several minutes I end up ending the update and hard rebooting the hub. It then after a few minutes with the blue light on turns green and when I log in it is updated. Why can’t these updates work properly?
I'm guessing that not many people are having this same issue., as its the first I have heard of this. Have you tried doing a reboot with advanced option to rebuild the database? After power off's (as opposed to shutdowns) can corrupt the database, and can cause many different symptoms. This may be one of them.
Thanks, yes I know powering down can do bad things but otherwise it just keeps spinning. Every time I’ve done it this way it’s been ok and successfully updated. But I feel I’m tempting fate… don’t know what I can do differently.
That said I’ll try what you suggest. Thanks!
Also, if it seems like it's taking a long time to download the updates, you might want to go into network settings and change "auto" to "fixed" (or "fixed" to "auto").
Sometimes, if it takes a long time to download the update, it doesn't quite do it correctly.
I just updated to the current level 2.4.4.132 yesterday, from 2.4.1.177 It did hang on extracting update complete for a long time. I just walked away for a bit and when I came back it was booting to the new version. You probably just needed to wait longer. I assumed it was because I was so far behind on updates, but it certainly took a long time for me as well.
2 Likes
Ah thanks thats very helpful to know. Just too impatient i guess!
You can also click the "home" icon and then go back to the settings -> update menu (or just try refreshing the browser page). Mine hung like that also on the last two updates (C7). When I clicked the home icon, and then when back the status moved forward. I noticed the same on home assistant. So, I am thinking it may just be a browser issue.
For the record, if I were going to pull the plug, it would NEVER be in the middle of an update unless I had tried everything short of that and had waited for more than 20 minutes. Even then, you can bet I would be posting here for advice before doing so. One of the best ways to break things is to power down during an update. Pulling power is not good most of the time. Pulling power during an update is even worse.
I have only pulled power twice wothout soft power off since owning my hubitat (~5 or6 years). Any time I do that, it is immediately followed by a reboot with the rebuild option selected.
Exactly. That is why I walked away and waited it out and it completed fine on it's own. I left it for about ten minutes, and the hub was booting and doing the new version driver conversions at that point when I got back.
I also replied to the wrong post apparently..... LOL Is it too late in the day to claim not enough caffeine
I figured. I was aghast when I read that @OCfarmer said they had hard rebooted the hub during an update, but I guess it all worked out OK.
1 Like
I agree it’s something I would never normally do. However, what I don’t understand is why it stays so long on “extracting update.” Every other update process I’ve used first don’t take nearly as long as this one, and they also display other messages after extracting, like applying the update, cleaning up, etc, Every time I update Hubitat it acts like it’s stuck… for example I’m updating my other Hubitat hub and it’s been going for over 20 minutes now still showing extracting… doesn’t anyone else wonder about this, or is it just impatient me?
Ok, the update finished… I guess in future I’ll just start it and walk away for ½ hour. 
2 Likes
Thanks for the advice, however, I was updating through the app, not the browser, fwiw.
