C7 Stuck starting up

🛎️ Get Help Devices
1

I have a C7 that was working great for 2 years. I ended up doing a power cycle on it recently and it ended up with a corrupted database.

I've tried soft resets multiple times but when it reboots it gets stuck at Initializing Hub: 60% - starting UPNP . I also tried to reboot it into safe mode but that didn't work either.

I do have a hub protect subscription. Is there something I can do to get this working again, like a hard reset or would I be better to just migrate this to a new piece of hardware? I already pre-emptively bought a C8-pro in case that would work.

2

@support_team ^^^

3

As you have a hub protect subscription, submit a warranty ticket at support.hubitat.com

1 Like
4

I already did, how quickly can I expect a response from them

5

Most likely, within the week.

1 Like
6

If you can get to the Diagnostics Menu (http://<HubIP>:8081) you could try dropping back to the previous firmware level, and then update to the current version after a successful boot.

7

//

1 Like
8

ooops :flushed:

3 Likes
9

I'm currently running 2.3.8.140 which is what the backups were done on. Is there a way to get back to that version of the firmware if I go back one version?

10

backups don't handle firmware. You can restore from the diagnostics page on :8081 if something doesn't work out

2 Likes
11

Diagnostics menu should show you the versions that are readily available - generally the last 3 production releases IIRC.

1 Like
12

2.3.8.140 is the final release of 2.3.8, so you can get back to it...

To download a previous version do the following:

hupIPaddress/hub/advanced/downloadPlatform/platformVersionNo - examples below for 238 and 235:

- 192.168.20.2/hub/advanced/downloadPlatform/238
- 192.168.20.2/hub/advanced/downloadPlatform/235

Then go to the diagnostic tool and click Restore Previous Version and you should see 2.2.8.140 available
- .140 was the last released iteration of the 2.3.8 platform version

1 Like
13

Ok, I just went back to 2.3.8.138, Still had a corrupted DB afterwords and did a soft reset and am still in the same place as before. Would it be worth clicking the "clear past logs" on the soft reset menu or is that considered a bad idea?

14

Since you have hub protect, why not do a full reset, and then restore a cloud backup?

1 Like
15

Yup - about to suggest the same thing. Assuming you have a recent enough cloud backup that reset/restore isn't going to lose you a ton of devices/automation setups, etc., @lance.gleason that you've added since your most recent cloud backup.

16

It's not letting me do that because I have active subscriptions.

17

Oh yeah...that is a thing. :frowning:

We need some @support_team help here...

18

If you have a good cloud backup why not just restore it instead don't a reset and restore...

1 Like
19

He can't get his hub to fully boot up, so he can't do a cloud restore. He's already tried soft resets & safe mode...

So full reset via Diagnostic Tool was suggested to get the hub to boot fully up and then he could restore a cloud backup. But he can't reset as he has active subscriptions.

1 Like
20

Downgrade of the firmware will normally also rebuild the database

1 Like