I did briefly play with Zones.
In my example I used the same volume settings (cut& paste) I do realistically use different volume settings for each device I talk to; some are hooked up to powered speakers, some are dots vs shows, and some are just in a quiet location. A single zone will not allow me to do that. I guess I could create 5 different zones...
As a heads-up I also dot not really use ES Actions; again I played around with it. But, and this is in now way a criticism, the power of WC and RM far surpasses the Actions ability. Call it personal preference if you want.
What I would absolutely love is some form of a speech queue.
Not a queue for speaking the same thing to 1-x devices, but a queue where you can speak 20 different things one after the other, and the app will queue them up and speak 1 at a time without killing the previous speech output. Correct sequencing will be up to the end user.
With the regular speech commands there is a queue. (It was broken but I fixed it in 3.6.0.0)
The queue prevents repeats and handles rate-limits from Amazon.
The only negative of the queue in its current form is that it does not cover announcement commands, I plan to add those eventually and maybe the other commands.
The last time there was a server update I ended up forking the ES github and using my fork when creating the Heroku server. Quite honestly I forgot why I did that until a few minutes ago. When I logged into the Heroku dashboard, it had already refreshed and rebuilt the server without any involvement from me.
When I set up the fork, I also installed pull to automate refreshing the fork. Pull can be found here. GitHub - wei/pull: β¬οΈ Keep your forks up-to-date via automated PRs
def playTrack(uri) {
if(isCommandTypeAllowed("TTS")) {
String tts = uriSpeechParser(uri)
if (tts) {
logDebug("playTrack($uri) | Attempting to parse out message from trackUri. This might not work in all scenarios...")
speak(tts as String)
} else { logWarn("Uh-Oh... The playTrack($uri) Command is NOT Supported by this Device!!!")
}
}
}
I am not an expert as you in Amazon Alexa, but I did a skill (copying and pasting from an exampel) in Amazon that reproduce an MP3 located in an HTTPS server. Could this help?
Second time I have given this app a try (last time was mid last year), and both times this app is the cause of my hub getting really slow and completely locking up.
The last straw was last night when my hub locked up around 11pm and the only way to bring it back was to pull the power plug. No app is worth the possibility of corrupting your hub, specially with the amount of work I have put in to my routines.
Anyway, with this happening both times I have tried this app between the space of at least 8 months I am assuming it will not get fixed. The feature set is nice, but if it is this destructive then the whole thing can't be used. Or is this only me having this problem? Seems strange though as I just followed the instructions as presented.
Does anyone know of an echo app that at least has the ability to send custom announcements to the echos? It's unfortunate, but I can't use this one.
Yeah it stays up for more than a few days......but it was noticeably slow to do everything. Getting half way down the stairs before the light turns on, for example, is unacceptable.
I don't want rebooting the hub every day to be a solution.
Fork is on the upper right. Once you have the fork in your repo, install Pull from above link. Install the Huroku server from your repo, The Pull app will keep your repo always up to date and Heroku will automatically update and rebuild the server.
Ahh, maybe I can get it to work if I set it up on smartthings, didn't think of that. Time to plug my smartthings hub back in I think....at least for echo speaks:
The Pull app will update your fork (every few hours I think) so your fork will match with any changes in the original repo. If your github has more than one fork, it will do them all so do whatever it takes to disable pull for anything you don't want to update.