since few days my Alexa event node temporarily stopped working stating the following error message:
"Authentication failed: "no body""
Usually it helped to either restart all flows or, as a last resort, restart the whole Node-Red integration (I´m using Home Assistant). But since today even this has no effect anymore. I´m using the
node-red-contrib-alexa-cakebaked
palette but also tried different other ones but it´s the same situation. Anyone know who killed Alexa and how to revive her?
I've got exactly the same issue/problem - exactly the same error message with my daily weather forecast.
Everything has been working fine for the last 3 or 4 weeks.
I've tried various things to try to resolve it - all have failed.
I've even installed the nodes on a Raspberry Pi that didn't have any of these nodes - still dosen't work
Tried it with both of the old pallets "node-red-contrib-alexa-remote2" and "node-red-contrib-alexa-remote2-v2". Unfortunately absolutely no change in the situation
Well this is really weird !!!
My daily weather forecast delivered via Alexa worked this morning.
The Node-RED flow hasn't been working all week, then burst into 'life' this morning.
I've just looked at the flow and it had a green success light against the Alexa node, yippppeee...
Unfortunateley, after I deployed the flow I'm getting the 'Authentication failed' message!!
Oh well that success was short-lived.
I've just removed my old version of 'alexa' and tried 'node-red-contrib-alexa-remote-fork' - that gives the same problem and error message.
I've tried all sorts of combinations of 'Fresh Authentication', 'Refresh Cookie' before doing 'Initialise'.
I did notice the (optional) User Agent box is blank. What have other people put in there?
Thanks much @Varguit - Looks like they already fixed it themselves. After re-installing the cakebaked version, the missing entry to alexa-remote.js was already made and the node initialized smoothly again