Wasn't sure this was the right place for this post.
I let my Hub fall behind on software because everything was working and life got in the way. I am nervous about jumping all the way to 2.3.9.176 in 1 update. I've started reading through all the release notes and saw notes regarding not being able to restore from 2.3 back to 2.2.
Is there a way to manually choose a platform release so I can jump 3 or 4 at a time to eventually get to 2.3.9?
If the answer above is no, then my next question is did I misunderstand the notes and recovery from my current backup should be fine?
There have been a couple of releases in the last few years that had some sort of dependency on a previous set, but don’t recall any lately. If you want to do some smaller jumps you’ll need to work with @gopher.ny or @bobbyD to find out what endpoints can be made available, but there’s a better than average chance that you could update directly to the latest firmware. Can’t recall, but you may need to also do a ZWave update afterwards.
Would now be a good time to upgrade to C8?
In the interest of service continuity, could the C5 be returned to service if it didn't work out right away? Lots of permutations.
Again, just thinking out loud; you don't want to shoot yourself in the foot.
If you go in and check for updates and it won't update, go to http://your.hubs.ip.here/hub/cloud/updateDiagnosticTool from a web browser and wait about 10 mins. Reboot hub, go to yourhubip:8081 and confirm that your diagnostic tool is 1.1.130. If so then simply go to yourupip>>check for updates and download the latest update.
Are you suggesting starting from scratch on a C-8 or trying to load a backup from my C-5 onto the current software on the C-8?
If it is the latter I can do that now on my C-5 but don't want to. My network (25 devices) and automations aren't huge but it will be a pain to rebuild from scratch so I'd rather not do that.
In order to perform a proper migration from an older hub to a newer hub, like the C8 Pro, one should have both hubs at the same version. Thus, I am not sure this really alleviates any of the concerns over performing the upgrade to the latest version.
I would wait to hear from @bobbyD and/or @gopher.ny from Hubitat, to see if they foresee any issues with simply upgrading to the latest version from such an old version.
Use this endpoint to download any final version of past major versions.
Where 234 = 2.3.4, etc... change to any version you want
/hub/advanced/downloadPlatform/234
Once downloaded it will be available in the Diagnostic tool under "Restore Prior Version..."
Was it referring to restoring a backup or restoring the platform? I suspect it may have been saying you cannot roll the platform back. The actual database backup can typically be restored.
As an experiment, I downgraded my development C-7 from 2.3.9 to 2.2.3.148
It was certainly a walk down memory lane to see the initial screens as they were back then.
Going that direction did indeed wipe the config. It was as if I did a Soft Reset too. The cert was out of date and thus the 'demand' of my browser to use httpS was making it hard to navigate. Reverting to using an IP Address solved that.
That made it unlikely that my testing could help you since I couldn't check the viability of automations after upgrading to 2.3.9 since the 2.2.3 version had no config.
I'm reverting to 2.3.9 now and surprisingly, the config was intact on reboot.
Thank you for the response, but I just realized after not touching this for about 2 years I discovered I am basically a noob again. Great.
I don't remember the HUB supporting SSH or any CLI interface. When I tried entering your suggested download path in the browser after login and/or through the diag tool window, all I get is 404 errors.
Be sure to change the IP address above to that of your Hubitat Hub, and change the '234' to whatever Hubitat Hub Platform version you'd like to download.
Your platform version is likely too old to support these endpoints, which were (I think?) added in later releases.
On your version, try something like:
http://hubitat.local/hub/advanced/download224
(replacing hubitat.local with your actual IP address, although that could very well work as-is, too)
If you want to go version by version, I think that works up until 2.2.8 or so, then you'll need to switch to the "new" format above once that format no longer works.
That being said, I'm not sure it's necessary. I'd probably just download a hub backup, try the current version, and know that you can use the Diagnostic Tool to restore everything later (hub platform version first, then hub database after that -- both separate processes) if needed. There were some breaking database changes in between if you downgrade, which is why the poster above found that theirs didn't work; these are documented in the release notes but are only a problem in the unique scenario of downgrading, and even then, your hub should store the last version before that and restore to it if needed (so likely none was available in that case).
If you wanted to do something like this but wanted to at least save a little time, you could at least go 2-3 at a time. I think that's how far back they are normally tested, although I suspect most come from the newest version (though you are definitely not the first not to upgrade from something relatively recent, though I don't know about to 2.3.9 specifically).
I guess the good news is that I was doing it correctly, but the bad news is I think my software is so old that the directory structure isn't matching (yours or the previous 1 suggested).
The diag tool is all the way back at 1.0.81 and is so old it doesn't have the "advanced" button I found people talking about when searching for info on this and it also doesn't appear to have the ability to update the platform and DB separately as you suggested (mine just has a "restore previous version" button)
My original plan was to jump 3 or 4 releases at a time and read the notes to make sure nothing important to me was deprecated or some kind of issue during the upgrade. Once on the latest sw I was going to migrate to a C-7 I bought Jan '23 so I could get better battery for I couple battery devices I would replace with the new chipset. I may just have to bite the bullet and risk the big jump unless I can actually find these endpoint downloads.
I'm not sure what you're trying, but it doesn't sound quite like what we are suggesting. The URLs above are just ones you put into your browser, then wait a few minutes, and they'll finish on their own -- unless, of course, you see an error when you try (in which case it's possible you're a version too early for even the first format of URLs I gave you, but I know they were introduced sometime around then, if not earlier...).
If that succeeds, then you can use "Restore Previous Version" in the Diagnostic Tool to change to this platform version (yes, the name is a bit misleading in this case...). There are no options to upgrade/downgrade your database in the Diagnostic Tool, nor was there any mention of this above; the platform handles this all for you.
My suggestion is to keep a backup saved locally yourself in case you need to restore it yourself at any point. If you downgrade, you might need to restore a database from that platform version given that there was at least one breaking change between your version and now. The platform typically handles upgrades on its own just fine, which is part of the reason I'm not sure you'll even need to do this, though some caution may be warranted given just how far back this is.
In any case, with a backup saved yourself and the ability to roll back to the last three or so platform versions available on your hub (normally two from the current release and the latest from the last release), you should be able to revert pretty easily if something does happen to go wrong.
Sorry for any confusion, I appreciate your patience.
I am typing the URLs into my browser after I've already logged into my hub, but I get a 404 error (The page requested could not be found) for all these URLs and the new SW versions don't show in "Restore Previous" list in the Diag Tool. So I am taking that to mean its not working.
As far as the comments about DB versus platform restore, that was me making the assumption I would need the diag tool to accomplish what you suggested from your post about restoring (see below) after going all the way to the current release. I was sharing because I thought it might be an indication of how old my diag tool is, sounds like this isn't the case and I misunderstood your comment about the restore being 2 different processes . As an FYI, I do have a current backup both on he hub and downloaded local.
What I meant by this is that "Restore Previous Version" in the Diagnostic Tool will get you back to a previous platform version, but does not (in most cases--it actually does try to be a bit smart here if it knows there were breaking changes) restore your hub database. So, you'll need to do that yourself afterwards (or at least it's a good idea so you know what you're actually working with).
That much doesn't tend to be surprising -- but what does surprise some (and is the reason the UI warns you about this now, though some people still don't see it) is that restoring a hub backup does not change your platform version. The filename includes the platform version by default for reference, but restoring a backup taken from an older hub platform version will not downgrade you; that's the reason you'll need to do the above first (or second if there aren't breaking changes or you don't care, but in your case, I'd suggest this order since I know this happened at least once).
Hopefully that makes more sense now.
That indeed seems to be the case, though I'm not sure why. Again, it's possible your hub version is one or so too old to have these added yet, though I know they've been there for a few years now. Can you share the exact URL you're using, maybe copied and pasted from your URL bar? (Your choice, but I'd share the whole URL exactly as-is -- no point in censoring an IP address that is internal to your network since no one else can do anything with it.)
I think that's how far back they are normally tested, although I suspect most come from the newest version (though you are definitely not the first not to upgrade from something relatively recent, though I don't know about to 2.3.9 specifically).
