I know what its like to be in IT and feeling like you never get a day offā¦or no weekend. But seems like āwork life separationā is more important than proper staffing to have coverage to support issues when they happen. What do i know thoā¦ Just that its like my house has had a stroke or bells palsy where half of its face doesnt workā¦
Not sure if this is going to help everyone but on my automation being very slow I adjusted my Geo fence in the Samsung smart things app to really far out applied it and then changed it back to the normal 500 feet And everything seems to be a little faster now not sure if that helps but helped mine.
One other thing I also unplugged the power to the hub removed the battery and plugged it all back in To reboot the hub
1 Like
Same as usual here. Things not working fully. Motion automations only turning on half the lights, or turning off some not all. Slow reaction timesā¦ all that. Iām glad to know we have a crack team of Top Men working around the clock to resolve issues.
Seriously every time I go back to thinking ādang ST has been stable time to buy some more devicesā, it just goes up in a cloud of smoke. I still agree we are not the normal users. We are the users that evangelize this system to peopleā¦become their support line, and even idea person. So when we get this crap for a week and seemingly no movement besides āits not getting worseā makes me really consider not telling people about it. To the point Iām really changing my purchasing decisions to go more Hue based cause for the most part all I do is lighting. And I just want it to workā¦
Disregard my post. I found the issue with lights coming on at wrong time. In automations>smartapps at the bottom I found a lighting app I forgot I created when testing out different options for routines. Had to scroll down to see it. User error.
My rule to turn on my garden lights at 7 PM tonight didnāt work - it has failed a couple of times in the last few days now.
Well the app canāt load (times out, gives unexpected error). This preceded the last catastrophic schedule failure. Hold on, looks like we might be in for another bumpy ride.
The trip from my office through the living room to the kitchenā¦ every trip through tonight has resulted in failed lights turning on or off with every trip. Think thats about 12 or so attempts of an automation working right. 0 for 12. I guess thats acceptable. Yes Iām Mr PassiveAgressive. Just getting tired of wondering if this is going to work or not. I wonder if this is considered OK by the upper management now? We hear from a few people in the trenches and I appreciate that as I am a IT pro myself. But the status page has been āyellowā for what, a month now. Even if it is complicated, a known bug shouldnāt be that long lived.
This all just really disappoints me
1 Like
Yepā¦ I havenāt been able to access my home location via the app all day. 
Just times out with āUnexpected Errorā and options to Logout (like that will help 
) or Retry. Really itās been coin flip for the last week or so. I have quite a few ādevicesā Iāve made for my home lighting system, so I imagine Iām well above āaverageā in that regard. But still, Iāve never been locked out like this.
1 Like
Somehow everything managed to fail last night. My wife isnāt home and is being reported as present, I am home, but being reported as not. 1 of 4 outside lights shut off last night, the alarm never armed, and the door sensors are in various states of who knows what.
Everything was working too smoothly and I was almost tricked into thinking they had finally scaled up to the level they convinced everyone they were already at. Very disappointed in the whole platform.
The Cassandra nightmare continueā¦
My download routines (dumping about 450 history events every 5 days) failed again today.
Out of the 11 temperature sensors my routine should dump, I can only dump 2 āby handā from the IDE before getting the dreaded :
"java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency LOCAL_ONE (1 responses were required but only 0 replica responded) @ line 112"
or sometimes :
"java.lang.reflect.UndeclaredThrowableException @ line 112"
As explained before in the other Cassandra timeout during read query thread, this always happens during the history database access :
--------------------- abstract from āJJās Test2ā smartapp ---------------------
111 for (tempSens in temperatureSensors) {
112 def allEvents = tempSens.eventsBetween(startDate, endDate, [max:2000]).findAll{it.name == ātemperatureā}
--------------------- abstract from āJJās Test2ā smartapp ---------------------
This is especially irritating since this dump routine is critical for me : it is the only way I have found to overcome the limitation to 7 days of history imposed by SmartThings.
So now SmartThings, or somebody at SmartThings, makes my workaround ineffective.
Reminds me of some SF novel by Frank Herbert (Whipping Star) where a whole āBureau of Sabotageā was dedicated to prevent the administration of becoming too efficient and too complacent.
SmartThings should tone down its own āBureau of Sabotageā !
Anyway, any geek naming a mission critical service āCassandraā should have been preventively sacked for attempting to sabotage the future !
1 Like
Why donāt you write the events to a database as they happen?
i.e., Subscribe to all the temperature sensors and call a REST-API to write to a database like Firebase or use InitalState or dozens of similar services?
Not saying that SmartThings shouldnāt get Event History queries to work, but that you could avoid the issues with it.
Well, I do not need real time download (I integrate the downloaded text files by hand from emails into Excel), and I am NOT sure I would have any less problems that way : any SmartApp I schedule has about 20% chances of not properly executing due to some SmartThings cloud problem (my statistics over the last year), and losing 90 events due to a trickle of incidents over 5 days would not be as visible as losing 450 once every 5 days.
At least, the way I proceed, I see when I do not get what I should.
And anyway I do not want to start anew and develop a completely new integration solution, after spending weeks developing the current one, which worked more or less (exempting random missed schedules) until SmartThings sabotaged me (againā¦ 
).
An Event driven SmartApp (ie, subscription to Device Attribute Events) is much less likely to fail than a Scheduled SmartApp in our experience.
But I understand itās a bother to rewrite existing functionality.
Iām posting this though as a recommended approach for other folks who are considering data collectionā¦ ie, donāt rely on Event History: SmartThings may arbitrarily truncate it at anytime.
1 Like
My routines donāt work too 
Is it common problem? If it is common ST staff has to inform all customers by email. Many people doesnāt know this forum.
They do, you just have to sign up for notifications. http://status.smartthings.com/
1 Like
I use Smart Rules as redundancy just in case ST automations fail .
My schedules seem to be firing pretty well this week from Core. App also seems more back to normal more or less. A bit of slowness here and there and IDE is a bit slow but almost back to what I expect
My Motion sensor event worked well yesterday, but sunset/sunrise automations donāt work
Sunset sunrise have been hit or miss for about a week. Turn off at sunrise seems to have more issues ( failures) than turn on at sunset.
Power limit off after x minutes is not working ( for me ) either.
1 Like