Would this have effected wemo stuff also?
What problems are you seeing?
I am able to actuate WeMo devices, but SmartThings are not seeing that state change. So it’s kinda like blindly turning things on or off.
I am also not seeing anything get triggered by WeMo Motion sensors - but I don’t think that is WeMo specific - I’m not seeing any sensor triggered events at all.
I have a ST motion sensor that is supposed to trigger a light to come on that is attached to a Belkin Wemo switch. It’s not working. If I change the action to come on at a specific time, it works perfect. I can also toggle the light on and off with ST. The problem seems to be limited to the motion now, but it sounds like this is part of a larger motion issue across any sensors? If I look at the console logs, motion is being detected properly by my ST motion sensor.
I’d say the issue is that the ST platform appears to not be processing any sensor input.
I have tried a bunch of different inputs and they all seem to not be processed.
The strange thing is that the log shows inbound events from the devices, so the platform is aware of the trigger.
I don’t know the inner workings of SmartThings - but I would suggest the message queue that they are using to advise subscribed applications of events is not working.
It is really disappointing that this has been offline for what looks like 48 hours now and either has not been detected, or hasn’t been resolved. Either way - a notice should have been posted somewhere advising of this sort of outage.
I am not sure if it’s a global motion sensor issue as my Aeon Motion sensor is working with my Hue lights. I added my Wemo devices yesterday morning and re-added them and I thought that was causing my issues. The Wemo devices have not been very stable on the ST platform (it is Beta after all). I really regret buying these Wemo devices, but did so before home automation hubs started to become more common.
As far as support, I’ve noticed the weekday support is excellent and they get back to you pretty quickly. However, weekend support is spotty and it’s probably due to resource issues. These are the growing pains of a growing, new company and we are feeling them. I still believe in the product, people and company. For the price, it’s very competitive with other controllers out there. I cannot believe Revolv is $299. That blows my mind.
Aeon Motion Sensor not working here with a WeMo switch. Removed and tried re-adding all my WeMos, but the WeMo smart app is now unable to detect any of my WeMo switches/plugs (!). (The WeMo app from Belkin works no issues)
Perfect timing too - I just hooked the Aeon motion with the WeMo switch yesterday morning. “You will never have to reach for that switch again!” I proclaimed to the wife. We get back after home around 8pm, and no light even after some frantic waving in front of the sensor. She is definitely not happy with my recent HA investment
(I am able to see the Aeon sensor report motion/temp/etc correctly though)
Yep, seems like all sensor input is being ignored…
Status.Smartthings.com reports operations normal across the board lol
This right here is the kicker. I am OK with things breaking because we cannot expect them not to. But there needs to be a system in place (that works) to alarm the more technically inclined of an issue.
Status.Smartthings.com has never been useful for me as it seems to be updated by a person and is not automated. An automated system with up down status, message queue statuses, and status of then link between S3 and Smartthings would be great! This could be an amazon issue for all we know but with out us knowing we, by default, blame SmartThings. The more information us developers and technical people have the better. If we know what’s going on we won’t flame the message boards;)
Because of the lack of information I have removed my hue lights as a part of my own troubleshooting and now cannot add them back… If I had information before that I wouldn’t of done my own troubleshooting… I guess that’s the rub of being a break/fix server troubleshooter by day haha.
Yeah… that’s the first thing I checked when my lights stopped being controlled; obviously they need better error checking. Spent the better part of a couple of hours trying to track things down. Luckily, I accidentally clicked on my smartthings community bookmark instead of the API bookmark and saw this post at which point screams and smart expletives ensued.
WAS about drop upper part of $800 on smartthings for new house in week or so. Now I am rethinking this. Even though ST seems more active in development than vera, at least their system is not fully reliant on servers. Not going to be an easy decision. Very disappointing.
I’d be careful with Vera. Seems like a better option sometimes but I’ve had it and I can tell you its not as good as Smartthings.
100% reliance on the cloud is a big issue for me as well. I love ST and I think it has a lot of promise. But I’d never use it in its present form for security or anything else mission critical. Things that sorta work most of the time are worse than things that simply do not work. Try convincing your wife that home automation is a good thing after she goes for a walk one day and can’t get back into the house because the garage door won’t open. (Yes, “the power is just as likely to go out”, blah, blah, blah. I don’t remember when was the last time my power went out in this house, actually.) The hub must perform the mission critical tasks otherwise it’s just a toy.
BUT! I also think it’s a fantastic opportunity for ST to introduce a Pro model that has the smarts to run the apps, a backup power, more connectivity options, etc. Lots of very cool engineering challenges. And lots of potential.
Hey guys, we’re really sorry for the inconvenience. As you realized we ran into some recent trouble with actions and alerts not working as expected. We’ve isolated the issue and corrected it. We’ve updated our status page accordingly and things should be back to normal: http://status.smartthings.com/
If you are still having trouble though, please feel free and shoot an email to firstname.lastname@example.org
Thanks again for working with us!
Reliance on the cloud is not an issue at all. There are tons of cloud services we use every day that work very reliably. The whole point of a cloud infrastructure is redundancy. The Amazon EC is highly available and reliable and outages happen once in a blue moon.
SmartThings issues and outages, on the other hand, happen much more frequently. This is an implementation problem rather than one inherent to the cloud infrastructure. It’s evident, however, that they have been making a continued effort to improve the reliability of their backend. Things used to be much worse only a few months ago, and are getting better and better.
As for status updates regarding the ST backend: Please, subscribe to updates at status.smartthings.com.
Forums are far from ideal medium for reporting and resolving bug in the system. If ST is serious about living up to their aspiration of becoming an “Open Platform”, they should open up a real bug tracking system to developers.
Would this outage have caused my Siren to go off last night for no reason…?
Wife was not happy with me…2-weeks in to starting Smartthings.
Kudos to Ryan and the ST team. I reported the issue at 11:23 AM and they had it fixed and a reply to my support request by 11:59 AM.
I have almost always received immediate support using email@example.com
I use the forums when I want to post or ask to you all (the community of users) something.
Now this is my opinion, but knowing the dudes and dude-ttes at ST, they’d be open hearing what the community has to say.
It is an issue for me. I don’t need a security system that’s easily circumvented by simply unplugging my broadband cable. Nor do I need a flood alert system that’s down just for a couple of hours at the wrong moment.
I have a few HA devices that I made myself - all of them are capable of working completely autonomously. Because outages happen. Even if you achieve five nines in your datacenter, it’s of no use to me because of all those wires between your datacenter and my house. Realistically, if you’re sufficiently paranoid, have a generator, an array of solar panels on the roof and a stack of batteries (all of which I happen to have, but for other reasons), you’ll still be lucky if you manage even two nines. And two nines is four days of down time - a lot can happen in four days.
I’m glad it was fixed within an hour of your report, but the fact remains that the issue was reported here almost a full day previous to that. I think this is what needs to be addressed.
Whether it is more error handlers in the app that automatically report broken throughput, or something more than what currently exists on the server side, something should be in place to monitor and report this kind of failure.
I am hopeful the causes of various failures, as they occur, are added to autonomous routines that are designed to monitor, report, and even fix future occurrences if the possibility exists that they could be reinstantiated.
The data connection issue with your security system is a different one, though: You’ll have the same problem with an old-school monitored security system. If someone cuts your phone line, an alarm will never go through to the monitoring company. Unless, of course, your security system has a cellular network failover…
The same applies to SmartThings: Connect your hub to a UPS and a router with integrated 4G failover to account for power and data connection loss. These days, both are available to the SOHO market.
And you are right: Even with 99% availability, there will be an average of 90 hours of outages every year. If that happens while your basement is flooding, then you’re out of luck. I’d argue, however, that for a consumer home automation system that would be acceptable for a great majority of users. For example, knowing that I would be properly alarmed 99% of the times my basement were flooding, would leave me satisfied.
The problem is that SmartThings currently does not mirror the reliability of the available cloud infrastructure. There is some sort of (albeit usually short-lived) backend issue roughly once a month, and things like a siren randomly going off is not an availability issue - That’s just annoying. Extending compatibility with other devices is great and all, but focusing on the core competencies is really mission critical if they want to become the de facto standard in modern home automation. Reliability is paramount, but blaming cloud infrastructure is just being lazy, when we really should be breathing down SmartThings’ neck to improve their backend reliability no matter the implementation details.
Again, in their defense, they have been promising a continued effort, and improvements have already been made!
On a separate note, you should definitely share some details about your generator / solar setup That sounds really awesome.