bamarayne
(Jason "The Enabler" as deemed so by @Smart)
4561
Very very true. But as @SBDOBRESCU said, it’s all a matter of perspective.
I do not see this as a security system. I never have. I knew better before I ever ordered it.
I do not see this as a top of the line always wields found in a rich persons home HA system. I paid 99.00 for the hub and service.
I do see this as a tech that I enjoy and love.
If I wanted something that always did the same boring thing, that thing being what the company tells me it will do, that thing I can not manipulate to do anything else, that in the box thinking and only achieve what I’m told I can achieve…
I would buy the white box with the Apple on the front.
I pledged myself to only use stock everything for a month since the day @bravenel x-d the Rule. It’s been a week or so since I’ve only used modes, routines, Smart Lighting and SHM. I really want to get a sense of what is like to be a consumer. I am documenting failures and short comings. I hope I’ll resist for a month, although I almost reinstalled a few things because there is no way I can accomplish much.
7 Likes
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
4565
The official dictionary how? The clue is in the name of the language. I think my dictionary is the official one you guys turn your car headlights on during the day?!? What’s that all about?
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
4570
Come on now… I’ve been to Canada… Yay!
I lived in England… Super yay!
I’m from Alabama… So just be glad I didn’t say 'rithmatic y’all!
xAPPO, RF is not the issue. AT&T uses RF for their Digital Life alarm and it works flawlessly. The problem is the cloud. Offsetting too much to the cloud and having way too many pieces of the puzzle act as points of failure. From an unreliable internet connection to a temporary issue with an ISP backbone, to a DNS issue somewhere in someone’s server, there are so many things that go wrong before the SmartThings ever gets the chance to fail on anything, but we all blame it on ST. Because nobody can tell if the internet transport has anything to do with this when it might. The whole concept of having the executioner in the house but the brain in the cloud is … utopic, to say the least. Brains need to get down into the house and let the cloud handle only remotely accessible actions (integrations with IFTTT for instance).
To give an example, my integration with AT&T Digital Life involves a local server that connects to the Hub via local actions. I send a message to the Hub on its local IP. Well, wait… the hub then forwards my message to the cloud, the cloud processes it and then sends the new “state” back down to the hub. How is this optimal?! Internet is down, my local server cannot communicate with the local hub. This is completely wrong, by any standards. Logic needs to happen locally, when possible, or in the cloud when the cloud is really needed. Just my two cents…
I’m surprised that there hasn’t been press about this even before Bruce withdrew Rule Machine.
The simple facts are that if you compare the promise of the system that you see on Smartthing’s consumer facing website, with the reality of what it is capable of supporting - there is a gaping disparity.
The reason why it has taken so long to come to light is that we (in this community) are so heavily invested in the platform (lots of new compatible expensive hardware, hours of our time coding and setting up rules) that it is not in our interest to see it fail - we desperately want it to succeed because we want those promises to come true to justify our investment…
I haven’t been since v2 came around…But I have a different approach now, it’s called “drop it or move it”. If it doesn’t work, I don’t fix it, I just drop it or move it (to a different controller).