2.2.6.133 - C-4 Hub won't update successfully

My development C-4 hub will not update to 2.2.6.133. I've tried 2x now, and the same thing happened in both cases. I get to the screen below and it never continues from there.

After the 1st failed attempt I did a soft reset, then rolled the platform back to 2.2.6.130 and restored the backup, which gets it working just fine on 2.2.6.130 again.

Tried the 2.2.6.133 upgrade again, and same result - this screen has been up there for 30+ minutes:

Rolled back to 2.2.6.130, and it is working fine on that version. :man_shrugging:

Mine updated just fine.

1 Like

In the end, since it is one of my dev hubs with no z devices I just reset it.

After that it went to 2.2.6.133 just fine. So maybe I goobered up the database at some point in the past or something.

No worries! My other 4 hubs upgraded to 2.2.6.133 with no issues.

2 Likes

How is 2.2.6 on C4? Anyone upgrade their production hub? Still on 2.2.5.131 awaiting feedback

I run 2.2.6 on all my hubs (2 C4, 1 C5, 2 C7). Other than the weird upgrade issue on the 1 hub, no real issues on my end with 2.2.6.

1 Like

My main hub is a C3. I also have a C4 (production) and a C7 (Development). All are running 2.2.6.130 without any issues. I have not tried upgrading them to 2.2.6.133, yet.

1 Like

I literally just had this on one of my C4's going from 2.2.5.131 to 2.2.6.133, it took something like 40 minutes to "verify" the update and then a similar amount of time to apply it.

I think mine was likely memory / load related, since it was one of my live system C4's with 60 or so ZigBee devices on it and been running for a month or so (free memory decline, slower UI, etc). I probably should have rebooted it first to give it a clean memory footprint, will probably do that on the other C4 when I update that one.

1 Like

Yep! I always do this as well, just to have as clean a system as possible before performing an upgrade.

I will point out, as I did in the other similar thread, that all reported cases have been C-3/C-4. That seems to be the common piece. Tagging @bobbyD

I think mine may be slightly different based on comments in the other thread. Mine did update fine in the end, just took longer than I was expecting.

2 Likes

I just updated my three hubs (C3, C4, C7) from 2.2.6.130 to 2.2.6.133. It took about 5 minutes per hub. No issues whatsoever with the upgrade process. I did take a backup and rebooted each hub before starting the upgrade.

2 Likes

Just for the record, I did reboot the C-4 that failed upgrade prior to doing the update.

1 Like

But no backup?

I always backup before upgrading. Not that that has anything to do with it completing or not completing an upgrade. :slight_smile:

1 Like

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.

4 Likes

C4 reporting in. I've been updating through the 2.2.6.xxx releases without a problem, though there did seem to be a failure to execute a rm4 or two on the first version. No problem updating to 2.2.6.133 or 2.2.6.134 ...though I held my breathe a couple of times.

1 Like

Hoping someone can help. I've given my old hub to a field hockey club to use in their clubhouse for HSM & door opening amoungst other things. It has been Hard Reset as I was advised to do. I've registered it, which has been confirmed.

However now the hub is saying it's not connected to the cloud & doesn't have the lastest firmware (not sure what version it has). And if I try to update the firmware it just keeps trying & nothing happens. Last time I left it for more than an hour, nothing happened. Is there anyway of updating it manually? Or anyone have any idea what could the problem be?

It needs to be connected to cloud to update. Perhaps Internet to the clubhouse is blocked, or connection is bad. Have you tried a known good Ethernet cable from the hub to the router? Has the router been set up to give the hub an IP via DHCP lease reservation? Can you reach the hub at that IP port 8081 ? It’s a bit unclear what steps you have tried except to Hard Reset and register.

If you can get to the diag tools menu at port 8081, you can “Download Latest Version” of the firmware.

1 Like

Thanks for getting back to me. I haven't tried anything yet, & difficult that it's not at home. I'll have to go to the club to investigate. Although I would have thought if the PC that is there is connected to the internet the hub would be as well, I'll have to follow the cables to see where there connected. I'll try to call over there today, Thanks again.

1 Like