"failed to load routines: "no body""

[GaryStimson]

Hi Folks, As of this evening none of my routine nodes are working and I keep getting this error when I deploy ""failed to load routines: "no body"".

I also am finding that when deploy every 1 in 5 times the authentication fails and I see an error "Error while checking Authentication: Error: no JSON".

Any ideas?

Thanks, Gary

[obaldius]

+1 on that issue. My on device activity node stopped working today. Is there any way to notify cakebaked of this issue? Routines are back!! thanks for your advice and thanks cakebaked

[MonkeyBusiness1]

@AleksCee - The command line seems to be the best way to update, as even with removing all of the flows, node-red-contrib-alexa-remote2 still appears to be in use when updating from the GUI. You must go one step further if you are doing it that way, and remove the alexa alexa-remote-account as well.

Then the GUI will allow removing node-red-contrib-alexa-remote2 and adding the update.

That's quite a bit more cumbersome than using the command line method above.

It appears there are some additional underlying problems with the plugin.

Clearing up the "no body" is a excellent step in the right direciton.

But clearly there is some more work that needs to be done.

[AleksCee]

@MonkeyBusiness1 I have not try to remove it via GUI. The admin command says "it's in use" in the CLI. So have use the npm way....

[obaldius]

In fact I removed my account details because otherwise it wouldn't allow me to unistall it. Even after doing that, on device activity is not working. Routines are.

[MonkeyBusiness1]

@obaldius - The GUI way is indeed clumsy and command line seems to be the way to go.

But it seems that solving one problem allows the next one in line to present itself.

Most likely it will take a number of tweaks to the update to resolve all.

[obaldius]

@MonkeyBusiness1 On device activity stopped working with the previous version, not with cakebacked's. I'm just notifying that cakebacked's hasn't still solved that issue, which form me has started to happen today

[MonkeyBusiness1]

@obaldius - Got it, thanks for clarifying.

[GaryStimson]

Thanks cakebaked. Your release solved the original issue. However today I can't initialise at all. Keep getting "Authentication failed: "no JSON"". This started being intermittent last week but is now happening constantly. Any ideas?

[peterchs]

FYI updated alexa-remote release 3.7.1 today

https://github.com/Apollon77/alexa-remote/releases/

I'm still using the original fix of manually copying in the Apollon77 alexa-remote js files into the node_modules folder and it seemed to help with my issues, it had seemed to have stopped working with 3.6.0. On device activity is working for me.

[alunfair]

I'm running node-red as a service on a Debian server. Have been getting the "no body" and "no JSON" errors for a couple of days now. Copied the alexa-remote files from Git, roughly following the instructions from @877dev and the alexa routines I'm using are working again (at the moment). Survives the service being restarted and node-red deployments without an issue.

I've actually done this twice today, missed the drop of version 3.7.1 by minutes, thanks to @peteakalad for mentioning it.

[brinzlee]

Hi @cakebake is it possible to update your code with the latest code authentication....I'm still getting the occasional fail and thought maybe this might address it.. https://github.com/Apollon77/alexa-remote/releases/tag/v3.7.1 Thank you very much

[hannoverRed]

Hi @cakebake is it possible to update your code with the latest code authentication....I'm still getting the occasional fail and thought maybe this might address it.. https://github.com/Apollon77/alexa-remote/releases/tag/v3.7.1 Thank you very much

Hi @cakebake das würde mich auch sehr freuen

[diego76]

Hello, I am running node-red on HomeAssistant Hass.io. I have followed @cakebake's instructions ,replaced the original node with the new fork and also restarted the entire box a few times. Unfortunately during the Alexa init I often get the same 2 error messages: "no body" and "Error while checking Authentication: Error: no JSON". Eventually, after a few manual retries, I manage to successfully initialise Alexa. Any clues?

[cakebake]

Hi Sorry. Besides my job and my free time, I didn't look in here.

Eventually, after a few manual retries, I manage to successfully initialise Alexa.

It is the same for me. If it works, it works fine.

Hi @cakebake is it possible to update your code with the latest code authentication....I'm still getting the occasional fail and thought maybe this might address it.. https://github.com/Apollon77/alexa-remote/releases/tag/v3.7.1

Did you test it? It works in 80% of the cases for me. Of course, that's better than nothing at all. I can try the update tomorrow.

[Chris380]

Thanks a lot for your effort, @cakebake! (Du hast mir den Tag gerettet :-) ) Maybe not the most efficient way in most scenarios, but for me this UI-only-approach worked:

• Export all flows to file
• Delete all flows
• Uninstall "node-red-contrib-alexa-remote2" via UI
• Install "node-red-contrib-alexa-cakebaked" via UI
• Import flows from file
• Restart Node-RED

[cakebake]

Hehe, kein Problem, gerne!

I've created a new issue here so it doesn't get miles in this issue.

https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/1

[obaldius]

@cakebake I just came to say thanks for your effort. Using your fork everything is back to working. I really hope you can keep this flow up to date. Is there any way to buy you a coffee? Thanks again, really

[team-tech-works-uk]

@cakebake please let me add my own great appreciation for your efforts and guidance - thank goodness :-)

