Had anybody the same issue?
I follow the instructions in "node-red-contrib-alexa-remote2-applestrudel" and at the amazon login I'll get an error message.
Thanks in advance.
Yes I get that also. No idea why - it used to work
Its been like that for nearly a month for me, and the Alexa nodes were not functioning. Suddenly this weekend they started working again without logging in on this page.
I'm running a flow that uses the proxy method, and a file path in context which reinitialises every 12 hours.
We’re having some issues here in Italy too; since yesterday evening, voice commands haven’t been working. Authentication is going through, though – the cookie is being saved, and Applestrudel shows ‘ready’. I’ve refreshed the cookie and restarted Node-RED, but it still isn’t working. I'm using Applestrudel 5.0.58, which already includes improvements for better use of cookies
I recently updated my Node-RED Alexa node to version 5.0.58 and then discovered my daily weather forecast flow wasn't being triggered because the Initialise node was failing. After some trial-and-error attempts at rectifying the issue, I found if I set 'Auto Init' to Off it worked.
Previously it was set to 'On' and had been like that for months and months.
I hope this discovery may help other people who are trying to get Alexa working again.
Hi all together,
I tried again with modiefied parameters like from dynamicdave described, but the same error as described at the beginning.
Nope, still Amazon will not let me initialise. Same as original issue. I've given up and disabled my flow
Has anyone manage to get the Alexa node working?
Mine won't let me initialise it - its been like it for sometime.
If I manage to get to the Amazon login page - it won't work. All very frustrating.
The feature I use a lot is... Routine >> Speak for Text To Speech (TTS) to an Alexa device.
Is there an alternative method to get Alexa to speak a text string?
Mine stopped a few days ago, I updated, i could only run the proxy login from the machine that runs node red, I also had to make sure the Android browser was in desktop mode. Using layla.amazon.co.uk and amazon.co.uk
Side note - Occasionally i have to go to config and switch method from proxy to cookie, then deploy and finally switch back to proxy method.
I have noticed the initialise node no longer outputs a cookie on successful login, via proxy. To work around save using the cookie file option (in config), and the file read node to access the cookie prior to the initialise node.
This node is still working for me.
nodered 4.1.10. every night I restart nodered and it works for a few days, then I have to redo the proxy procedure manually, I use amazon.it. there is some trick to avoid this annoying procedure
.I didn't upgrade to nodered 5 because some streams no longer work.
I'm also have this issue in the US. It seems to have coincided with me updating to Node-RED 5.0 and updating node.js. I took a look at the Apple Strudel GitHub page, as they seem to be actively hunting this down there. Looks like they've published an update to it (5.0.59), but be warned it won't install if you've upgraded to node.js 24.
Alternatively, there is a temporary patch listed in the comments there that should fix the cookie refresh bug if you don't want to downgrade node.js to v22. I'll report back in about 24 hours to let you know if the patch worked for me.
So it seems that my cookie has survived the 24 hour mark. I'll keep track and report back again later. But, for now, the patch seems to be working.
