node-red-contrib-alexa-remote2
node-red-contrib-alexa-remote2 copied to clipboard
586837r
Authentication Failed "no body"
I'm able to authenticate once but if I make a change to any node and press Deploy I get Authentication Failed "no body". The only way to resolve the problem is to either delete the file that I put in the File Path or point to a different file. But even after I do that, and I make a change somewhere that requires I re-deploy, then the error comes back.
Any help would be appreciated.
Mike
I've experienced the same problem.
It works for several days and then "Authentication failed: "No body".
Initially I would fix it by deleting and re-creating the proxy file. However, I recently discovered that all I need to do is edit the Account node, just click Update, then Deploy the flow. That causes the flow to work (just re-deploying the flow alone doesn't fix it).
This stability/reliability issue is a showstopper; I can't use this in my home. The "Detect Activity" node works for several days and then just stops for no apparent reason.
EDIT It appears that the technique I described above only worked once. I had to revert to the original technique of deleting the proxy file and creating a new one.
Does anyone else have any suggestion. The configuration is very basic but it does not seem to work as expected. Am I missing something or is this a known issue?
This node's ability to maintain a connection to Amazon's Alexa cloud service is unreliable.
My flow now uses a status node to monitor the connection status of the alexa-remote-event node. It alerts me whenever the node's status changes to "Authentication failed: "No body". This way I know when the connection has failed and then I can proceed to create a new proxy file.
I'm notified every few days, sometimes twice in the same day. The longest it has ever maintained a connection is about 6 days. For my purposes, it's bordering on being unusable. I could live with this behavior if it occurred every few months but not once or twice a week.
I'm willing to provide whatever information is needed to track down this bug.
Has anyone got any joy solving this? This palette is clearly the best and easiest to use when it works reliably. I am using it to play the radio as an alarm clock, but after a few days it stops.
I experience the same issue when I reboot the server (Raspberry), is there any possibile solution? I like the node but this is very annoying!
Same issue here with Italy and French accounts. Have something changed in Amazon cookie?
