bamarayne
(Jason "The Enabler" as deemed so by @Smart)
21
Hi Dan and welcome to EchoSistant! We’re glad you’re here.
Please let me know what you find out of order in the Wiki and let me know what order it should be in. I wrote the way I install it, but I’m trying to make user friendly.
Also, please let me know what custom slots are contradictory… our free speech engine doesn’t conform to the “Norms”… I remember being told back at the beginning of this… “I can’t believe your code even works, let alone works as good as it does!”… So, just and fyi, ES does things differently than what you would expect.
Please post screen shots of the Live Logs… then we can find out what the problem is… but did you add the “Bedside Light” to your list of devices?
Don’t worry about this… not an issue.
Thanks… we really enjoy it… and remember, this app is in full blown development by TWO developers… changes happen almost every single day.
Congrats on installing the app! We know how painful the initial set up is. But the good part is that once the Lambda is connected to ST, things get a lot easier. I strongly recommend linking the Github to ide, or the next annoying thing you may notice is our crazy update releases, which sometimes can be daily.
If you don’t mind, the next time Alexa appears to have heard the device name correctly and the command, I would like to see a screenshot. There is something that didn’t match right. The EchoSistant is using a 1 to 1 match process of device names, to avoid issues like “I turned the light on, but the room is still dark”. We’ve had great success so far, with limited error rates, but…of course Amazon sends us what Alexa thinks it heard so sometimes we do see ‘accidents’ like the one you described.
I’ve had them linked for a long time now, so that’s not an issue.
I’m a bit tapped out for the evening and need to use what’s left to entertain my grandaughter who is here for the weekend, so I’ll look into getting you and Bama the requested info if I get a chance tomorrow.
Thanks for the feedback.
1 Like
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
27
No problem… that initial install is a beast… but it is worth the trouble…
You got PM. There’s one less error now and it’s on a different line. I notice that the fCommand comes back as undefined when looking for individual feedback but not when I ask what doors/windows are open/closed. Thx
1 Like
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
29
Send this to me please
bamarayne
(Jason "The Enabler" as deemed so by @Smart)
30
UPDATE UPDATE UPDATE
Well, it seems that we broke something major in the release with feedback… but that’s ok… It’s fixed now.
Please do the following, and I apologize for any inconvenience
Take a look over the revised list of commands for feedback located here ~ http://thingsthataresmart.wiki/index.php?title=EchoSistant#Feedback ~ Please remember that this is not an all inclusive listing of commands. Other phrases will work, and some of these may not work for you. If you find something that is not on the list, let me now and I’ll add it.
INTRODUCING A NEW ECHOSISTANT PLUG IN MODULE
zWave Thermostat Manager
The ever popular zWave Thermostat Manager smart app is now a fully functioning integrated part of EchoSistant. Control you thermostats from within your EchoSistant Environment.
This integration is optional and is at the entry stage. The integrated version provides the same features and functionality of the stand alone app, but gives the convenience of being with your ES smart app. This app add on is also being geared up for active development. Enhancements are on the way! So, stay tuned for more updates!
Nothing is better for Nest than Nest Manager by @tonesto7 . This little app was mainly for the Zwave thermostats. We decided to bring it in the EchoSistant because it’s the easiest way to give our thermostats a voice.
I’ve just had a look at this and to be honest from a quick look it’s really good. As you say, nothing is better than Nest Manager but this comes a close 2nd and for non Nest thermostats this would be brilliant alternative.
It’s working perfect now guys. Thx for the quick turn around too. One thing i did notice is that my list of devices was missing my dsc contacts when generated. I’m able to select all my devices in the echosistant app however. My dsc motions came through no problem though. It must be something with the device type used for the dsc integration I guess. No big deal, I just added them manually to the custom slot. Thanks again!
Ask Home what devices have low batteries…OR what devices have low battery levels…(of course the IN connector works best in this case: Alexa what devices have low batteries IN my Home - assumes your Invocation word is my Home)
What do you mean by correctly? Just asking if they are wet or dry?
OK didn’t try that sequence. How is low defined? I was thinking about getting battery levels of devices below say 50%…
Re: water sensors, are they still reporting or updates within the last day or so… is what I was thinking. They are only verified as working with a splash of water. I guess a device health check
Ah, two things you need. Go in the app, select Main Home Control, then click on Change Defaults. Scrolling down, you will see a section called Activity Defaults. That’s where you set the battery level (lower than 25% is the default) and the inactivity time frame (24 hours is the default). I set mine to 72 hours.
To ask Alexa to give you the inactive devices, well just ask: Alexa what devices are inactive in my Home…
