Echo->IFTTT->SmartThings->zWave deadbolt

if someone using voice to hack into my echo then security system to come steal my old crappy stuff is my biggest issue in life, i'll be a happy happy man. TBH, that isn't even in the top 50 things i'd be worried about. Home invasions, armed robberies, heck wall street insider trading killing my 401(k) are a heckuva lot more likely than that.
 
I think there are more possibilities that your family will take to the Amazon Echo like fish out of water and well, you can watch what happens.
 
Being on the left coast and on the left side of that big tectonic plate I would probably be more concerned with natural selection (mother earth) creating a nice and neat demarcation point than a home invasion or armed robbery these days or that your echo gets hacked.  (I mean with no internet transport it doesn't work anyways). 
 
I still read paper here some and thought this magazine cover was fitting for the original OP. 
 
EchoSleeping.jpg
 
Earthquake shmearthquake, right now its Jan 3rd and I wore a tshirt & light workout jacket to the gym at 8am this morning. I grew up in NYS and the ice storms/snow-related accidents killed multiples more. A home invasion or armed robbery is infinitely more likely, in any city you're going to see a few dozen/month get impacted. 
 
Yeah here went out to get the paper at the end of my driveway in a t-shirt and shorts.  The brisk walk down the driveway woke me up before breakfast.
 
BTW we had an ice storm last week here which knocked down my patio furniture and the ice glued it to my deck.  I tried to move it yesterday but couldn't walk on the deck as it is now snow / ice still frozen a bit.
 
It was a bit of a white and icy winter wonderland after Christmas here.  IE: it snowed big flakes then it rained and then it got really cold and solidified that nice winter look to last a bit.
 
IVB said:
Got the new SmartThings setup within minutes, locked the front door deadbolt with voice within minutes.  No CQC needed, so you HomeSeer/other folks could do this pretty easily too.
@IVB - We published our Amazon "Skill" a few weeks ago, so HomeSeer users can do this natively now using the Echo with commands like "Alexa, tell HomeSeer to lock my door".  FYI
 
macromark said:
@IVB - We published our Amazon "Skill" a few weeks ago, so HomeSeer users can do this natively now using the Echo with commands like "Alexa, tell HomeSeer to lock my door".  FYI
 
Thats cool. Yeah, I hear folks are doing the same with CQC and it only took (some 15m, others 1-2 hours) but this was even simpler as its not a "skill" but rather native. From what JKMonroe explained native moar better from an accuracy perspective this way on the CQC forums: (All on the Amazon side, nothing to do with CQC or HS or ...)
 

lucky for us my wife is a computational linguist.  she says that what most likely is happening is Alexa is programmed to listen for the prepositional phrase. [VP(V)[PP(P)[NP(N)]]]
 
so the entire thing is a verb phrase [VP]; the verb (turn/set/run/load) is followed by a preposition phrase [PP] and preposition (on/off/to), and finally the noun phrase [NP] and noun (lights).
 
it's why she responds so well to the lighting API: Alexa, turn (verb) on (preposition) lights (noun), but gets a little confused using the skill: Alexa, tell (verb) SKILL (noun) to (preposition) turn (verb) on (preposition) lights (noun).
 
Been looking at ways to interface the Amazon Echo (Alexa) with my HAI Omnipro for control of devices and really not liking the AWS or (local) internet server based development options.  After a bit of researching, I'm fairly impressed with some of the thought in the SmartThings unit relating to defining objects (including virtual ones) and their API's.  It's nice that SmartThings now talks directly with Alexa without having to do the whole "Alexa, tell XYZ to ...".   I'm going to look at defining my HAI objects (lights, locks, thermostats, buttons, etc) in SmartThings and then use the Alexa/SmartThings integration to control the HAI OmniPro.  A side benefit is that SmartThings also gives you free mobile apps for controlling what you've defined in the system.
 
Anyone else look at going this route?
 
not sure i follow the question, but I use ST with the Echo. I decided to only expose lighting and not locks, but I can say "Alexa, turn <light> (on|off)". I could do the same with locks too. I know jkmonroe does much more than I directly.
 
My question was really just relating to whether anyone was using the SmartThings controller as a front-end/intermediary for interfacing with their existing systems (e.g. OPII or M1).
 
I like keeping most of my system logic in the OPII, but with the ST, I could add systems not easily supported otherwise (like proximity logic based on cell phones or Alexa control).
 
IVB - are you just using the built-in Zwave control with your lighting or did you write modules to talk to the M1?
 
First of all, my disclaimer, I don't own or use a ST relay hub.  But I was under the impression that you need more than just a ST relay hub and IFTTT to communicate with  an OP2 controller.  I think you need an additional product to connect the ST to the OP2 such as CQC or HomeSeer. Otherwise, it would probably be impossible to control the OP2 specific hardware such as thermostats or possibly a WaterCop attached to a OP2.
 
AFAIK, there have been a few requests to develop a groovy interface to the OP2 but nobody as of yet has undertaken the task.
 
Please correct me if I'm wrong but that's the way I understand it.
 
JonW said:
My question was really just relating to whether anyone was using the SmartThings controller as a front-end/intermediary for interfacing with their existing systems (e.g. OPII or M1).
 
I like keeping most of my system logic in the OPII, but with the ST, I could add systems not easily supported otherwise (like proximity logic based on cell phones or Alexa control).
 
IVB - are you just using the built-in Zwave control with your lighting or did you write modules to talk to the M1?
 
Just the built in controls. I have CQC as the bridge to the M1.
 
BobS0327 said:
FAIK, there have been a few requests to develop a groovy interface to the OP2 but nobody as of yet has undertaken the task.
 
Please correct me if I'm wrong but that's the way I understand it.
 
This is correct - you need custom code in groovy to make the integration.  That's what I'm looking to do.  This is where the ST appealed to me since it has the infrastructure to actually host the custom code and it has the ability to create virtual devices that you can map to your other systems.  I've already built a server app that can accept HTTP & TCP connections to interface to the OPII, so I'll extend that to be my bridge to talk to the ST.
 
Also, I'm not looking to use IFTTT at all.  Not a fan of putting the logic out on the cloud (which brings big latency issues).
 
SmartThings can't handle raw tcp socket connections.  not sure if that matters to your scenario, but it might.
 
the Echo Lighting API is what is used for these virtual devices, so you get on/off/dim/brighten/set as your command set.  it's really a pain in the ass except when turning things on, or actually controlling lights.
 
i currently have CQC, Wink, SmartThings, Hue, IFTTT, and Talk to Nest hooked up via my Echo.  99.99% of our usage is the native Hue integration.
 
Back
Top