Cant upgrade from 2.2.6.131 to 133 - Hub Unreachable after update

One of my hubs 'USA 42' wont upgrade to latest 2.2.6.133. Was running fine on 131.
It never completes the update but if you access the hub it has a startup page (below). But every button eg Settings just redisplays this page. Online find.hubitat.com finds the hub OK. The startup % never shows ie 20% 25% etc. But the UI below does after a time

At port 8081 it shows 133 and I can revert successfully revert to 131 but still can't update as such.

image

When that happens is your ui url some TOS at the end?

My failed upgrade yesterday was similar, and when I could get into the UI, the url kept redirecting to a url ending with (I think) /#TOS .

Yes - sorry I should have included that info - did you fix it ?

http://192.168.1.42/#TOS

Ahh - seen the other thread....

That's exactly what my C-4 that wouldn't upgrade did.

Never resolved it - since it was one of my dev hubs with no "z" devices I just factory reset it and moved on. Went to 2.2.6.133 on a factory reset (which is what I would expect).

Seems like there is a real upgrade issue on some hubs that is new to 2.2.6.133. Hubitat will need to figure that out I think...

1 Like

Interesting that both reported cases of this were C-3/C-4.

My C-7 is doing the same thing. All the butons go back to the main page .
The the hub goes unreachable. It does find it when I do find my hub.

Tagging @bobbyD in case he is not aware of this.

3 Likes

If you see this after an upgrade, please go to http://hubs.ip.address.here/hub/acceptTOS
It will return an empty page, and you should be set going forward.
Not sure how this happens on an existing hub, It shouldn't be shown if there are any apps or devices.

2 Likes

I believe I’ve got a repeatable test case here. Thank goodness you had posted about the corrective acceptTOS URL, because I had a moment of panic.

C-7 running 2.2.6.134, hours after successful update from 2.2.6.133. This was not an update from 2.2.6.133 that caused the issue, but may give some insight where to look in your restart code.

TL;DR: soft reset seems broken in 2.2.6.134, causes loop with TOS screen rather than allowing restore from backup.

Fix:
http://hub.ip/hub/acceptTOS
When blank screen appears, then
http://hub.ip
then use restore from backup link at bottom of screen.

Background: I was noticing an explosion of Null Pointer Exception errors in the logs from a Rule that accessed an attribute that I had inadvertently deleted in a community driver I was modifying. That part is not important, just background.

So, I fixed the driver, did a backup (I’m OCD about making backups before and after any change), went to port 8081, did a soft reset, that worked but did not boot, just showed the initializing page without an xx% indicator, just the solid light blue line, message to “please wait”, I waited 1/2 hour, but the cows never came home. So, went to hub IP address, got the usual screen expected after soft reset finish. However, when clicking the link at bottom of page to restore from backup, instead got the screen wanting a TOS accept.

Hub was still accessible at port 8081. Was able to shut hub down cleanly, power down, power up, TOS problem still there. Was able to restore previous firmware version (2.2.6.133), several versions were available (I’ve got DB backups for everything, no devices added recently), but choosing 2.2.6.133 made that firmware restore, showed to be running 2.2.6.133, but stuck in TOS loop still. Used Diag tools to download latest version, successfully downloaded 2.2.6.134, but stuck in same accept TOS loop.

Then tried the URL posted above:
http://hub.IP/hub/acceptTOS
got blank screen, then went to
http://hub.IP

Got screen with link at bottom to restore backup (as usually happens after soft reset), clicked the link to restore from backup, and everything proceeded normally.

Hope this helps you find the issue, @gopher.ny
I’m back up and running.

Hotfix is coming.

2 Likes

FYI - Just had this happen on a brand new/out of the box C7. Powered it up, went through initial setup, upgraded platform, stuck at #TOS.

Your link/workaround fixed it though.

1 Like

Having the same experience as JasonJoel. Brand new C7, added a local user, upgraded, /#TOS max redirects problem. URL above doesn't work I am guessing because I have a local user so it doesn't mark the TOS as accepted (I am not logged in). Will try a factory reset