Same here - Thailand
same problem from italy, for a few days now, no longer receiving voice commands. Thank you for reporting the anomaly I didn't understand if the problem was on my node-red.
Same problem with me, listener not reacting but speech fine. Glad i saw this as I have already spent a few hours faulting
We just need to hope someone comes up with a solution/fix.
Just found this after looking for a few days and trying reported fix's with no success.
following for new updates.
in the logs I found that it redirects the service to a new domain, does this seem normal to you ?Authentication checked: true 8 Sep 12:19:29 - [debug] [alexa-remote-account:opt] Alexa-Remote: Sending Request with {"host":"alexa.amazon.it","path":"/api/endpoints","method":"GET","timeout":10000,"headers":{}} 8 Sep 12:19:29 - [debug] [alexa-remote-account:opt] Alexa-Remote: Response: {"alexaApiUrl":"https://api.eu.amazonalexa.com","awsRegion":"eu-west-1","retailDomain":"amazon.it","retailUrl":"https://www.amazon.it","skillsStoreUrl":"https://skills-store-eu.amazon.it","websiteApiUrl":"https://eu-api-alexa.amazon.it","websiteUrl":"https://alexa.amazon.it"} 8 Sep 12:19:29 - [debug] [alexa-remote-account:opt] Alexa-Remote: Change Base URL for API calls to eu-api-alexa.amazon.it 8 Sep 12:19:29 - [debug] [alexa-remote-account:opt] Alexa-Remote: Initialize WS-MQTT Push Connection
I am trying with wireshark to capture alexa-remote traffic but cannot decode the TLS data
I think a fix is coming but not quite here yet.
Patience people ![]()
Seems to be fixed now with new version -
I can confirm this
Better still audio player state change is now working again, so my music player flow is back in action ![]()
I can confirm that v5.0.40 works for me.
Glad to report... 'onDeviceActivity' is working again.
HUGE thanks to whoever fixed the issue.
![]()
Note:
I found on my system, I needed node v16 or greater for this update to install.
(I'm actually using v18.16.0)
now works again ,
-
In the Alexa account node you have to activate Events because by default it is switched off.
-
There must have been some problem with the type of events as the selection box has disappeared in the new version.
Have you tried just entering 'alexa' (without the quotes) in the search box?
It should bring-up all the alexa nodes including v 5.0.40
![]()
I could see the node - it just wasn't the right version ![]()
All OK once I used npm install from command line

I'm noticing some unreliability - I seem to be having to re-initialise often to keep things working
Haven't managed to come up a repeatable sequence of events - all a bit random at the moment
I'm on v5.0.41
Update - redoing cookie seems to have sorted it




