Amazon EchoControl LastVoiceCommand doesn't update anmore

please notice the discussion here:

We have 7 echoes here in the house and I just unlinked the “lastVoiceCommand” items from six of them. Perhaps this will allow us to stay below the rate limit. at leaste there’s no more 429 or 503 error after one of the 6 echoes received an command.
I’ll report back.

Can´t confirm that.
Even the first commands in the morning are ignored, after atleast 8 hours without any command.
Sometimes the last command in the evening works.

here the same…
The only command that was processed yesterday was one at 19:00…

We have 7 echoes here in the house and I just unlinked the “lastVoiceCommand” items from six of them. Perhaps this will allow us to stay below the rate limit. at leaste there’s no more 429 or 503 error after one of the 6 echoes received an command.
I’ll report back.

did that help?

not really. I still think it has something to do with rate limits, because I keep getting those 429 errors and 503 thrown in between. Perhaps we use our alexas to often - and especially with music.
but that brings me to another idea, perhaps I’ll also unlink the items for album covers and titles…

Hi there,

I have problems too:

Since a few days, my SmartHome/J-Binding auf Amazon EchoControl goes offline every 5 Minutes and comes back. The Error there is:

2025-07-08 15:27:09.832 [WARN ] [rol.internal.util.HttpRequestBuilder] - Parsing json failed: false
com.google.gson.JsonParseException: Empty result

Now I have changed back to the official binding. Here I have the error:

GET url 'https://alexa.amazon.de/api/phoenix' failed: null

on the account-Thing. The Account-Thing stays in OFFLINE-State - but the Device-Things are going ONLINE and they are working ?!!? - But no feedback of LastVoiceCommand or changes on Media or Volume Channels.

So at this time whether the official binding nor the smarthome/j binding are running stable.
I am not sure, which binding is the better solution for OH 4.3.X at this time and which binding would be supported and fixed.

Some suggestions what to do (I am not able to fix the error myself)…
@J-N-K: Are you still supporting these bindings ?

Ralph

I don’t think so. The problem is reported in the ha-forum too and there it was solved by a change of the interface. Unfortunately @J-N-K seems out of business as he was the only one taking care about the echo binding.

Still doesn’t rule out unwanted overreach on quotas. 429 errors explicitly cover rate limit violations. Don’t you get those in your logs?

Hey, could you share that link please?

was posted in the parallel thread as posted above: Amazon EchoControl LastVoiceCommand doesn't update anmore - #21 by Larsen

Is there a way to combine threads on this forum? I’ve got the feeling, we repeat ourselves in both threads - or could a moderator at least close one and link to the other?
I would close this one but even as the author I don’t see a button to close this thread…

Has this thread here the same root cause?

Our body’s from HA has solved their problem meanwhile…

Here is the Github link, were the HA guys have changed their stuff to get their Things running again.

1 Like