When you said automations don't work I did not realise that you meant contributed nodes.
I haven't used any of those nodes. I suspect any issues are more likely to be with nodejs versions rather than NR 5
For what it's worth, I've had no problems since installing the temporary patch almost a month ago. I did eventually downgrade node.js to v22 so I could update other nodes that required it and I did update to the latest Apple Strudel and none of that broke the patch for me.
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.
Node-RED version: v4.1.10; Node.js version: v20.20.2. ; node-red-contrib-alexa-remote2-applestrudel 5.1.1 Iâve been using Applestrudel for a week and everythingâs working properly again. Great!!
Thanks for the heads-up on v5.1.1
I've just updated to v5.1.1 on a RPi-4B running Node-RED version 4.1.10 with Node.js v18.20.8 and can confirm I can now send "text-to-voice" messages to my Alexa devices (again).
I have all the latest bits & bobs and I can't even get Amazon the accept the http://xx.xx.xx.xx:3456 login
I'm running Node-RED 5.0.1 with the "temporary" patch and it's working great. But seeing that others are still having issues is why I haven't updated to applestrudel 5.1.1 from 5.1.
It's probably worth mentioning that even though the issue was closed on GitHub it was revived as a new issue there. User fkhr79 (who came up with the temporary patch) has been working on figuring this out. Check out this post here on GitHub for more info on the on-going effort to tame this beast.
Tried both proxy & cookie. This has been going on for nearly a year now. Amazon will not authorise the login (also tried layla.amazon.amazon.co.uk as well as alexa.amazon.co.uk)
If I use cookie to initialise the init node says 'success' but all the other nodes are still waiting and give
TypeError: res.writeHeader is not a function
at accountHttpResponse (/home/pi/.node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js:287:7)
at /home/pi/.node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js:604:118
at Layer.handle [as handle_request] (/usr/lib/node_modules/node-red/node_modules/express/lib/router/layer.js:95:5)
at next (/usr/lib/node_modules/node-red/node_modules/express/lib/router/route.js:149:13)
at /usr/lib/node_modules/node-red/node_modules/@node-red/editor-api/lib/auth/index.js:69:28
at complete (/usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:280:13)
at /usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:287:15
at pass (/usr/lib/node_modules/node-red/node_modules/passport/lib/authenticator.js:446:14)
at Authenticator.transformAuthInfo (/usr/lib/node_modules/node-red/node_modules/passport/lib/authenticator.js:468:5)
at /usr/lib/node_modules/node-red/node_modules/passport/lib/middleware/authenticate.js:284:22
as an error message.
The Amazon log in sends me a Whatsapp code and then says the page is not available ????
Same here, no way to login
Firstly you must have applestrudel5.1.1, try clearing your cookies or re-authenticating via port 3456 (or whichever port youâve set) in your browserâs incognito mode. If youâre using a proxy, do the same and delete the saved file. If it still doesnât work, then do the following: go to /home/pi/. node-red/node_modules/node-red-contrib-alexa-remote2-applestrudel/nodes/alexa-remote-account.js and on line 287, replace res.writeHeader(...) with res.writeHead(...) It should work, but I donât know how to make the change permanent.
Tried all that. Got rid of the error message but when trying to log onto Amazon I got
Looking for Something?
We're sorry. The Web address you entered is not a functioning page on our site
This is how I trigger the Alexa node on my set-up...
The top
inject node is set to trigger every 180 minutes (3 hrs). When the Initialise node is triggered it can take 5 to 6 seconds before it shows the success state.I updated to v5.1.1, 5-days ago - fingers crossed all working fine since that date.
Can you tell me which versions youâre using of Node.red, Node.js and AppleStrudel, and which method youâre using â proxy or cookies ? It really does look as though youâre retrieving an expired cookie or an incorrect link to Amazon.
Node Red v5.0.1
Node.js v26.5.0
AppleStrudel v5.1.1
I have tried both proxy & cookie. The cookie used to work and using it with the flow that Dave shows (which again I have been using for a long time) the initialise node shows success but none of the other nodes work (all show uninitialized)
Using proxy gives the failures as already mentioned. All settings as shown in the AppleStrudel node setup instructions for UK. (I can also log on to Amazon shopping using email & password used for authentication - again, which used to work)
Tried using a separated browser, also incognito mode, neither made any difference.
Fixed the problem (for the moment anyway). I created a new Amazon account and it now works. 
I would advise against using v26, it is not yet the LTS version, some nodes may well have problems with it. Stick to 24 for the moment.
Acknowledged. I am experimenting using Temporal which requires 26. So far none of the nodes I use have a problem.
Re- the AppleStrudel issue, I also had to delete the config node and re-create so this may have been to problem all along.
I would advise against using v26, it is not yet the LTS version, some nodes may well have problems with it. Stick to 24 for the moment.
I had to downgrade from 24 to 22.23.1 because the 5.0.59 palette update was failing with EBADENGINE since the package engine declaration didn't include v24. Was that updated in applestrudel 5.1.1?
I have given up. I can log in using the new user name & password, but still not on the original. The issue?? all my devices are on Alexa with the old user name & password (that still works by the way)
