I’m about to release version 4.5. It’s a major update to 4.0.
EchoSistant version 5 is in work, and has been for about 4 months. Our very skilled team is working daily to bring an experience you’re not going to believe.
1 Like
So are Echosistant and Ask Alexa the same thing, but Echosistant doesn’t require the extra “ask” in your command?
No, they are not the same thing. They may look similar because of the end result, but EchoSistant gives the user a freedom over how they talk to Alexa. It’s designed so the user is required to spend a minimum amount of time in the mobile app and they gain the maximum out of Alexa. That is why we keep the app very utilitarian. No need for pretty graphics when the user doesn’t need them.
1 Like
@bamarayne
I really like the idea of no invocation.
I started into this whole situation due to my garage door, when using the default integration, started making me say “Alexa, turn on/ off the garage door” which makes no sense in natural language. It used to work fine when saying “Alexa, open/ close the garage door” and then one day it started only accepting the on/ off commands.
This problem is what has led me to community created solutions such as yours and Michael’s.
The icing would be to issue “and” commands so that this truly would be a more natural language.- Or a series (3 or more devices-- but maybe that’s a little much. haha)
Again, any custom app within Alexa has to have an invocation word to run the skill. However, what hasn’t been mentioned is the fact you only have to open the app once…so your conversation could go like this…
Alexa, open Smart things
Open the Garage
Turn off the patio
Unlock the door
Since you have Ask Alexa already installed you can do this today. Just modify your continuation commands in the Settings area…might eliminate the need for the “and” here…
Yeah, I didn’t know I could do that… That would work for me. I didn’t think about doing it that way. Thank you for your response!! You have been so helpful to me!!
@MichaelS
I notice you said that invocation was necessary when using a custom skill with Alexa. I thought the same. But in a post a few up from this one
It seems otherwise, but maybe I just don’t understand what I am reading. It sounds like he’s saying echosistant doesn’t have to use invocation?
Actually, EchoSistant does use an invocation.
Kitchen is the invocation. I designed ES to be user friendly and work the way we want it to.
Also, EchoSistant does continued commands, and there is no need to go in the app to set it.
Sometimes you want it and sometimes you don’t. Do you want to go into the app every time to turn that on and off?
In EchoSistant you just say…
Alexa, stop the conversation in the kitchen.
Or
Alexa, start the conversation.
What’s the point of voice control if you can’t use just your voice?
Jason is correct. While I use “Smartthings” in all of the documents as the invocation word, you can use practically any word you want. You can also add it to the end and use “ask” or “tell”. All of these have the same result:
Ask Smartthings to turn on the light
Tell Smartthings to turn on the light
Turn on the light using Smartthings
Turn on the light with Smartthings
I follow you now I believe. So Jason’s invocation word changes based on the Room the devices are in and yours is a single set word or words.
No. Just different philosophies. Ask Alexa can also be set up with multiple skills just like Jason’s and you can use the room concept as the invocation word. That works but adds extra effort as you have to create multiple Alexa skills.
I have an extension I will be releasing this week that will allow the room concept with a single skill name. So you would control the aspects of a room instead of individual devices. So the command would be like:
Alexa, tell Smartthings to turn on the {room name}
Alexa, ask Smartthings to lock the {room name}
Etc
You would still invoke the skill but now you can do neat things on a room basis.
And I did look at the compound (and) command and this is easily done with my current code structure. Will just need to make a minor tweaks and will include it in the version after next.
Michael is correct, very different philosophies.
With Michael’s room concept you are still telling smartthings to do something in a room, who it’s not really controlling a room.
Alexa, tell smartthings to turn on the lights in the bedroom.
In EchoSistant, you are actually controlling the room.
Alexa, turn on the lights in the bedroom.
Ask Alexa really shines when you start wanting reports on feedback about your home. You create macros! Then you just execute those macros to give you the information.
If you want to know what lights are on in the bedroom, create a macro and execute it. Though, I’m thinking that may change with his upcoming update.
In EchoSistant, you just all, Alexa, what lights are on in the bedroom. No need to create a report, just ask.
My advice, install both apps and see what works best for you. Heck, you may find that you get the best use out of both at the same time.
@MichaelS I’m looking forward to the compound commands. I know that didn’t work that well in the past, I hope you got the bugs worked out.
1 Like
Never tried the compound commands before today…but the way I structured the code I found it is rather easy to add.
While I disagree with you that creating macros is difficult, the room extension will auto create a report based on the devices you add to the room. And you don’t need to specify “lights”…just turn on or off a room and the lights/switches will turn on or off…lock the room and only the locks are locked…a new concept for Ask Alexa and it makes it insanely easy to control large sections of your house with one command.
My wife would thank you immensely (the non techie)… She is the one that was griping about “Alexa not understanding “and””. Alexa is stupid I remember her saying a few times… Now I can tell her, I have a guy that can make Alexa smart. haha… But I do admit, I find myself thinking, it would be very useful if Alexa understood the “and” …Alexa, turn on the Bedroom light AND turn on the bedroom fan… sounds nice to me and still very normal/ natural speech. lol
Thanks for the ongoing dialog. I am understanding how these smartapps are working a little better now.
1 Like
I definitely don’t want to have to setup multiple Alexa skills, that was kind of painful for me for the first time and I would consider myself above average with PCs. (no developer for sure but a good pc user)
Yeah…I tend to agree and from the informal polling I have done others agree as well…That is why I focus the documentation on a single source (SmartThings) with multiple destinations (switches, macros, etc).
Thanks! And be on the look out Friday for the next version!
That is amazing. Thank you for all of the talk. You say, the one I really want to look out for is the one after your upcoming one right?
Also, could you point me to upgrade instructions to make sure I don’t mess up my current installation.
BTW, @MichaelS and @bamarayne, you all are way too d>&# smart for me. So impressed with what both of you have built. Thank you all for sharing it with everyone. They are great!!
1 Like
I may have yelled a few other expletives at her a few times other than just stupid. Sometimes Alexa seems to be very hard headed.
@MichaelS and @bamarayne are both awesome code writers and community members. I only use askAlexa but either one is capable of a lot more than just alexa on it’s own or ST on it’s own.
2 Likes
That’s no kidding. I feel the same about Alexa.
Yeah, they are both impressive, @MichaelS and @bamarayne. I must admit.
Thanks for the kind words guys…