Love this part. Nothing bugs me more than an app on my smartphone with release notes that just say “We upgrade our app on a regular basis to give you the best possible experience.” Like… thanks for NOT letting me know if this is going to fix any of my issues or give me any new features.
And to add my 2 cents here, I agree if you don’t want to “deal” with the bugs, you can just upgrade a couple times a year with the major releases, just like you would be able to with SmartThings or any other wet noodle system. (However, I do agree that it may be nice for users who want to be able to do this to be on a separate release channel and not get the notifications for each non-beta release. Seeing that notification up in the upper right corner for extended periods would drive me bonkers.)
IMO, yes, there are bugs, and yes we do help to resolve them if we upgrade right away, but I have never seen a public platform with this amount of flexibility and with a team that responds so quickly and thoroughly to issues and feature requests. I can point to some current features that I directly suggested as enhancements, and I can’t say that about any other platform/app that I use (except for those that I helped develop at work).
not necessary just dismiss it.. i dont mind that.. but yes would be nice if it was tagged B for beta or not, as i installed the beta recently when betas started again on the same major release number after a general release was issue on that same number.
But i am sure that would screw up a lot of the restore older version etc code.
Related to that it would also be nice to have a web url interface to restore a specific version including the subversion. Currently you can only download the major version and only then install the latest, and that bit me when i installed like 3 betas in 2 days and could not go back far enough!
Having read through this thread to this point I'd like to chime in and say that my favorite part of the five year Hubitat adventure is the get out of jail free card; easy to backup, restore and roll back. I arrived here from Wink because I couldn't backup or roll back. If you want a fully mature system Wink may still be willing to take your money.
Perhaps an inappropriate thread for my first post, but bcopeland's comment really tickled me . . .
After the update bricked your unit, I'm SURE the vendor offered to sell you a BRAND NEW one at a 5-10% discount, right? Customer service at it's finest.
Really enjoying learning the environment of Hubitat and my C8 Pro since purchasing in January. Also enjoying the volume of staff participation here. (still learning and NOT dis'ing WarlockWeary as his posts/knowledge have also helped me along the learning curve)
I love it.
I get to watch an incredable system evolving.
I have not had issue with this at all.
9 hubs hubmeshed together, strong zigbee and zwave meshes.
Thank you to the members of this forum, including the staff for making this a great learning experiance.
I firmly believe in "local", not much external here, and minimal non builtin.
I agree with what has already been said. I don't update until there hasn't been a change in a week or two. If it is a major update (x.x.y) then it might be longer. I just updated one of my hubs to 2.3.9 for the first time today. I didn't want to but I picked up some Z-Wave LR devices and wanted to try them out. I ran into some issues with LR and added some feedback even though the issues were mostly my mistake.
Even Apple has bricked devices with new updates. They have a QA budget that is larger than the net worth of Hubitat. Bad things happen. It is a balance between having the latest and greatest and having a stable system.
There is a reason IT in big companies lag behind in updates. It is not unusual to see them running Windows NT years after 7 came out; and 7 years after 10. When you can't afford to be down you wait until the new system is vetted.
Hubitat is far from perfect, but what company is more responsive than Hubitat? I've seen an issue or feature request get reported and a few days later it is in an update.
I'll preface this by saying that I think "it will likely never happen..."
Would it be worth splitting the genuine "platform" elements from those that are built-in apps. So changes to things like Hub Variables, network comm's, Z-network stuff, etc, see those as "platform" changes, but updates to RM, Dashboards 1.0 or EZ Dashboards, Button Controller, etc, see those as updates to individual apps that you can choose to apply, just like we choose to apply custom app changes via HPM, with a very strict reliance on the platform version that is required for an update to a built-in app.
The benefit to this approach being that we can separate the need to apply a fix to a built-in app like RM with another potential breaking changes in another built-in app.
I applaud the beta testing effort for major releases and I think it's showing results. It's the other releases that are in my opinion uncontrolled and untested. Recently that was a release Release 2.3.9.141 and maybe a day or 2 later another with the note "Fixed dashboard background and scrolling (bug introduced in .141)". While I appreciate both the need and desire to be responsive with release of software, all these quick releases are obviously not going through any beta testing. And we the customer/user pay for that in wasted time or broken systems. I now know that's how this product team works so like others, I do not update until the dust has settles with all of the real world testing. I'm not interested in being a tester or having my system broken. Software testing is not a trivial endeavor and this company has other things on their minds - good things I'm sure.
I just read some of the thread - i agree with a previous poster - I just make note the flurry - skip the updates for a while. we went through this with RL, etc. going back.
I want to voice for the unspoken - one factor about 'free' updates, or the comments about 'rolling back' ... My hub doesn't exactly come to life after a reboot perfectly every time. There seems an assumption that everyones hub is perfect and flawless. Not true and updates are a pain in the arse.
Theres always the review, the light that got caught in a wierd state, a v-switch not coming to life proper or the mode being wrong. Then I remember my expectation on this device and I let it go again. and again. and again ...
Again, it's hard to account for a lot of things until it gets out to a broader public. The fact that those fixes come out within a day or 2 (and occasionally hours) truly says something fantastic about the company. Their dev's care. If this were ST or Apple, or Wink(ahahahahhahaha) you would not see that level of commitment. ST would wait a month for a fix, Apple may or may not would allow you to roll back but in most cases they'll strip the previous version of validation so it won't load... Wink? Well..hahahahahaha...
I think rather the assumption is we all have full control of when and if we update, so that allows us to be as picky/careful as we want/need to be. In other words, it's on us to resist the FOMO.
If someone has a more "fragile" or complicated setup that may require a more conservative update approach, hubitat supports that. The additional flexibility that HE provids puts us in a hugely better space than the other "We're going to blast your device(s) w/an update and you can't stop us or revert!!" approach. In this context I think it's on us to make the best decions for our setups/tolerance for potential disruption. But that's just me...
true I have control over how I schedule my updates - generally I like to set and forget. When updates come out once a month its okay for an automatic update - but when a flurry comes every other day it changes things - and I don't like change. This isn't a tinker toy. i'm relying on the thing. maybe I need to rethink reliability.
I have seven but three of those are being decommissioned and one will be for testing and development.
