Workaround for "no json", "no body" etc.

bwims commented 3 years ago

What I find works for me is the following workaround:

In every flow with Alexa Remote routines, I use a catch node specifying all of them, sending them to debug in the first place.
I then use a switch node to check for the errors, e.g.no Json, Authentication failed: "no body", etc and execute an "initialise"
if it's an error I haven't checked for, it goes to the debug line. If re-initalising cures it, it goes in the check list.

bwims commented 3 years ago

On Fri, 2 Apr 2021 at 15:53, Giamma1963 @.***> wrote:

Some screenshot would be much appreciated .....

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/18#issuecomment-812564861, or unsubscribe https://github.com/notifications/unsubscribe-auth/AENIQ2ORRTEX45MEQCQBROLTGXLANANCNFSM42I4UP7Q .

ghost commented 3 years ago

Thank you very much ....

maddingamer commented 3 years ago

@bwims could you provide your exported flow? :)

bwims commented 3 years ago

It's very difficult, which is why I used screenshots. The alexa routines won't point to any meaningful devices, so will immediately be unconfigured.

Still, here you go

First flow is where the account is initialised periodically after authentication the link comes in from any tab which has an alexa node that may throw an error.

[{"id":"b9eb3ad5.40c0b8","type":"alexa-remote-init","z":"87fa7c5d.a1e39","name":"","account":"77f08fbc.87385","option":"initialise","x":550,"y":300,"wires":[["5b221ebc.7f747"]]},{"id":"343315b2.cc471a","type":"inject","z":"87fa7c5d.a1e39","name":"","topic":"","payload":"","payloadType":"date","repeat":"10800","crontab":"","once":true,"onceDelay":"5","x":340,"y":300,"wires":[["b9eb3ad5.40c0b8"]]},{"id":"9fd88224.61fec","type":"catch","z":"87fa7c5d.a1e39","name":"","scope":["b9eb3ad5.40c0b8"],"uncaught":false,"x":760,"y":300,"wires":[["d80b17e5.463358"]]},{"id":"776955b9.8dc69c","type":"debug","z":"87fa7c5d.a1e39","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":1080,"y":500,"wires":[]},{"id":"71a60332.bd9bcc","type":"delay","z":"87fa7c5d.a1e39","name":"","pauseType":"rate","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"5","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"x":810,"y":200,"wires":[["b9eb3ad5.40c0b8"]]},{"id":"5b221ebc.7f747","type":"change","z":"87fa7c5d.a1e39","name":"","rules":[{"t":"set","p":"loginCookie","pt":"flow","to":"payload.loginCookie","tot":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":860,"y":400,"wires":[[]]},{"id":"d80b17e5.463358","type":"switch","z":"87fa7c5d.a1e39","name":"","property":"error.message","propertyType":"msg","rules":[{"t":"eq","v":"Authentication failed: \"no JSON\"","vt":"str"},{"t":"eq","v":"Error while checking Authentication: Error: no JSON","vt":"str"},{"t":"else"}],"checkall":"true","repair":false,"outputs":3,"x":960,"y":320,"wires":[["71a60332.bd9bcc"],["71a60332.bd9bcc"],["71a60332.bd9bcc","776955b9.8dc69c"]]},{"id":"3681816c.1b119e","type":"link in","z":"87fa7c5d.a1e39","name":"Init Alexa In","links":["e0401e43.1fce7","828f912b.28846","9daaf98d.1228c8"],"x":265,"y":360,"wires":[["b9eb3ad5.40c0b8"]]}]

Here is an example of a tab catching an alexa error and linking back. Of course, I'm only using it for remote button presses, so can just retry. Other needs may include sending some kind of message of failure.

[{"id":"5a40b572.06952c","type":"catch","z":"5beb7bc7.3bcfb4","name":"alexa bug","scope":["87f2843a.ae13f8","74405399.be3b6c","c60f46aa.c20ad8","2853b155.0f3ebe","50f53085.2ca5f","e3b44ec5.cc5aa","efaade47.56557","14bbed52.8d8b63","475f358.31958cc","184f5464.828c8c"],"uncaught":false,"x":340,"y":660,"wires":[["edb18d3d.abc9d"]]},{"id":"293dbc4e.8747d4","type":"debug","z":"5beb7bc7.3bcfb4","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":870,"y":700,"wires":[]},{"id":"edb18d3d.abc9d","type":"switch","z":"5beb7bc7.3bcfb4","name":"","property":"error","propertyType":"msg","rules":[{"t":"eq","v":"no body","vt":"str"},{"t":"else"}],"checkall":"true","repair":false,"outputs":2,"x":530,"y":660,"wires":[["81eb5e8b.4c2fa"],["b2ad0cf.d5400f"]]},{"id":"81eb5e8b.4c2fa","type":"link out","z":"5beb7bc7.3bcfb4","name":"Init Alexa out","links":["722a72b1.e268ac","d53cd4b0.0a6b68","ff4d4dd1.31634"],"x":665,"y":620,"wires":[]},{"id":"b2ad0cf.d5400f","type":"switch","z":"5beb7bc7.3bcfb4","name":"","property":"error.message","propertyType":"msg","rules":[{"t":"eq","v":"no JSON","vt":"str"},{"t":"else"}],"checkall":"true","repair":false,"outputs":2,"x":610,"y":740,"wires":[["81eb5e8b.4c2fa"],["81eb5e8b.4c2fa","293dbc4e.8747d4"]]}]

cvlaray commented 3 years ago

It seems that the "no json" error is triggered when I try to run several commands in a short time. At least in my case, the problem was solved by introducing a delay of 3 seconds before executing another command in the same device. I am not sure if it also occurs when different devices are used simultaneously.

Toxo666 commented 3 years ago

Hi.

Here mine auth checking flow with catch & status node. Status Node monitors "Check Authentication" node. It shows a led on dashboard green/red, logs errors and input cookie file at intialise. Maybe it will help someone...

You need node-red-contrib-moment and node-red-contrib-ui-led.

msedge_JuO2zxZ4iY

Greetings Toxo

gaussey commented 3 years ago

Solution : https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-853162235

cakebake / node-red-contrib-alexa-remote-cakebaked

Workaround for "no json", "no body" etc. #18