Respectfully, @gopher.ny, the updates to 2.2.5 seem to be going out at a fast and furious pace, not well tested.
I have two hubs, a C-5, which is very lightly loaded and used as a development hub, and a C-7, which is my production hub.
I always update the C-5 first, see how the update goes, and then, if successful, and if the update seems to work after preliminary testing, update the C-7.
Up until now, that’s been a good approach. Not with 2.2.5.125 to 2.2.5.126. Of course, I always back up and download before and after each update.
The C-5 update went smoothly. Settings, check for update, new update available (running 2.2.5.125, new update available, 2.2.5.126), do the update, it validates, installs, hub reboots, all fine.
Not so with the C-7, also running 2.2.5.125. Settings, check for update, never completes the check. Waited 10 minutes, still the blue line going back and forth. Went back to the Settings page, again check for update, same result, never completes checking (not in 10 minutes, anyway).
Here’s what I had to do to get the C-7 to update:
Go to Diagnostic Tool, log in, download latest update. The hub downloads, then reboots. Settings, hub details, shows that hub now running 2.2.5.125 (which it had already been running for about five hours, successfully). Again did Settings, Check for update, this time it reported new update available (2.2.5.126). Installed, installation was successful.
Simply FYI, now up and running 2.2.5.126 on both hubs.
