@nathancu that’s my wife when it comes to egg timers …
This is turning out to be more complex than i anticipated
I haven’t been following along for a while and it wasn’t obvious from a search… can this new/2020 skill trigger voice notifications via SmartThings or WebCore like the old EchoSpeaks smartapp?
No. It cannot.
Almost a year later and things are still a mess
Some, sort of, and it depends on the details.
You can use whatever logic you want on the smart things side with the end result of turning on a virtual switch which is also a virtual sensor, and then you can use that virtual sensor changing state to trigger an Alexa routine. (Assuming that everything is working the way it supposed to, the new skill is much glitchier than the old one was.)
At that point, you can have the “that“/action in the routine be to speak a preselected “notification.“
All of that works fine, when it works.
For example, I can have opening the front door cause my echo devices to say “The front door is open.”
I can also combine it with a presence check to say “Michael is home.”
But echo speaks could work with variables, so that you could change what was said on the fly. You can’t do that with the new skill method. So I believe in echo speaks you could have just one rule and insert a different name depending on who had just arrived, where with the new skill method you have to set up one routine for each person.
You could certainly set up a voice notification for something like “the mail is here“ if you have a detectable sensor to act as the trigger. But you have to have one routine for each phrase you want to speak, you can’t change any part of it. And you are limited to a total of 99 routines altogether.
All of which is to say some people can get everything they want just with echo routines, assuming the smartthings skill doesn’t glitch. But you could definitely create more sophisticated logic with fewer total rules using echo speaks.
Voicemonkey was working great for this up until a few days ago, but Amazon took it down
Hopefully it will come back soon. The author of the skill has been posting updates on the thread linked below.
Hi TIm…I’ve hit my max 3 replies for a topic…I’m not sure when this gets lifted but when it does I’ll be sure to keep posting updates. Otherwise please visit: https://voicemonkey.io/status for the latest
Thanks I’ll keep checking your link and can update on the other thread linked below when it is working.
I think that posting limit is temporary when you newly register. It should go away as people like and respond to your posts.
I’ve been using the Alexa skill to make door open announcements. Normally Alexa will sound a tone followed by the announcement but for the last few days Alexa makes a “boop” sound, then the tone followed by the announcement. Anyone else hearing the “boop”?
I still have the normal tones before and after each Alexa function. I have always received a before and after tone, even though I have Alexa configured to only sound a tone following a task completion. If I choose a before tone, Alexa still gives an after tone as well.
Only way I’ve found to “fix” this is to turn off both the before and after tones. A bug that has never been fixed in all the years I have used an Alexa.
This is the longest topic I have seen. I have had problems with Alexa not able to voice control some ST lights but able to control them with a button push on my iPhone screen. Turns out you can solve this problem by renaming the device in Alexa.
That is a great tip, thanks for sharing. The voice integrations are pretty complex so there is a lot to talk about!
Any status update on the changes to allow users to select which devices are shared with Amazon Alexa and Google Home? It’s been a year since the new integrations were released, and about 8 months since it was mentioned that a fix was in the works…
The Smartthings Alexa skill got updated 2 days ago. Anyone want to try unlink and relink and see if we got device selection:
Edit: Still the same
Glad you tested it Andreas, I really did not want another 50 devices duplicated, shame it is taking so long to change, I am actually more pis##d we STILL do not have and probably never will have as it has been so long, Shortcuts to individual device automations on the devices page, ala original app, that for me is my NO1 annoyance followed by the alexa issue
Hey Mike. Definitely with you on that one! I have a light that turns itself off at arround 6 in the afternoon and i have no idea what triggers this behavior! For me this is the biggest issue with the new app. I can live with the rest. Even with Smartthings exposing everything to alexa.
Check the Alexa App to see if “Hunches” is enabled. This is often the cause of seemingly random events like this. If you have HomeKit integration, Adaptive Lighting might also be the cause.
Thanks i ll give it a try
Yup, similar here Andreas, a light that turns on for no reason, I have given up keeping the system tidy and organised, it mostly works fine but the days of resolving issues quickly and easily are 3 years gone now
With ST being so poor in the past and Echo reliable, alot of automations went to Echo, now when issues do appear I just cba to trawl through multiple ST actions and automations and the terrible way that it is laid out, Echo is just a better UI to find and resolve issues
In the UK I don’t think we have hunches in Echo, I couldn’t find any mention anywhere
For those that never used the better older app, each device had a tab, that when tapped listed all the automations that particular device was attached to, you did not have to go back into multiple lists of poorly auto named items that were not relevant to that device, this made system maintenance easy, logical and quick, it has never been re implemented and as it has been years now I suspect it will never appear
The current app is designed by software engineers technically involved with the system, it is not designed for jo public to pick up and use easily which it should be, oddly the jo public version is the correct approach, for multiple reasons I can’t be bothered to list but the bottom line is, the easier and more logical it is, the less support is required and the more people will pick up the system and use it, and let’s not forget accessibility for disabled… it appears this current app is shamefully poor and to fix that JD should have (ST staff member ) next to his name and be paid for being chief accessability engineer, you will never get better