Restoring a backup does not change the platform version. So not sure what you are saying exactly.
Cloud.hubitat.com can be pinged.
Did you try my suggestion of using the diagnostic tool to download the update?
1 Like
OK, glad at least the traceroute worked. Would that have resolved that there is nothing in the modem/router blocking the path to hubitat servers?
If so, any other reasons why the hub will not update?
Did you do what @jtp10181 said about using the diagnostic tool. It has a option to download the latest release. On that menu. To get into it perform the following steps.
-
Go to the setting menu and open up the hub details page. Highlight your hubs MAC address copy it to your devices clipboard.
-
Go back to the Settings menu and scroll down until you have a button listed for "Diagnostics Tool" and click on it. This will take you to a new URL that is your hubs ip on port 8081. It will prompt you to enter your Hubs MAC Adress to authenticate. Paste in the address we copied earlier and you should get a new menu. It should look like what is below.
-
Please provide the Platform version, Hardware version, and Diagnostic Version. Also confirm the date and time are fairly close to real time for your location.
-
This is where you can download the latest platform version if you are behind, or load a previous one. I would suggest picking the option to download the latest version.
You may want to also perform a reboot with the advaced option to rebuild the DB after next restart. That essentially does a soft reset and then a restore from backup to perform database cleanup.
1 Like
Yes, I have tried this before but I repeated it now. The Platform version is 2.3.9.201, hardware version C8 and Diagnostic version is 1.1.131. Time and date are correct, time out by 2 mins.
Tried downloading latest version and got this error 'Could not download this update, try again later'.
If you perform a soft rest from the diagnoatic menu and don't restore can you perform the upgrade?
That should reset the DB as if it was from the factory but leave your radios intact.
I have a hunch.
This sounds very much like the issue where the z-wave logs overrun the system memory. It was a bug for a short time and you might be stuck on those versions. Next stop is possibly a semi-bricked hub.
Do the soft reset with the clear logs option. Do not restore your backup until you get the platform updated. Let me see if I can find the other instructions.
EDIT: I found the old instructions, sounds like it was 2.3.8 that had the issue so this may not be it, but it sounds very similar to the symptoms people were getting with that bug. Urgent Z-Wave Logging issue identified in platform version 2.3.8
You could try this endpoint from the instructions to see if it makes a difference
3 Likes
Ok..so I tried mavrrick58's suggestion, soft reset without restore. The upgrade still failed.
However after returning to the hub UI I got the message ' Hubs firmware: Your hub will now update to the latest firmware to ensure you have the latest apps, drivers and features. This may take several minutes and ....hub will reboot'. Options are 'Update now' or 'Start over'.
I believe I should choose 'Update now' option...
You could try update now. If that doesnt work look at what @jtp10181 just posted above.
Ok, so I followed jtp10181 instructions, including clearing the past logs and the zwave debug and disable command.
I was able to restore a newer platform, moved from 2.3.9.201 to 2.4.0.151, but after trying to update to the latest version which is 2.4.2.125, download failed once again.
Did you try the download after the soft reset and before restoring a backup? If still failing then I don’t see how it could be a hub issue. Sounds like a network issue on your end.
1 Like
What exactly does that mean. Those are different hub platform firmware versions. The standard upgrade process doesn't step through the versions but instead goes to the most recent onw Rhe restore process doesn't touch hub platform versions just the DB for your hubitat environment.
If you used the standard upgrade process you would be on 2.4.2.125. Did you use a special URL to perform the upgrade instead so you could specify a specific version.
If you go into the diagnoatic tool what version is shown for the hub platform. If you click on the button to "restore to previous version" what options are there.
What kind of network setup do you have? Firewall router, vlans, ect.
I updated to a previous version stored on the computer which was 2.3.9.151 but was still unable to upgrade to the latest version 2.4.2.125.
So the hub is currently running 2.3.9.151. Previous versions available are 2.4.0.144, 2.4.0.147, 2.4.0.151 and the hub came with 2.3.9.201 installed.
However, I am now seeing that there are no devices installed. I believe this happened after I soft reset but did not restore. I hope this does not mean all devices and automations are now obliterated 
Setup is very simple, modem from service provider going into google wifi mesh network. Hub is hardwired to google mini for internet and plugged into UPS.
It is a setup that I used other places and works well, until now.
Can you please provide a screenshot showing you are on hub platform 2.3.9.151.
The soft reset resets the DB but not the radios. Once you restore the DB your automations and such should be back and functioning.
I would also suggest you go into the Diagnostic tool and use the "Restore Previous Version" to switch to the latest 2.4.0.X version. The options on that screen are already downloaded.
It would also help if you can post screenshots of any errors that occur.
This statement is concerning as it doesn't make sense with how the hub works. We as users have never been able to download the platform firmware to our computers so if this is true then somethings are very wrong on a variety of levels.
3 Likes
Mavrrick58, I apologise if I am using the incorrect terminology, so let me explain a bit more with pics.
So as we spoke last night the hub was running 2.4.0.151 and that was the case today when I viewed the hub UI.
Unfortunately even though only a soft reset was done, no devices were apparent.
I tried to update the platform to the latest version again with no success.
Even though an update is available.
The statement I made last about 'previous version stored on the computer' was meant to refer to the back ups which are stored before updating..
So where I left it today, the status light on the hub is green but still the hub is unable to update to the latest version. Also at this point, even if the hub is salvageable, I will have to rebuild from scratch it seems.
But the main error continues to be inability to update the platform version.
I hope I did not leave anything out and that my pics went through..frustration is setting in..sorry.
Thanks for all your help everyone.
Dunno if this helps but....
I recently had a problem and thought my C-7 hub had carked it.
C-7 started to slow down and show Hub Load - Elevated/Severe also losing the cloud connection and ultimately crashing and needing a soft rest. Also refused sometimes to reload the database. I finally gave up.
Meanwhile an old linked C-4 happily chaffed along.
I thought the C-7 had died and luckily I have picked up a few spares along the way and loaded up another hub and imported the database. Started ok but gradually went the way of the original C-7. Tried 2 different additional hubs and no go.
With a lot of hair pulling, roll backs trying to find the app or driver causing the problem, and finally removing things from my network one at a time - the culprit turned out to be a rogue D-Link switch - a DES-1016D to be precise.
The original C-7 is now back up and running with no errors.
Not actually sure what the DLink switch was doing but the C-7 hated it. And the C-7 wasn't even connected to that switch the C-4 was! But just the switch being on the network was screwing over lots of things.
Seems all ok now that the offending switch is gone (touch wood).
So not always the hubs fault or something connected to it that can be causing the errors. Bit of a trap really.
No, the soft reset only wipes the hub database, not the device radios. If you restore one of your saved backups it will load the device list back to how it was. Just do not factory reset or mess with any of the devices.
The backups on your computer DO NOT change the hub platform version. 99% of the time you can load any backup on any hub platform without any issues. The version listed on the backup files is just a reference point for your info only.
Try running this endpoint from a web browser, it will seem to stall for a minute but let it run.
http://HUB.IP/hub/advanced/downloadPlatform/241
*Fill in with the IP of your hub
That should download the newest 2.4.1 build to the hub if it works. Then you can install it from the Diagnostic tool (restore previous button).
If that endpoint fails, along with the normal update UI and the diagnostic tool button, then I would say 99% certain it is some sort of networking issue on your end.
Thanks again, good advice net.sheriff and jtp10181, I am learning as I go along. It is good to know that the backups do not change the platform version, the naming was confusing.
I will run the endpoint tomorrow when I am close to the hub once again.
As far as issues are concerned and devices that clog up the hub, I noticed I was asked about zwave logs over run. What is this? I have about 3 Zooz multisensors on the network which were constantly detecting motion (trees and birds). Could this have led to a swamping of the hub to the extent that it could have caused this problem? And if so, how do I prevent it from happening again?
The problem with that is Google wifi is super simple. I ran the 2017 version for years until i upgraded to unifi. I just mean it is super simple stuff with zero complexity.
I wonder if it is simply a reception issue between the satellites and the main router unit. Maybe it is on the edge of reception?
No, that alone would not cause it. It was mainly just a bug in 2.3.8 (you are on 2.4.0 already), and would have been fixed by the Soft Reset with the log purge which you said you tried already.
True, @Caribman you could try moving the hub so it can plug directly into the main router node (which is connected to the modem).
Ok, I can try a direct connection to the modem but I will say that the hub is less that 15 feet away from the modem with direct line of sight and about 2 feet away from the google node.
I asked about the multisensors because when I had devices attached to the hub (memories..lol) these were the fist to stop working.
