Same thing here. Failure with the Amazon Echo and SmartTiles. And I woke up to SmartThings not executing any of my Home status commands, which set off the SmartAlarm app. Not sure what’s going on, but it’s been about as bad a day yet as I’ve had on this platform.
+1
(20 chars…)
I’m having the same issues today. I’m thankful for this forum, it saved me from hours of trying to troubleshoot everything!
FYI: I just pushed SharpTools 2.0 R3 to Google Play which works around the recent issue introduced for authorizing third party SmartApps! The SharpTools update should become available in Google Play over the next few hours.
Edit: It looks like there are still some lingering platform issues. From what I can tell, SharpTools can control all NON-LOCAL devices. If a device is manually moved to the cloud, you will regain control of it.
Echo is showing commands in live logging, but they ST isn’t processing them.
Same thing here - Everything was working fine then I lost my internet connection. When the internet connection came back up, Echo didn’t work. I get the proper responses verbally and in the log file, but the lights DONT turn ON or OFF.
Jack
Might as well toss in here that I’m in the same boat. GE dimmers not working at all via Alexa. I can still turn them off with the Smartthings app, but the Echo just says OK and does nothing…
I came home today to find out my echo wouldn’t turn on my lights. So I did what any one of us would do and start trouble shooting by deleting reinstalling. What a big waste of time that was. Thanks Samsung
1 Like
Having the same issue. Alexa responds “ok” but nothing happens. Seems like there is no longer a communication with the smartthings Hub. GE switch, smartthings plug only turn on and off with the st app. I also noticed there is a slight delay in the response of the st app with the lights or plug powering on.
“OAuth broken”
a search in the Developer forum hints at endemic problems on the part of the development team. i am far from conversant enough with the languages used in the development to make a contribution, but even when hacking away in MacFortan or C–, we knew we had to sandbox, sandbox, rewrite every line, sandbox again, and most importantly, perform a “real user” test - all this before even a beta was contemplated. that principle seems to be secondary to “publish it now!” amongst the ST team. (in fairness to them, the problem isn’t confined to their shop.) a search for the string “OAuth broken” returns results which suggest this has been a problem for a long time.
maybe it’s time to charge for the service and pay the developers more - maybe invest in a real development shop with executives, supervisors, cubicles and a ping pong table. i’ll pay, for one.
EDIT:
22:57 CST, every device controlled by the ST hub entered the OFF state. this means something…
EDIT 2:
23:09 CST just realized that i had restrarted the hub, and i surmise that what i reported above was a symptom of the failure of OAuth. or of the ingenuity of one of my cats.
That’s what weird to me too… If it’s an authorization issue, how am I still seeing it in the logs? Shouldn’t it be not communicating at all? But the majority of this stuff is above my head, so I’ll leave it to the smarter folks…
1 Like
Yeah my whole install is pretty wonky. App control isn’t working at all - echo not working either. But some stuff (motion controlled lights, minimote) are OK. Clearly a backend issue. Hub went offline briefly today, too.
Im having the same issue as of arriving home from work tonight. Just wanted to continue the +1 so Samsung sees how many are affected and addresses this issue.
Noted this in another thread, but Echo turned on bulbs, but not outlets, when I asked it to turn on a group. Had to control the outlets via ST app.
ST did put out a status note that there are problems with routines. Could be related.
Exactly the same here.
At least with SharpTools, I can control all NON-LOCAL devices.
If I manually move a device to the cloud (by editing the device to use a cloud copy of the device type), I regain control of it with SharpTools.
Would be nice if they’d update the community as a whole. Own up to the issue.
maybe it’s time to charge for the service and pay the developers more
Or…it’s time for Samsung to invest in development first to stabilize the product and demonstrate that they can deliver something worth paying for. They’re a huge company with plenty of capital, not a crowd-sourcing startup.
@DParker, samsung is in business to make money. i don’t mind paying for a service even in its infancy. a small fee, say 5.00USD/month, would suffice to fund a more professional team or at least pay existing personnel sufficiently to keep their attention. and a pound a month wouldn’t be noticed by most users.
it’s true that, ordinarily, a corp like samsung would develop first, release second. in this case they put the horse in front. that’s so - but in a way, i admire that heterodoxy. they certainly can’t withdraw the product at this point for further development. for myself, i already find the service useful enough to warrant a small monthly payment & i suspect many others would also go along with it - albeit not without a grumble or two, certainly. me, i’d pay right this second for a coder with the foo to find and fix the b0rked OAuth flow.
I am also affected by the problem. Haven’t been able to use echo to control Smarthings devices for over twelve hours. Echo still works fine with my harmony hub.