Seems like with all the new stuff lately there are some kinda bad "bugs"
Really it seems most of this could have been and should have been addressed in the beta vers ?
I'm a little taken back by what's what's going on with all the bugs that are in the new releases.
It's very exciting to see new stuff come out and then you try them and they're unusable.
I guess I'm a little disappointed ..
Also if I wanted to sign up for or to be a beta tester I would've.
But I didn't but I still seems like I am and many others are and just seems un-necessary..
What do you guys think?
Am I wrong? Am I being too hard on the guys at Hubitat ?
its a very complicated system and hard to test everything.. case in point i use the legacy dashboards heavily between 4 hubs.. and it took me like 2 days and 3 beta versions to find out they were broken.. guess we need more beta testers.. but i dont believe in beta testing unless its on the hub in the location where i am present.
normally i wait too and it did confuse me that we have betas and releases coming out on the same major version.. in addition, i looked at release notes and only saw a serious exclusion issue fixed and stuff relating to the new dashboards which i am not using so i thought it would be safe.. spank me!!!!
Well that may be the case and yes it is complicated system..
But I kind of found the bugs within the first 5 or 10 minutes of testing the new dashboard.
I'm just surprised that this wasn't found during beta testing or if it was beta tested at all I can't really tell
There will always be some bugs that go unnoticed during the alpha and beta testing, though some of the features in this release spent less time in beta than others. Also, because this release has significant visual enhancements, some bugs are more noticeable to some users more than others.
Fortunately, as you might already know, unlike many companies in this industry, Hubitat offers an easy way to revert to a previous version if a particular issue affects your system beyond your acceptable level. You can do so from the Diagnostic Tool.
I also try to be a glass half full kind of guy... all of these updates are provided to us free of charge. On the whole, I feel like we're getting a pretty good deal.
Well .. that's true ...
But that's not really the point is it ?
The point is that this stuff is happening
And it's happening to your paying customers.
And the customer is having to figure out how to fix and or use a work around for said problems.
And or " revert " back to a semi working product.
I would call this " beta testing " your product.
And yes not all computers are the same and yes
They all have differential setups and yes this can make a difference..
But this is not why the drag and drop doesn't work
On opera and only works on chrome and only if you turn off auto resize.. this is just bad coding.
And again should have been found way before
This was released to your paying customers.
Well that's true and untrue we paid for a system and expect it to work and also expect that the makers of the product give us updates that work correctly just like any cell phone computer system or any other product that you purchase that has updates if we had this kind of problems with Samsung updates or iPhone updates there'd be a bunch of really pissed people
All updates are optional, no one has to update to the latest version. I’m in the beta group but don’t always participate and have missed the last two rounds. As others have mentioned, due to the huge variance in setups throughout the user base, beta testing will only highlight more obvious bugs with others being found once the firmware is released to the masses. I will say that Hubitat staff are very fast to respond and iron out the remaining issues. An easy strategy is just to wait a week or so until after the initial release of new firmware before updating, as by then most residual bugs have been reported and squashed.
I’m in support and all my customers have this expectation too. If our engineers ever fiquire out how to make this happen 100% of the time i’ll be out of a job.
And there are not? The big difference between Samsung's phone updates and Hubitat updates is that bugs in the latter system take hours or days to be fixed, while the former take weeks and sometimes months.
This is not to say that Hubitat cannot do better, there is always room for improvement. So thanks for your feedback.
I remember the times when Smartthings used to push updates on Friday evenings that would cripple systems with no way to go back to a previous version, or even to prevent the hubs to be updated. "Fun" times those were. I guess that's why so many Smartthings users are here.
In the case of Samsung's phones, the process is no different Just the length of the period between updates and subsequent bug fixes is a lot longer. I know, because I am one of the testers.
I'm very happy with the level of support and quick turnaround on bugs when they (inevitably) crop up. And the ability to opt in/out of updates and in/out of Beta releases coupled with the OOPS GO BACK TO AN OLD VERSION option, we're in great shape.
One little bitty change would make it even better. Append a "B" on the end of a version number when it's a Beta release. As it is, you have to quickly check the release notes instead of blithely hitting the update button.
That way when you see an update available you'd immediately know if it's a bug fix release to the current OS, or a Beta version with an expectation of potential issues. Yes, it means that there will always have to be a new build when it's ready to release to the full user population, but I think it would be worth it. If Alphas in build numbers aren't available another scheme could be used. A thought...
So thanks for your feedback.
Just the length of the period between updates and subsequent bug fixes is a lot longer. I know, because I am one of the testers.
