I am currently on 2.3.9.193 but I am trying to get back to .184 to test some things with a potentially broken rule. Since I've been downloading recent betas, the only versions available in the Diagnostic Tool are .190 and .192 and the previous 2.3.8 platform. I am trying to download and install 2.3.9.184 specifically. Is there an endpoint I can use to get this particular version installed again?
Not that I am aware of, I think only final major versions are available via endpoint (2.3.8.xxx last version published).
Generally they dont want people to go backwards because in theory it would be worse than current, but not really always the case. Especially with some of these short beta cycles that don't expose all the issues.
Just some random thoughts:
It would be nice if the hub would track beta and production versions separate. Especially for updates, it could tell you if its beta or production. If you could even temporarily turn off beta on a hub by setting the update "channel" like so many other products have. The system could also keep X number of production builds so you can always roll back to prior production if needed, instead of beta builds knocking the production builds off the list.
Would be really cool if you could just pick a prior release from a dropdown menu in the diag tool and download it. They could always set a filter on it if there are releases they want blocked from going back to for some reason. Or only add specific builds to it and then when there is a final major version remove all the older builds.
5 Likes
This is a great idea! It would be nice if the Diagnostic Tool could be able to select between the last 3 official builds or the last 3 beta builds if your hub is on the beta program.
Yeah and I think the current 3 build limit may be to avoid filling the drive space on the hub, which it is nice it keeps it on the hub in case you cannot easily get it online for whatever reason. But, if it was tracking the builds or could pull from a recent build list from the cloud system, it could still remove the older ones from the hub but then allow you to re-download it via the diag tool.
No idea how the current update system works so this may not be as easy as it sounds, but it would be nice!
Love this idea. @gopher.ny @bobbyD thoughts?
While in beta, one can download current production from the Diagnostics tool, that's about it. We don't keep version history, and there's no way to download a specific minor firmware revision.
2 Likes
The current production release, 2.3.9.193, has some known issues with nested IF/ELSE-IF statements that were not present in the previous production release 2.3.9.184. However, because I have downloaded the other beta releases in between, I no longer have the ability to get 2.3.9.184 to test the differences between the working older version and the newest version. Also, I have no way to get back to a fully functional version of RM5 until all the IF/ELSE-IF issues have been solved. I get that being in this situation is technically my own fault for putting beta software on my only hub instead of buying a dev hub to play with, but still I feel like there should be safeguards put in place to prevent people from getting stuck on a build with known issues. The last production version should always remain available in case the current version has an issue.
If Hubitat itself doesn't want to host previous versions, then there should be a way to always keep the previous production build available on the device itself so roll-back is always possible to at least the most recent previous production version.
I know this is not always the case but a new beta dropped yesterday with more RM fixes for the IF/ELSE stuff. May want to see if that helps.
Yeah that came out pretty much right after I made this post yesterday. I am currently on the latest beta .194 now. I was hoping to run a few rules and then roll back to .184 to run the same rules and compare logs. Unfortunately, now that comparison isn't possible 
I like that idea, it's similar to Unifi products where you can be using Early access/release candidate firmware and just untick it and check for updates to go back to the latest general release version.
Personally.... I would like to think that beta-tester's are given a degree of latitude where they are available to install a range of platform versions, allowing them to adequately test the platform for their circumstance. This would allow them to report back on their experience between platform versions and where they feel an issue may have arisen. This may be particularly useful for those issues that are only detected late.
Obviously beta-testers will need to absolve Hubitat of responsibility for the consequences of opting for the ability to choose prior platform versions... Those in the fellowship of beta-testing acknowledge they are entering the marshlands of Mordor and even the Elves of Hubitat cannot protect them.... In this space... 
But this should still include the ability to download prior platform updates.... even with Sauron observing the download....
Just my 2c...
1 Like
