C7 Update from 2.3.9.160 or .162 to .163 or .164 download verification failure

🛎️ Get Help
1

HUB: C7
Platform: Android phone or windows browser
Firmware on Hub: 2.3.9.160

I have been trying to upgrade from .162 to .163 for a day but no luck. Download verification fails every time. I reverted to .160 and have the same issue. I powered down, unplugged, and powered back up but have the same issue. I'm not getting any exception message that I can see other than Download Failed after verification. It sits on the download failed screen perpetually after that until I navigate away. Any tricks I should try? I'm stuck.

2

Have you tried this?

"Settings". Select "Networking" and scroll down to "Ethernet Speed" section. Switching to "Fixed 100mbps" or "Auto". Whichever one is DIFFERENT from your current setting.

1 Like
3

Yes, same result.

4

Is the hub plugged directly into your router?

5

It is wired to a switch. Has never been an issue since purchased years ago.

6

For giggle run it straight to your router and try. Make sure speed is set for auto

2 Likes
7

I can try but the download isn't failing. It is the verification after download that fails. @bobbyd for additional thoughts as I continue to try suggestions.

8

No, it's the download that's failing. Your network is receiving a corrupt image that none of the rest of us are. The verification process is stopping the hub from using the defective image. But it's the image that is wrong. That's why the suggestion was to whack at the network option :smiley:

2 Likes
9

OK, I'll keep whacking.

1 Like
10

I watched the long download this time from start to finish. It got to 89%, then went directly to verifying and then "download failed". I rebooted the switch at that location prior to download. I'll try moving it now but I'm not sure how my otherwise perfectly functioning network would be responsible for a corrupt image over TCP.

11

No change in behavior. Same failure.

12

I was able to download and install it from :8081 without issue. This seems like a bug.

13

I know you have tried this from your posts above, but when I've seen this many moons ago, changing the network settings from fixed to auto or visa versa has resolved the issue for me.
At least you've managed to get round the issue. :+1:

4 Likes
14

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.