I tagged you because I saw your reply (post #2) above. I also noted that this appears to affect C5 hubs so I was wanting to know if this was also your observation. Edit: My C4 and JasonJoel's C4 hubs did not have this issue.
Mine is a C5 and had the update issue also.
Mine was an original hub showing no updates available but after reboot was updateable.
I think this is now fixed ?
On the last 2 updates, my main C5 hub has updated fine. My remote (shed) C5 Hub indicated that it needed to be updated but when I started the update process it said that there was no update available. On both updates, I had to reboot the second hub before it would recognize that there was an update. After it went through the motions it appears that it is fine.
Tonight's update from 2.1.3.125 to 2.1.3.127 had the same issue. My C4 hub updated just fine. I started my C5 hub just before starting the C4 hub. The C4 hub updated and rebooted. The C5 hub is just sitting there stuck at "Applying update." I don't think this has anything to do with the cloud issue. Both downloaded the update and unpacked it just fine. The problem is that the C5 hub is stuck. In a moment, I will reboot it and try again.
Edit: After a reboot, the update for the C5 hub completed.
I had the same issue. My 2 C4 hubs updated with no problems but my C5 hub got stuck and I had to do it several times before it applied. This was with 2.1.3.125. Tagging @bobbyD for his awareness.
Are you saying that when you updated from 120 to 125 you had this issue? If yes, then that is a known issue and fixed in 125. If no, then I'm confused because it appears that your hub is running 125 so it does not appear that you have upgraded to 127 yet.
It happened to me going TO 125.
If it has already been fixed, that's great (although it should show up in the release notes I think, too... If it was, and I missed it, I apologize in advance.).
It wasn't that big of a deal either way for me. Reboot, retry, done.
Ok, I have my wires crossed. If you have the issue of clicking update and the download finishes but the update never completes try switching to port 8081 and see if the update is available there to switch to. I believe I know what the issue is (the shutdown process hangs so the reboot doesn't complete) but it will require more testing on our end and will hopefully be fixed in 2.1.4.
3 Likes
That is exactly what happened to me on my C5 hub (all my C4s updated as expected). I did not try connecting to 8081, thanks for the tip on that. If it does it again, I'll try it.
I was upgrading from 2.1.2.123 to 2.1.3.125 and had this issue.
@chuck.schwer I just experienced this upgrading from 125 to 127. I took your advice and went to port 8081 and used the "rollback to previous" option to move it forward. This worked just fine.
1 Like
Just more confirmation...
3 C-4 hubs upgraded from v2.1.3.125 to v2.1.3.128 without issue.
1 C-5 hub upgraded from v2.1.3.125 to v2.1.3.128 and it had the issue.
8081 and used the "rollback to previous" option and that fixed the C-5
1 Like
2.1.3.127 to 2.1.3.128
C4 completed with no issues. C5 hung again. I did not see the post about switching to port 8081. I'll have to remember that if it happens again. This time, I clicked on Settings and then chose to reboot the hub. Then when I tried again, the update for the C5 hub completed.
It will be good to get this bug squashed!
I've noticed this problem with 4 different hubs when applying the first update when brand new, (one took 16 hours before the update was successful), then every update after that just breezed right through.
Today I updated 3 c-5 hubs, 2 of them were on 2.1.3.127 going to 2.1.3.128 ----updated fine
The third one stays powered off daily as there is nothing on it and it a backup emergency hub. Upon powering on I was going from 2.1.2.123 to 2.1.3.128. And it took 5 times attempting to update before successfully updating.
Power on causes a variety of things, including a backup. I hope you weren't trying to upgrade(reboot) in the middle of the invisible/auto backup. The hub may have been ignoring it or perhaps even deferring it.
5 times.. corrupted the 4 onboard DB backups and the 5 time...
These are WAGs (wild ass guesses)
Ya unless it does a automatic backup upon start up..... This hub is never powered on long enough to get one otherwise, I just power it on to have it on the same update as the hubs I'm using are on then shut it back down.
Also had the same update issue on my C-5 hub trying to go from v2.1.3.125 to v2.1.4. When I went to http://[Your Hub IP]:8081/ it said I was running v2.1.3.128 (which was odd because all my backups were .125) Ran the restart/reboot hub again from settings and the update finally went into the initialization process.
This is what didn't work and did work for me.
I tried to up date from Chrome, Android then Safari as mentioned previously- no good. I tried rebooting, shutting down - no good.
I back dated to a previous version -no good.
Afterr downgrading I rebooted tried again and still no good then whilst it sad downloading I refreshed my screen (Android) it started downloading AND WORKED. Hope this helps for you guys
