[amazonechocontrol v5.x.x] - lastVoiceCommand vs. TTS (both never working together)

Setup, Configuration and Use Beginners
1

I have upgraded from OH 4.3.8 stepped all the way through the OH 5.x versions and I’m currently on the latest 5.1.0.m3.

What I’m experiencing is either lastVoiceCommand or TTS isn’t working based on when I log into the AmazonEchoControl binding.

  • If I do a clean OH start, then TTS works fine and lastVoiceCommand does NOT.

  • If I logout/login via AmazonEchoControl binding, then lastVoiceCommand does and TTS does NOT.

I have Logout and Re-register via the AmazonEchoControl binding.

I have cleared the cache/tmp areas.

I have blown away the bridge and ALL 17 Echo’s device and re-added them.

The same thing keeps happening on every version of OH 5.x.x so far.

Best, Jay

2

Did you already try to reset your account?

3

Just did, same results. It logs you out and once I log in again, I get lastvoicecommand but TTS doesn’t work.

Best, Jay

4

Are you using the Thing Channel sendMessage?
That one does not work for me, too (openHAB 5.1.0.M3).
But all individual textToSpeech Channels are working fine.

Are you still using the workaround with refreshAcitivity? It is not needed anymore.

Apart from that I have no ideas. Since the fix from lsiepel the binding is working for me, then another api change from Amazon broke it again, then the fix from digitaldan and lsiepel worked again.

5

Nope.

Only reason I can come up with is, maybe so many Echo’s ranging from v2 - v5?

I do have 1 offline that I can’t get to until Friday, different location. Can’t image that would be the issue.

I’m still getting these in the log, which means their is a rouge URL still needing to be migrated to v3 of the API.

2025-12-08 08:26:52.128 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:27:08.694 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:30:10.290 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:30:26.936 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:32:34.032 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:32:52.426 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:42:34.254 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request
2025-12-08 08:42:51.282 [WARN ] [g.amazonechocontrol.internal.connection.Connection] - Failed to get notifications: https://na-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request

Best, Jay

6

I don’t think that is the reason, because I am seeing similar messages a couple of times a day, too (but today only once):

2025-12-08 10:31:33.334 [WARN ] [zonechocontrol.internal.connection.Connection] - Failed to get notifications: https://eu-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request

Maybe: I only use two of my eight echos for tts.

1 Like
7

I posted this before somewhere (GitHub or OH Community), these API calls need to be replaced with the new ones.

All I did was Grok the error and it says:

The error “Failed to get notifications: https://eu-api-alexa.amazon.com/api/notifications failed with code 400: Bad Request” indicates that the request to Amazon’s legacy Alexa notifications endpoint is being rejected. This endpoint (eu-api-alexa.amazon.com) appears to be part of an unofficial or older API structure, commonly used in integrations like Home Assistant’s Alexa Media Player (AMP) component. As of late 2024 and into 2025.

Migrate to Official APIs: For production, switch to Alexa Smart Home Skill API v3 (endpoint: https://api.eu.amazonalexa.com/v3/…). Migration guide available in Amazon docs (Nov 2025 update).

I wish someone could address this URL swap out in the binding.

Best, Jay

2 Likes
8

Github is your friend, but you already did :+1: