For some of my devices I want to get the latest update, and that's no problem.
However, for some devices I want them to be on the last update of the 2.3.N.XXX series. In other words, I don't want them to be at the latest version, but I want them to be at the latest version of the 2.3.N series. That's probably a lot safer and they won't have any issues.
Is it possible to update to the last version of the 2.3.N series?
(Obviously, we only know that 2.3.N.XXX is the last one, when we are already at 2.3.N+1.YYY)
You can ask for some of your hubs to be in the beta so you can get the bleeding edge versions, beyond that, overall it's your choice on what devices to update when. They can't just assign your hub a specific version nor do I expect they would want to. They leave it to the end user. And remember you can always roll back.
There are end points available to download the last hot fix of a previous update. So say the current version is 2.3.5, if you go to the following path, you can download the last version of the 2.3.4 series:
hub/advanced/downloadPlatform/234
Similar end points exist for 2.3.N updates, you just need to change the last 3 digits in the above path.
How do I find in that list, the latest one that I downloaded from that endpoint that @bobbyD mentioned?
How do I find out the latest version number that existed?
Not necessarily on my machine, but in the updates found on Hubitat's cloud?
If you have multiple versions of 2.3 4 on your hub, already, then the highest number is the one you downloaded. Each end point contains the last hot fix released before a new major version was released.
Not all hub HTTP endpoints are officially documented, particularly some of the ones that can provide a very advanced function that isnβt otherwise available in the GUI, like this one.
In nearly all cases, the current version would be recommended, and the Diagnostic Tool can help with most of the remaining odd cases (and it is documented). My inclination is to leave this as-is given all this, though I'm open to feedback.
The reason that I suggested it, is because let's say that you have a hub at a client's site.
You want something over there that is as stable as it gets, even without all of the latest functionality that the latest versions can give you.
We have seen that the latest versions may introduce "breaking changes", although this is very rare.
So, the latest version is not necessarily the most stable one.