I have a C7 hub running 2.3.8.119 and I'm trying to migrate to a new C8 I purchased, but need to update my C7. Whenever I try to update to 2.4.0.151 it just hangs on Checking for Update and I'm running out of ideas on what to try to fix the problem.
So far I taken these steps:
- Switched from static IP to DHCP
- Switched from auto port negotiation to fixed 100Mb (Full duplex)
- Tried static and dynamic DNS settings. I don't believe it's a DNS issue then since both my hosted DNS and the static 8.8.8.8 both fully resolve everything as expected.
- Tried doing a soft reset
- Tried doing the update through the diagnostic tool. It tells me the latest version downloaded and I can user the Restore Previous Version function to apply it, but 2.4.0.151 that just downloaded isn't there (just two older versions: 2.3.8.131 and 2.3.6.144
- I also verified I'm using the latest diagnostics tool by going to MYLOCALIP/hub/cloud/updateDiagnosticTool
Any ideas what else to try at this point?
This is easy to rule out (and I'm mentioning it since it's commonly the cause). Go to Settings > Network Setup, select Network Test, and then type a hostname (not an IP address) like cloud.hubitat.com in the "Ping Host" box, hit Ping, and verify that the output resolves to a public IP address. Post the results here if you are not sure.
Also: any unusual network configuration on your side, like multiple vLANs or guest networks? Plugging the hub into a switch or switch port that does not have any special configuration is an easy troubleshooting step to rule that out if you do have something.
A plain reboot can also help, but you would have already done that as part of your other steps...
1 Like
Can confirm I have previously restarted it. I just ran through Network Test panel and can confirm no lost traffic with the ping test to 1.1.1.1 as well as to cloud[.]hubitat[.]com
I do use a segmented network with VLANs, but the VLAN I have confirmed the device to be on is an unrestricted VLAN with no special firewall rules blocking traffic in/out, it's basically got a wide open internet connection on that network.
I might bypass my internal network and let it connect directly through my modem for absolute confirmation it's nothing with my local network, but I'm very versed at networking and am fairly confident there's nothing with my local network.
Any other steps that may be worth trying? I'm confused as to why the Diagnostics Tool doesn't show the latest version in the Restore Previous Version function after the Download Latest Version on the Diagnostic Tool page confirms it successfully downloaded it.
No "lost traffic" isn't the only concern; you want to make sure it's going to a sensible public IP address (won't necessarily always be the same one in my example, but you can use a well known one of your own choosing if you want to test things generally). Sharing those results here can be helpful if you aren't sure.
I'd definitely suggest removing the VLAN from the configuration, at least to rule that out.
I don't see a network reset on the hub as a specific step you tried above, so that may also be worth doing (although probably not much different in the end than all the settings you checked). As documented, hold the round recessed button (only round opening in a sea of squares) for 7 or more seconds, release it, make sure the LED blinks blue (try again if it doesn't), and wait for the hub to reboot.
2 Likes
Post a screenshot of the cloud.hubitat.com ping test.
Have another theory also. I think you should have the option when you reboot for advanced settings of rebuild database and log purge. Reboot and check both of those. When it reboots you can verify if the log purge worked by checking past logs and it should end when you rebooted and no go back further. Some of the older releases had an issue where the log purge was not actually working so hopefully it works for you.
The log purge is also an option in the Soft Reset menu so you possibly have already tried it.
Also in the current Diag tool there is an emergency safe platform version you can install, 2.3.7.146. You could try rolling back to that as well and see if that lets you update to current.
One final thought, have you tried just doing the migration as-is? It would probably work just fine going from 2.3.8 to 2.4.0. I think the instructions to have both on he same versions is to avoid potential issues with the backups from random old releases, but if it works it should be fine. If it fails then the old platform may be the cause. No harm in trying anyway.
1 Like
It's been a few days, but wanted to close this thread out. The fix was to reboot the hub selecting the options to purge logs and rebuild the database. Once done, I used the diagnostic tool to downgraded to the oldest version available as the safe build (2.3.6.144). Finally, I was able to upgrade from that build directly to 2.4.0.151.
Thank you all!
1 Like
