[RELEASE] Echo Speaks


Here's what I hope is a simple question. In RM, I want to program a morning sequence where I push a button and a series of things happens including playing a station or playlist from Spotify. How would I go about that?


@napalmcsr did you get it working on hubitat? Can you provide any help in terms of the steps you went through on Hubitat to get it working?


Writing this from work, but it is something like this:

  1. go to post 86 and click on the link CWWilson08 provided.
  2. log into amazon in that link.
  3. wierd file shows up, copy to notepad
  4. go to one of your new echo devices in hubitat
  5. find the executeroutineid in the device
  6. search the notepad file for the routine you want. there will be a couple routine ids for that routine. I kept trying the different ones until I got it to work. The logs show an error if you don't get a good routineid.


Installed to Hubitat using the provided instructions. Working great so far. Great job.


Hi all. My hub has been very slow lately and the only way to resolve my issue is to reboot it. Others are suggesting a custom app or driver as the culprit. The only 2 custom apps and drivers I have are Homecloudhub and echo speaks. Has anyone else had issues with their hub slowing down after installing echo speaks?


Nope. Echo Speaks not likely the culprit.


Out of sheer curiosity how many echo devices do you have in your home?


I have 3 echos connected to echo speaks but I have 6 Alexa device in total on the same network.

3 echos
2 cubes
1 fire tablet


I am getting the same logs. Have you found a fix?


@napalmcsr - just getting back to this. I'm lost at number 4, 'go to one of your devices in hubitat', 5 find the executeroutineid in the device. Thus far, I only have the one device in hubitat, I've only added the zwave tilt sensor at this point directly in hubitat. I can see in the logs that there are other devices that hubitat seems to know about from alexa, but they are not listed as devices in hubitat. What am I missing?

  1. Go to the new Echo speaks device and find executeroutineid

This makes it so you can run echo routines.


I created a Routine in the Alexa App to take a voice input and then play back the traffic and weather. I went through the process listed above but I don't see any "routine" IDs in my text editor. I have a couple of sequence IDs. Did I do something wrong?


@napalmcsr - gotcha - that makes sense now that I've read it over a few times. I've found the executeRoutineId(string rID) at line 1464 in the Echo Speaks Device. And based on @homeauto2112 comments, I see plenty of sequence IDs, but nothing called out as 'routine' IDs. Once we find an ID that meets the criteria, are we pasting that ID in the device code somewhere? I'm reading lots of stuff, but my later years are slowing me down a bit.


try the automation ID, you don't enter it into the code, but as an argument.

I test it from the echo device as the value you add under the button for executeroutineid.

After that I created a custom command in rule machine that I could use by rules.


Many thanks for this amazing app. I have just installed it and have a few things talking to me.
I don't see a way to enable/disable debug logging in the Echo Speaks app. My logs are full of debug log messages.


it is the automationid that comes before the routine.


Woww! Just installed this little nugget! So impressed! This opens up so many possibilities! Thanks for all the hard work in making this happen!

I do have one quick question what exactly is the trackImgHtml attribute for?


Ok, I couldn't get this working, so decided best to start over and see where I could have gotten off track. I'm back to the point where I've got the Echo Speaks app installed, Heroku seems to be working as expected, and my Alexa devices are showing up in the Echo Speaks app. I've tried the experimental tests, but thus far, I'm not getting any results - no announcements, no broadcasts, etc. My tilt sensor is also no longer recognized as a device in the Alexa app. So it would appear that nothing wants to talk to me. Any clues where to begin to troubleshoot? I've reviewed some of the common errors in the troubleshooting doc, but nothing seems to fit.


I did go to one of the Echo devices and am now able to play an announcement directly on the selected device, so it look like I'm better off than I had expected, at least from the communication between Hubitat and my Echo. Happy dance !!!


NV, figured out that the tilt sensor was there in Alexa App because of ST, not HE. Cleaned things up and have setup Rules machine to detect sensor, and now am able to send notification to Echo when garage door opens and closes.