Alexa Cookie is not saved

Hi everyone,

I am using alexa-remote2-applestrudel and am setting up on a clean install of nodered. Another PI is also running fine with the same configuration.

On this new install I entered the same details including the filepath where the cookie shall be stored.
/home/pi/Alexapass.txt

Afterwards I went to x.x.x.x:3456 and entered my credentials. I receive the white success page and the node shows "ready" in status. But when I check the file on the linux filesystem it is empty. I already changed the rights to 777.
That means, after I redeploy, the alexa node asks to be re-authenticated again.

Debug panel also shows, that nodered cant access the file. What location would be suitable for the file? What user needs to own the file?

What do I miss? Is there any setting that needs to be done aswell?

That alexa node is very problematic

This is what I have configured and it works for me (or has done for about 2 years anyway)

If your using Home Assistant in a Docker coinmtainer - all bets are off :slight_smile:

I am using nodered as an adapter of the iobroker, so it is installed below iobroker somehow.
The folder where you have your pass doesnt exist for me.

As the field is optional, I guess leaving it blank should work and the file gets stored, where nodered has write permissions. But that doesnt work either.

Btw: Do you have a suggestion for a better node? Havent found anything else than applestrudel that works.

I remember to stumble upon this question everytime I install, so here is a note for my future self:

the directory "pi" needs to be writeable aswell. Not only the Alexapass.txt

Thx!

I agree with Simon @cymplecy the node is very problematic, although it has worked for me (apart from Device Activity not working) for the last year or so.
I bet it will "play-up" now I've said that.
Here are my settings and where I keep the cookie text.


friday_alexa_permission

Here's a posting on what I use to detect device activity...