[RELEASE] Echo Speaks V4

⚙️ Custom Apps and Drivers
,
2113

I am getting the same warnings as you:

image
image1217×147 41.3 KB

As you can see, the 'Uh-Oh', warnings are also happening. Here is the portion of my webCoRE piston that's causing the warnings:
image

Note: The variable, 'EchoGoodbyeText' = Goodbye!

This piston has been running without issue using Echo Speaks for over a year - until about two weeks ago.

2114

@Bruce123 @lflorack1

I am not seeing those errors in my logs and I send text to my Echo devices daily.

I think you both may need to redo your Echo Speaks cookie setups. The Cookie Authentication Cleared by Device warnings don't seem right. Are your devices showing as online?

image

2115

Thanks for the response and suggestion.

Yes, all (13) of my echoes are online and all other text commands to Alexa are working fine. Also, according to my Echo Speaks Tile (@thebearmay), my Echo Speaks cookie on Heroku is up and running as well.

Thanks again for the response and suggestion.

1 Like
2116

Where can I find this? I searched, but did not see anything.

2117

Two Links

  1. ES Tile Discussion (@thebearmay)
    [RELEASE] Echo Speaks V4 - :gear: Custom Apps and Drivers - Hubitat
  2. Device Code: https://raw.githubusercontent.com/thebearmay/hubitat/main/esTile.groovy

Here's what it looks like on my dashboard (combined with Tile Builder @garyjmilne ):
image

2 Likes
2118

As of yesterday (7 April), these errors have disappeared, and the pistons controlling the voice and music output have started working again. This may have had something to do with the changes that are going on in the background for the new 'Alexa+' initiative that's coming.

2 Likes
2119

I also confirm that everything seems to be back to normal today, including track info.

2 Likes
2120

I just started playing with an Echo Input to feed into my whole house audio system. Seems to work well.

I noticed that the now playing information - artist, song name, cover art don't update in the device unless I hit refresh? Or hitting pause and play.

Happy to look into the code but was wondering if anyone had any pointers?

2121

If you are getting that info from Amazon, it has been an issue for me for years. Seems to be related to Amazon.

2122

I haven't looked into this in detail yet. I don't know if the Now Playing information is available to all echos or just certain ones? I don't recall seeing it on the traditional echos. I just got this echo input to test hanging it off my whole house audio system. It seems to work well and in theory is a much cheaper version of what I am currently doing with my Russound MBX Streamers.

I wrote a driver for the Russound's and I have to listen for updates coming from the player and when I see a new song starting I parse the information coming from the player and refresh the fields.

Presumably the Echo Speaks driver is doing the same thing but either not able to see that it is updated or is not correctly listening for it? I took a quick look at the driver and it is several thousand lines long. So wanted to hang it out there first before I dive in?

I did log a bug in GitHub but the last bug I logged there in January was marked as investigating and nothing since. I am not sure if this is being actively maintained as the GitHub shows no real activity this year and I see @tonesto7 has not posted this year? Maybe I missed something in this long thread about end of support of lower support or something?