[johnwyles]

+1 👍🏻 Using the fork of this project over to @cakebake's and abandoning @586837r's by switching the npm packages worked for me. For HA OS, like @Chris380 mentions, if you change it in the UI you can do that, but I think the more correct way to do it would be to update the Configuration under Supervisor for Node Red and setting up the config there to have something like the following:

...
npm_packages:
  - >-
    node-red-admin node-red-dashboard node-red-contrib-home-assistant-websocket
    node-red-contrib-alexa-cakebaked node-red-contrib-amazon-echo
    node-red-contrib-alexa-home-skill
...

In order to not have to Re-Initialize NodeRed and Alexa again and again so it stays up to date and doesn't need to refresh the cookie so often I have found a nifty way to do so with HA OS. I am not sure where else to put it but I have also found it useful to use this Preserving variables in NodeRED (flow|global) flow from here: Preserving variables in NodeRED along with incorporating this Initialize Flow flow from here: The answer to almost all Echo needs: Alexa-remote2.

Then to re-authenticate after a reboot or restarting Node Red I do a:

ssh -L 3456:127.0.0.1:3456 -p 22222 root@pi-home-assistant.local

and load up http://127.0.0.1:3456/ on my local machine. Sometimes it works and sometimes it doesn't. Doing a re-deploy in Node Red is sometimes required if it gets confused about an csrf error or the Success screen doesn't show up. Nevertheless it will eventually authenticate and I am good until the next restart.

• @cakebake are you going to semi-officially take up the project? 😄

[1liminal1]

Hi guys,

I have node red installed as the add on for home assistant os

I have disabled most of the nodes but cant remove the last one. I have also removed all my sequences as well

What am I doing wrong here?

Thanks :)

[1liminal1]

I got it,

Go to the hamburger menu> Configuration nodes> double click the config node/s for Alexa remote and delete in the top left

:)

[sarsw]

So does cakebake work for everyone? I installed it and I still get the errors noted above (no json) and all my echo devices become sluggish to respond to any question and occasionally fail and the circular led goes red with the appropriate "I'm sorry...." utterance. Thankfully Google home/Nora flows are still ok. I'd still like the echo devices to work again though as I have lots more devices set up for those.

[deosrc]

So does cakebake work for everyone? I installed it and I still get the errors noted above (no json) and all my echo devices become sluggish to respond to any question and occasionally fail and the circular led goes red with the appropriate "I'm sorry...." utterance. Thankfully Google home/Nora flows are still ok. I'd still like the echo devices to work again though as I have lots more devices set up for those.

Unless I've missed some configuration (very possible), this package is only sending and receiving one-time commands with Alexa (e.g. play announcement or receive event, not both unless you have implemented it that way in a flow). All of the "conversation" logic (e.g. receive and reply) is still processed by Amazon and this doesn't have any control over it. That would suggest the "I'm sorry..." response you are getting is a connectivity/configuration issue with Amazon/Alexa rather than a problem with this.

As I said though, it's very possible I've missed something. If you're not getting a specific error message in Node-RED, I'd suggest posting your flow.

[kzelnick]

thanks cakebake fairly new i too and the original error but removed alexa remote , then added your update the original error is gone but now have the failed to load routines: "routines.map is not a function"" any help would be appreciated

[sarsw]

So does cakebake work for everyone? I installed it and I still get the errors noted above (no json) and all my echo devices become sluggish to respond to any question and occasionally fail and the circular led goes red with the appropriate "I'm sorry...." utterance. Thankfully Google home/Nora flows are still ok. I'd still like the echo devices to work again though as I have lots more devices set up for those.

Unless I've missed some configuration (very possible), this package is only sending and receiving one-time commands with Alexa (e.g. play announcement or receive event, not both unless you have implemented it that way in a flow). All of the "conversation" logic (e.g. receive and reply) is still processed by Amazon and this doesn't have any control over it. That would suggest the "I'm sorry..." response you are getting is a connectivity/configuration issue with Amazon/Alexa rather than a problem with this.

As I said though, it's very possible I've missed something. If you're not getting a specific error message in Node-RED, I'd suggest posting your flow.

Hi, my problem was it wasn't connected fully. When I added my first virtual device there was no connection info/instructions displayed in the lower part of the node's info cfg panel so I didn't progress past that. I've just updated node red too and reinstalled cakebake and it seems to be working for the 5 minutes since I set it up now. 👍

[quadhammer]

i too and the original error but removed alexa remote , then added your update the original error is gone but now have the failed to load routines: "routines.map is not a function"" any help would be appreciated

Apparently this happens when you have no routines in the Alexa app.

[kzelnick]

Above there was a solution, seems odd but it works log on to the alexa app on your phone or tablet go to the routine section add a routine like a bogus alarm and fixes it for some reason there needs to be at least one actual routine on alexa for the warning to go away

[commandcontrolit]

Your fork fixed my issue! Thank you!

https://github.com/586837r/node-red-contrib-alexa-remote2/issues/191#issuecomment-774193329

[johnwyles]

@commandcontrolit - isn't @cakebake the greatest? 😍