Mine was working correctly 6 and a half hours ago. I can't narrow it down anymore than that.
Agreed... It's on the Amazon side. Further proof is that Spotify Connect isn't allowing me to play audio to any of the Amazon Echos right now. All the Echo devices show "Can't play this right now" in the Spotify app.
If this latest issue reinforced one thing, and one thing only, it is my hate of [the modern trend for] cloud integration. There is literally nothing that will still be working in 10 years time, whereas some of my old equipment from 10-15 years ago works just fine!
I'm in the middle of setting up your method, thanks for the idea. Don't you have an issue with your rule as written if the same message is sent twice in a row? The second message won't play because nothing has changed. Correct?
Yes. But I never send the same message twice. For example, when I use TTS for washer/dryer notifications, I use %now% in repeats of the notification text (Washer is done at %now%. Move clothes to the dryer). So each time the repeat occurs %now% is unique.
I was an ES user since the beginning, but the last update now locks my hub up consistently/repeatedly between 6-8 minutes from a reboot. Disabling ES fixes the issue.
As a result, I have installed /configured the latest of this TTS solution. No issue encountered during the setup etc., however, it only kinda works for me!
Note: I am on the "manual cookie" configure option, but lets get this out of the way - it is NOT the issue.
An "AlexaTTS xxxx" device was created in Hubitat for each physical device I have.
On all of my Echo Dots, from within the device itself, when I do a speak command, the silence is deafening!
Doing the same from my Echo Show it works just fine!
And now for the real puzzler, from the "AlexaTTS All Echos" device, it works for every single device!!! Shows, Dots, you name it.
But individually, the Dots are silent.
There doesn't appear to be anything useful from a log perspective; at least no errors being generated.