Mine has been temperamental. Sometimes I have to say home and sometimes I have to say house to get the same command to work. It’s not consistent on when it does this.
Alexa, tell home good night
I’m sorry but echosistant wasn’t able to take any actions, would you like to try again?
Alexa, tell house good night
ok I’m running the good night routine
Next day:
Alexa, tell home good night
OK, I’m running the good night routine
I thought I’ve followed the wiki pretty close but getting
Error: A Lambda function ARN should be between 25 and 65,535 characters., any idea?
NVM, just set to no for “Provide geographical region endpoints” solved the issue.
Other issue I am getting
I am not sure you will get an answer to this…The whole original Echosistant team jumped ship from Smartthings and work for a company called Hubitat.
Well i’m pretty sure that’s not a true statement.
They didn’t jump ship. Their time is just far more occupied now.
Didn’t mean the new team…just Jason and Bobby…but checking out LinkedIn today it appears Corey is also working for Hubitat as well. And while this doesn’t mean they CAN’T continue developing here, I don’t see why they would.
Just saw the the end user here wasn’t getting a response. That is all.
I know you meant well 
The problem is that neither solution fills all the cracks so I think using both will be required. There is a bridge solution somewhere in the community that allows communication between both environments.
Just getting into this and trying to gauge its status. Is a team still developing and supporting this, or is this destined to become broken at some point? Thanks
News about Echosistant…
For those of you who have been patiently waiting for the release of v5, we would like to echo the exciting news that @MichaelS shared.
The Echosistant team is happy to announce that we have reached an agreement with Michael, and that amazing ES v5 game changing features will be merged into michael’s awesome Ask Alexa app. This is something that we’ve always wanted, and we are thrilled to hear that Michael was able to get passed our design differences for the betterment of our community.
Thank you Michael for working with us. We trust you, as many people in the community have, to take Echosistant to new heights.
This really is the right thing to do and the only thing that would greatly benefit the ST community.
While some of us have been busy working on Hubitat, as Michael pointed out, we will never abandon our user base and the Echosistant team will continue to monitor the needs of this community and contribute any time when there is room for improvement.
Thank you all for your support over the years. The Echosistant Project has been an awesome experience for all of us.
This is by no means a goodbye, but rather a see you soon, from all of us:
@coreylista, @bamarayne, @SBDOBRESCU, @jasonrwise77, @tonesto7
Hello, and I’m Back!
I’m no longer with Hubitat… I’ve decided I’m retiring and preparing to move to the beach… seriously. So, for those of you that are still interested in using EchoSistant, I will continue the support of it.
I am also going to port a version over to Hubitat. Look for me there!
Jason
Welcome back.
If you’re going to support echosistant, how will this effect the combining of echosistant with askAlexa?
Quoted from another thread:
I get: “Sorry, I heard that you were looking for feedback on something but Echosistant wasn’t able to help”
Is this command not in the regular github installation files?
I’ll check on this… I’ll get back to you asap.
Would someone (@tonesto7 @bamarayne @MichaelS ) please clarify the roadmap(s) for Echosistent and Ask Alexa ? For both ST and HE, if possible.
I think this sums it up: [RELEASE] Ask Alexa
And the Echosistant message pretty much says the same thing: [RELEASE] EchoSistant v4.5
Are you looking for specific features or just clarification of what is continuing to be developed or not?
Thanks, Michael. I have early releases of both Ask Alexa and Echosistent. I’ve held off on putting too much time into upgrading until the new and improved installation method is released. In the mean time, I’m evaluating and slowly moving devices and automations to Hubitat. So, there’s a lot of transition and I just want to make the best long-term decisions for how to implement voice control.
For instance, are there going to be two forks of Echosistent: one by @bamarayne and one by you and @tonesto7 ? Will either/both Ask Alexa and Echosistent be supported on Hubitat?
It is my understanding there will be NO more Echosistant on ST. That can always change, but there will be no forks from me…and there will be continued development on Ask Alexa, integrating the functions users want…Most of the features of ES4.5 are now in Ask Alexa as it is, including some of the proposed but never released features of ESv5 like Echo Identification.
As for Hubitat, I have no plans for that platform, but only because I don’t own it. I am investigating this, but without a mobile user interface I believe I would have to do a major conversion to that platform. Who knows…more ST outages gives everyone more time to investigate other options 
Figures…I finally bit the bullet and installed Echosistant… And now I have to install Ask Alexa. Don’t know if I’m willing to go through the whole Lambda process again, lol.
Actually, the hardest part is actually creating the Lambda account. Ask Alexa has a feature that gives you the complete code to put into Lambda. One copy/one paste…then you are done with that section. Since you already have the account set up I am betting the Lambda piece will take a minute or two to create.
I am here to help if you need it.
We’ll see…ES took me the better part of a day, although I had to research a lot of stuff along the way (like the geographical endpoints. What a PITA). I’ll be sure to bug you when get the nerve to start. 
Is there an easy way to disable ES while I’m trying out AA? Do I just delete the smartapp from the ST app?