[RELEASE] Echo Speaks V4

dabber · November 2, 2025, 12:42am

When setting up TTS for notifications, etc. It goes through each device one at a time. Any way for it to work simultaneously? If there is no way, I might work with delays to see if I can get them to synch - not sure it's doable.

jkudave · November 2, 2025, 9:03pm

Setup a zone in the Echo Speaks app.

Pantheon · November 3, 2025, 1:14am

I did that and the notifications still daisy chain through my house.

thebearmay · November 3, 2025, 1:33am

Alternatively you could try creating a multi-room device inside of Alexa and sharing it back to HE for ES to broadcast to.

dabber · November 6, 2025, 12:23am

worked -- sometimes there is a very slight lag between the bulk and one device -- mostly all good. Better than all the virtual devices and routines in Alexa app.

terminal3 · November 6, 2025, 6:35pm

I have a 5th gen Echo dot but it shows up as a echo show 5th gen. I assume it uses the device type parameter to set this. The device type it returns is A4ZXE0RM7LQ7A, which is listed as a 5th gen echo show in the echo speaks app code. I saw in the change log the quoted line below. @jtp10181 is the device type wrong or is there something I need to do to get it updated? The device is working fine. I seem to remember there was some discussion in this thread about this, but I couldn't find it, it's quite a bit of stuff to look through.

[FIX] Added support for 5th gen echo dot and other devices. Thanks @jtp10181.

[Edit]I have removed the device and let echo speaks re discover it but it comes back as the same thing.

jtp10181 · November 6, 2025, 10:14pm

I have no idea why I got tagged on that notes line, it was someone else who added it. I am the one who added the Heroku url override to get that working again.

Anyway... I guess someone just got it wrong in the code, its here:

github.com

tonesto7/echo-speaks/blob/3030924f258af6009e655157053ee3acb7d55431/apps/echo-speaks.groovy#L7119


      
          
          // Amazon Echo Spot's
          "A10A33FOX2NUBK" : [ c: [ "a", "t" ], i: "echo_spot_gen1", n: "Echo Spot" ],
          "A3EH2E0YZ30OD6" : [ c: [ "a", "t" ], i: "echo_spot_gen1", n: "Echo Spot (Gen2)" ],
          
          // Amazon Echo Show's
          "A1NL4BVLQ4L3N3" : [ c: [ "a", "t" ], i: "echo_show_gen1", n: "Echo Show (Gen1)" ],
          "AWZZ5CVHX2CD"   : [ c: [ "a", "t" ], i: "echo_show_gen2", n: "Echo Show (Gen2)" ],
          "A4ZP7ZC4PI6TO"  : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 5 (Gen1)" ],
          "A1XWJRHALS1REP" : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 5 (Gen2)" ],
          "A4ZXE0RM7LQ7A" : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 5 (Gen5)" ],
          "A1Z88NGR2BK6A2" : [ c: [ "a", "t" ], i: "echo_show_8", n: "Echo Show 8 (Gen1)" ],
          "A15996VY63BQ2D" : [ c: [ "a", "t" ], i: "echo_show_8", n: "Echo Show 8 (Gen2)" ],
          "AIPK7MM90V7TB"  : [ c: [ "a", "t" ], i: "echo_show_10_gen3", n: "Echo Show 10 (Gen3)" ],
          "AQ24620N8QD5Q"  : [ c: [ "a", "t" ], i: "echo_show_15", n: "Echo Show 15 (Gen2)" ],
          "A1EIANJ7PNB0Q7" : [ c: [ "a", "t" ], i: "echo_show_15", n: "Echo Show 15 (Gen1)" ],
          "A11QM4H9HGV71H" : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 5 (Gen3)" ],
          "A2UONLFQW0PADH" : [ c: [ "a", "t" ], i: "echo_show_5", n: "Echo Show 8 (Gen3)" ],
          
          // Amazon Echo hub
          "ADMKNMEVNL158" : [ c: [ "a", "t" ], i: "unknown", n: "Echo Hub" ],

terminal3 · November 6, 2025, 11:13pm

I had found it in the code, but I was unsure of exactly how that was determined. So I guess I can just change the description on that line?

