Depends on the competition. And the features. 
Every system has pluses and minuses. In general, the ones with more reliability in the same price class have fewer features. (Indigo, for example, is rocksolid, and runs locally. But it only supports zwave and Insteon, and even then no zwave door locks. ( it doesnāt support the security command class) ) So it just comes down to what you specifically need as to what a good match will be. Detailed discussion here:
Haha, that would be me - good times! Whenever things go bad with ST, I pull up that screenshot to remind myself that things could be worse.
I will say thisā¦ Iāve been really frustrated with ST lately, but this weekend was the first time in probably 4 months that everything in my system worked properly, including scheduled timers and the gradual dimming functions that I use āGentle Wake Upā for.
Of course, now just starts the countdown for the next time Iāll have issues though. 
Yea Iām messing with the Indigo demo on my mac āserver.ā The locks is a big deal breaker. I see it has a lot of potential, it just looks a little behind the IOT ball.
I know itās completely unrelated, but I thought it was funny when I checked the status page sometime yesterday I think and got thisā¦
Ah, those were the good old days.
Iāve not been here as long as JD, and I was one of the āgive them a breakā crewā¦up until my 6th alarm going off because the SHM didnāt turn off on time. Iāll still give them a break, but I wonāt recommend ST to others, at this time.
Most of us arenāt ready to abandon this ship. I still think the Hub is a useful device, I still like it. Butā¦
In the end, we, the users, canāt do anything. The ST engineers should have logging and measurement tools in place to be able to determine where the problems exist. Frankly, I suspect the whole architecture may be flawed, if theyāre still trying to determine the root cause after months.
What irritates me, though, is this make-work the ST people have us do. If the issue is the back end, then why does using a custom rule work, but not SHM? It probably doesnāt. Or if it does, itās temporary. I suspect the whole reason weāre told to make change is to give us something to do, so we stop complaining, while they throw equipment at the app.
But these changes could be starting to muck our systems up, with their convoluted equivalent to āfollow these 17 stepsā.
(This weekend was the first time I heard the back end was using Cassandra. Cassandra and Java. Ick. Sorry, Java bias.)
JDās point is good: this really isnāt the way to find the problem. The ST people will have to find the problem.
My concern is this: It appears that this may have started out as an overload or attempted change to the scheduler, then this eventually resulted in database corruption - weāve seen many cases that point to this. If thatās the case - no matter how it happened in the first place, anything short of a restore from backup on their side (very messy), the data (devices and rules, etc.) wonāt be coming back on its own. Intervention on our part - such as rule rewriting/replacing or changing device names to force a data rewrite, etc., may be the only way to clean data. I also fear that the existing corruption of data on their end is continuing to corrupt more data - and create new issues. If we truly have data corruption, we have a very real and ugly mess that may self-perpetuateā¦
knocks on wood Iām at about 36 hours with no issues. Still not confident enough to install a siren, but even SHM has been behaving. Which is nice, because we have a 1 month old and I have SHM set to disarm and arm based on our master bedroom door open/close, which happens about 3x a night when going downstairs to fetch bottle parts.
I agree, a corrupted database is probably a worst case scenario.
Iām just not going to require close to a hundred rules over three apps, only to turn around and do it 10 more times.
My plan is to wait it out, perform maintenance, and when weāre running again Iām taking the entire system down and starting it from scratch.
That makes sense. My housemate just announced this morning that I have to choose between SmartThings and breakfast. 
Since the last iOS mobile app update broke voice navigation, he has to do everything with the app for me. Usually in the mornings he makes breakfast, puts away dishes, and checks the laundry before he goes to work, but he can sort of do all those things on autopilot.
Since the DST debacle heās been spending about 10 minutes every morning checking things for me in the app, and I think heās just tired of it.
We may just unplug our hub until things stabilize and the mobile app is fixed. Because, you know, breakfastā¦ You have to keep your priorities straight. 
Thanks for all the updates guys and gals.
Weāre pushing a few things throughout the day today we are confident will continue to help. Weāll keep you posted.
Youāre still SOL?
Cāmon, guys. Wake the 
up.
To be fair, they offered to try and find me the previous build for the mobile app, but then Iād be out of sync with the rest of the world and it just seemed like too much trouble. Whatās the point in being able to take screenshots if the screenshots themselves are useless to anyone but me? Plus that would be a fun conversation to have with support: āno, I canāt update the mobile app to the most recent version because that one doesnāt have voice access.ā Weād both go way off script.
Iām hoping theyāll have the mobile app accessibility issue fixed in the next update. @david.mccrindle indicated he felt it was a pretty high priority.
Mine has been working about the same time as yours. I do have a siren and so far there have been no false alarms.
Canāt disable my alarm!!! Ahhhhhhhhhhhhhhhhhhh keep getting notifications.
Mine didnāt disarm my SHM today morning as part of routine. Had to cycle through arm, stay, disarm couple of times to get it to disarm.
Ditto for me. I can fire Good Morning manually, but it doesnāt fire automatically, even though the notifications are there as if it had. It doesnāt change mode or disarm. Away and back modes seem to be working ok, though.
ST staff must be closing in and getting confident. Job History was re-enabled in the IDE this morning.
