Risk of upgrading a very old version

I have two homes. I spend very little time in one of them and use Hubitat to manage lighting, intrusion detection and HVAC there. As I am rarely there, I have been loathe to touch anything lest something break and I have to fly back to the US to fix things. I am currently at that house for a few weeks and am contemplating finally installing an update.

I will be upgrading from 2.3.2.141 (8/2022) to 2.4.1.157. I'm a little concerned about making that large of a leap. Does anyone have any thoughts as to how things might go? Should I do incremental updates? Does the HE QA team test such things? What say you, smart men and women?

As a note, all of my automations are managed using WebCOre.

Thanks for any thoughts.

With a remote hub, I would wonder if there are any benefits to updating the platform version. It sounds like it is working well and is stable. Based on this, I would tend to keep things as-is. As they say, if it ain’t broke, why fix it?

3 Likes

since you're there I'd say go for it, of course with a local backup JIC

If my only reward was getting rid of a red exclamation point on my screen I wouldn't risk it. :thinking:

There have been cases in the past where failing to keep the system updated on a somewhat regular basis broke future updates from being possible.

Well that seems like a better reason.
Did that happen on Hubitat between 2.3.2 and 2.4.1?

No I think this was a very long time ago, but just something to keep in mind.

I think the only reason I'd do the upgrade in your case is if your ability to manage it remotely (or other HE support features) might be benefited by getting up to date on your vaccination, errr....I mean version.

But of course the backup first, and do it now if you're going to do it at all ...so that you can spend your free time discovering and fixing gremlins before you leave.

If you're using anything device-wise that's not mainstream popular in this community then that might be another reason to maybe not.