jtp10181 · November 7, 2025, 3:10am

I would go for it, if anything goes sideways just run a repair in HPM.

terminal3 · November 7, 2025, 3:35am

Yeah that's what I did and it seems to have worked. I linked to the Echo Dot 4th gen picture as there doesn't seem to be a listing for the 5th gen. It works though.

gikjll · November 7, 2025, 10:59am

This works for me, that function plays if the message is different...

jshimota · November 7, 2025, 4:23pm

this is a regression bug to me. I had forked and was managing devices, icons and music play stuff for myself as it felt like the app wasn't getting love. Then a recent resurgence - I upl'd my graphics and stuff to help filter this out - here is my sections from a year ago - which also includes a notation about someone else discovering a new device, and a unit incorrectly described in the Echo Spots as a gen 1 when it is a Gen 2

marktheknife · November 7, 2025, 6:14pm

Send a pull request to the dev in the echo speaks GitHub repo.

jshimota · November 7, 2025, 10:01pm

@tonesto7 PR sent. I included images and some updates to the device tables.

dabber · November 10, 2025, 9:47pm

Created a couple of zones to use for announcements. I noticed one devices has the custom HE voice I set in settings a long time ago, the rest of the devices have Alexa voice.

Anyone else seen (Heard) this?

gikjll · November 10, 2025, 10:00pm

What is a HE voice? I use different alexa voices, wife likes a male voice

672southmain · November 10, 2025, 10:42pm

Sounds like Bruce?

john022662k · November 11, 2025, 3:26am

Hi Team,

Echo Speaks seems to be working fine. I am using a local server that @jtp10181 helped me set-up several years ago. The app seems to retrieve the needed cookie but I'm getting errors in the logs and also have the Red X on the Auth Status but all other check marks are green.

Any thoughts on what may be wrong?

Thanks,

John

benmoore1991 · November 11, 2025, 8:02am

Hi has anyone had this issue with deploying a container for the echo speaks cookie. I cannot seem to get past it,

It all states that it authenticates in i get the successful cookie message and then it redirects me back to the same page where it says login again. I have been going through the logs and i find this under the NPM logs

34 http fetch GET 404 https://registry.npmjs.org/echo-speaks-server 95ms (cache skip)
35 timing command:view Completed in 98ms
36 verbose stack HttpErrorGeneral: 404 Not Found - GET https://registry.npmjs.org/echo-speaks-server - Not found
36 verbose stack at /usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/lib/check-response.js:95:15
36 verbose stack at processTicksAndRejections (node:internal/process/task_queues:96:5)
36 verbose stack at async RegistryFetcher.packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:92:19)
36 verbose stack at async View.getData (/usr/local/lib/node_modules/npm/lib/commands/view.js:203:20)
36 verbose stack at async View.exec (/usr/local/lib/node_modules/npm/lib/commands/view.js:111:28)
36 verbose stack at async module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:78:5)
37 verbose statusCode 404
38 verbose pkgid echo-speaks-server@latest
39 verbose cwd /usr/src/app
40 verbose Linux 6.12.15-production+truenas
41 verbose node v16.18.1
42 verbose npm v8.19.2
43 error code E404
44 error 404 Not Found - GET https://registry.npmjs.org/echo-speaks-server - Not found
45 error 404
46 error 404 'echo-speaks-server@latest' is not in this registry.

and under the container logs i get this

2025-11-11 07:59:20.885405+00:00Alexa-Cookie: Response (401)

2025-11-11 07:59:20.885855+00:00Get User data Response: ""

2025-11-11 07:59:20.886283+00:0011-11-2025 - 7:59:20am error: generateAlexaCookie: Unexpected end of JSON input

2025-11-11 07:59:20.886902+00:0011-11-2025 - 7:59:20am debug: Alexa Login Status: There was an error

2025-11-11 07:59:21.827698+00:0011-11-2025 - 7:59:21am info: ** ServerVersion Sent to Hubitat Endpoint Successfully! **

jtp10181 · November 11, 2025, 11:57am

@john022662k have you tried restarting the cookie server container?

@benmoore1991 have you tried this from my guide? (click the link to see the full post)
Nevermind, I see you double posted this in both places....