I have a C8 and it fails to update to the latest version every single time.
I have to clear the database and then restart the hub before I can successfully update the hub.
What could be wrong, and how could I troubleshoot this issue?
Thanks
Are you on a static ip or DHCP reservation?
Are you using the OEM power supply?
1 Like
When you say it fails, what exactly are you seeing (or not seeing) to suggest the update fails? Screenshots of any errors or similar would be useful.
3 Likes
Also, what platform version are you attempting to upgrade from?
3 Likes
I would try using the diagnostic tool to download latest version then restore from prior version (which also lets you update despite the buttons name). This can get past stuck updates sometimes.
4 Likes
I'm using reserved DHCP for IP allocation.
I'm using the PSU that came in the C8 box.
Currently running version 2.3.6.145.
When I try to install it, it takes a bit of time for the download to start, and then it takes a long time to get to a few per cent and then fails. To me, it seems like a storage issue of some sort.
When I clean the database by using this URL and restart, the download gets completed without any issues: http://x.x.x.x/hub/cleanupDatabase
This happens for every version update. So far, I installed all version updates with this method since I moved to C8.
For giggles, can you press the network reset button on the bottom of the hub for 7 seconds with a toothpic or paperclip? It will be the only round hole out of all the square holes. Then when it comes back on line, try again.
1 Like
I remember this as a symptom of the speed negotiation problem the hub has in certain cases.
In network settings, whatever this is set to, try the opposite. This is assuming you are connected via ethernet?
1 Like
The reason I wanted him to do a network reset (figured it would be easier)
2 Likes
I don't think a network reset changes that setting, if anything it would set it back to the default of Auto, which is usually what causes the problem to begin with with and setting it to 100Mbps will fix it usually.
3 Likes
Ahh usually I find setting it to fixed causes the issue..
1 Like
Thanks for suggestions. I'll check my switch and my hub config and set them both to 100Mbps and see at the time of next upgrade if it works.
I just saw an update and tried upgrading and faced the same issue then checked my network setting and it was on 100Mbps.. I changed it to auto and without even restarting, the upgrade done successfully in no time.
Thanks for your help. I'll monitor it for a couple of more upgrades.
3 Likes
That was my inclination when I wanted you to do the network reset 
1 Like
Im having the same problem with my brand new C-8. Just took it out of the box.
I tried setting it to 100Mbps and Auto Neg back and forth
soft reset
network reset
connected it to a hotspot on my phone using 4G data (to eliminate local router issues)
Changed DNS to 8.8.8.8, 8.8.4.4
it takes about 10 minutes to get to about 20% and fails later on around 50%. Any other suggestions?
You could try using the "Download Latest" in the diagnostic tool, not sure if that will work in any different way: Hubitat Diagnostic Tool | Hubitat Documentation
Are you connecting via Wifi or ethernet?
forgot to mention i tried that as well.
I have it on Ethernet now. I have tried to shut down ethernet and use wifi only as well
What version are you on right now?
Try doing the ping test to cloud.hubitat.com in network settings > Network Test
(I was going to say try the speed test but I think its broken? not working for me).
The version i have out of the box is 2.3.5.152
ping test works just fine:
PING d194wzi4ri2kev.cloudfront.net (13.249.98.83) 56(84) bytes of data.
64 bytes from server-13-249-98-83.mia3.r.cloudfront.net (13.249.98.83): icmp_seq=1 ttl=244 time=36.8 ms
64 bytes from server-13-249-98-83.mia3.r.cloudfront.net (13.249.98.83): icmp_seq=2 ttl=244 time=90.4 ms
64 bytes from server-13-249-98-83.mia3.r.cloudfront.net (13.249.98.83): icmp_seq=3 ttl=244 time=37.2 ms
--- d194wzi4ri2kev.cloudfront.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 36.754/54.804/90.442/25.200 ms
Do you have the advanced button on your diagnostic tool? Try the option in there to install 2.3.7
If you do not have the advanced button this page has instructions on how to force it to update at the very bottom.
If anything it will get you on a different version, maybe once you get to 2.3.7 you can then update to current.
