Problems with node-red-contrib-alexa-remote2-applestrudel and Amazon

[Buckskin]

I have recently received the message open XXXX:3456 in your browser. However, when I do and enter my email & password I then get a pass code sent to my phone. The resulting entry box is very flaky and when I finally do get to enter the code I get an amazon.com 404 error (I have my node set to amazon.co.uk)

Has anyone else had this problem, and if so have you resolved it and how?

[DiverRich]

Not sure but this may be part of the problem. https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/234

[ghayne]

Same here, here we go again!

[E1cid]

Yes that is the issue .
I fixed mine by upgrading applestrudle to latest, then edited the alexa-remote-ext.js as described in the link you provided. Then restarted node-red and re authorised via proxy url http://localhost:3456
There should be an update to the node coming soon if you do not fancy editing your node_module files.

[dynamicdave]

I've just updated the Alexa node using the Palette Manager to 5.0.54 and restarted Node-RED.
Seems to initialise without any problems. (No edits needed or performed.)
It will be interesting to "hear" if Alexa delivers my weather forecast tomorrow morning.

[Buckskin]

Nope. Still doesn't work. I still get to the Amazon login enter email & password, then get flaky entry for SMS code straight to Amazon dot com 404

PS Checked the customer ID bit

	async getCustomerId() {
		const response = await new Promise((resolve, reject) => {
			const callback = (err, val) => err ? reject(err) : resolve(val);
			this.getUsersMe(callback);
		});
		ensureMatch(response, { id: '' });
		return response.id;
	}

[DiverRich]

It might be worth trying a private browser when requesting your cookie as mentioned in this post.

[Buckskin]

Tried that. Exactly the same flaky entry for an SMS code straight to 404

[franz]

I also have Alexa... Applestrudel stuck at authentication (I have version 5.0.55 and nodered4.1.1.) and I can't even uninstall it. it will be because of this problem : `npm audit

npm audit report

cookie <0.7.0
cookie accepts cookie name, path, and domain with out of bounds characters - cookie accepts cookie name, path, and domain with out of bounds characters · CVE-2024-47764 · GitHub Advisory Database · GitHub
No fix available
node_modules/alexa-cookie2/node_modules/cookie
alexa-cookie2 >=2.0.0
Depends on vulnerable versions of cookie
node_modules/alexa-cookie2
alexa-remote2 >=2.0.0
Depends on vulnerable versions of alexa-cookie2
node_modules/alexa-remote2
node-red-contrib-alexa-remote2-applestrudel *
Depends on vulnerable versions of alexa-remote2
node_modules/node-red-contrib-alexa-remote2-applestrudel

4 low severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.`

[DiverRich]

If you haven't resolved this yet, have you tried another browser or tried getting the cookie on another device?

[Buckskin]

Yes. I even tried moving the nodes to a different device. Entering the cookie request in the browser keeps sending me to amazon.com, not amazon.co.uk (not sure if that is correct) and I still end up with a 404 error (dogs on the page)

[franz]

I have Nodered in a container. I made a backup and reinstalled everything. Now it works fine.

[ghayne]

The same procedure worked for me too @dynamicdave,

[franz]

I waited 24 hours, but with the latest version of Applestrudel, I can only do one voice query at a time. I had to tie a knot to reset Alexa every minute, but that's not a good solution. It almost seems like there's a problem with proxy mode. Does anyone know how to use cookie mode?

[Sgooch]

I can see version 5.0.55 in palette manager, but it tells me I have a conflict with "node-red-contrib-alexa-remote2 (not the applestrudel version). I thought I had disabled everything that uses that, but it seems to think that "something" is using it but I sure can not see it visually! Any thoughts on next steps? I REALLY want to get the Alexa stuff working again.

[Colin]

Uninstall that node. If it won't let you then check in Configuration Nodes for any unused configuration nodes related to that and delete them and deploy and try again. If it still won't let you uninstall it then open a command window and go into your .node-red folder (assuming this is a conventional install) and run
npm remove node-red-contrib-alexa-remote2
Then restart node-red.

[Sgooch]

I had to remove each please it was used even though they were “disabled”. New version seems to be working great!

Can someone explain to me (in old man terms) exactly what was failing in the Alexa authentication and what was done to fix it in the new version?

-Steve