Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account not initialised! #115

Open
cyqx13 opened this issue Mar 30, 2020 · 3 comments
Open

Account not initialised! #115

cyqx13 opened this issue Mar 30, 2020 · 3 comments

Comments

@cyqx13
Copy link

cyqx13 commented Mar 30, 2020

Dear all,
I really like this alexa-remote2 skill.

I have the issue that this skill is not working after some days. Log of Redmatic shows: Account is not initialised. By reboot of Redmatic everything is working again for some days. I guess that it might be an issue with Cookie refresh, but I'm not completely sure. The node doesn't show any failures (like some people have with no CSRF), everything is

Does anyone have the same problem? I'm using Redmatic 4.7.1 on a RaspberryMatic version July 2018.

Many thanks for your support!

@dissemin8
Copy link

I had the same problem. After a random number of days, it would stop working and the refresh node would start complaining about not being initialised. After it happen for about the 4th or 5th time I removed it. It was compounded by also causing node-red to restart every few days as mentioned in another comment. My setup:

node-red version : 0.20.8
os-release : PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
uname -a : Linux hs14 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux

@jensrossbach
Copy link

jensrossbach commented Apr 5, 2020

I have the following issue since yesterday: Nodes ask to visit login page and after logging in I get error "no csrf found". After re-deploying, again I'm asked to visit login page. I can't get out of this "error loop".

Update:
I could workaround the problem by deleting the cookie / auth file and then restarting Node-RED as mentioned in #102. After logging in again, the error didn't appear anymore and the nodes are ready. Hopefully remains for longer time now.

Update 2:
Unfortunately the problem reappeared 5 days later (I'm not sure if it is related to the refresh time which I set to 5 days). :(

@SvenBayer
Copy link

SvenBayer commented Jun 5, 2020

PS: I am writing here about the node-red-contrib-alexa-remote2 module of course.

I have a similar issue with Node-Red running with IoBroker.
In the last weeks, since end of May 2020, NodeRed would crash and restart constantly due to the alexa-remote2 module. This makes it impossibe for me to access NodeRed at all!

To get NodeRed running, I have to rename the alexa-remote2 folder in
/opt/iobroker/iobroker-data/node-red/node_modules

Changing the auth file, does not help, since I use Proxy authentication. Then, I search for Alexa Remote in NodeRed and delete the configuration node for alexa-remote2.
Afterwards, I can rename the _alexa-remote2 folder to alexa_remote2 and restart NodeRed. I am able to create a new configuration and alexa-remote2 works fine. Then, after one or two days, alexa-remote2 breaks my NodeRed again, forcing it to restart continuously.

The error message I see in the logs is not helpful:
promise rejection. this error originated either by throwing inside of an async function without a catch block, or by reject

EDIT1
I try to re-initialise the alexa-remote2 configuration after each deployment. Maybe this helps to avoid this issue.
[ { "id": "f29786d7.62e138", "type": "tab", "label": "InitAlexa", "disabled": false, "info": "" }, { "id": "df30ec09.55605", "type": "alexa-remote-init", "z": "f29786d7.62e138", "name": "", "account": "2cee64ed.67e2bc", "option": "fresh", "x": 420, "y": 80, "wires": [ [ "bb89f3a8.b3a1d" ] ] }, { "id": "6ba99006.19071", "type": "inject", "z": "f29786d7.62e138", "name": "", "topic": "", "payload": "alexa", "payloadType": "flow", "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "x": 160, "y": 80, "wires": [ [ "df30ec09.55605" ] ] }, { "id": "bb89f3a8.b3a1d", "type": "file", "z": "f29786d7.62e138", "name": "", "filename": "/opt/iobroker/iobroker-data/node-red/context/TODO_file_name", "appendNewline": false, "createDir": true, "overwriteFile": "true", "encoding": "utf8", "x": 810, "y": 80, "wires": [ [] ] }, { "id": "9d70e93.458fe18", "type": "file in", "z": "f29786d7.62e138", "name": "", "filename": "/opt/iobroker/iobroker-data/node-red/context/TODO_file_name", "format": "utf8", "chunk": false, "sendError": false, "encoding": "utf8", "x": 530, "y": 160, "wires": [ [ "26324b62.f3b344" ] ] }, { "id": "1b007619.a28c3a", "type": "inject", "z": "f29786d7.62e138", "name": "", "topic": "", "payload": "alexa", "payloadType": "flow", "repeat": "", "crontab": "", "once": true, "onceDelay": 0.1, "x": 180, "y": 160, "wires": [ [ "9d70e93.458fe18" ] ] }, { "id": "26324b62.f3b344", "type": "alexa-remote-init", "z": "f29786d7.62e138", "name": "", "account": "2cee64ed.67e2bc", "option": "initialise", "x": 880, "y": 160, "wires": [ [] ] }, { "id": "2cee64ed.67e2bc", "type": "alexa-remote-account", "z": "", "name": "", "authMethod": "proxy", "proxyOwnIp": "TODO, add ip", "proxyPort": "TODO, select port", "cookieFile": "/opt/iobroker/iobroker-data/node-red/context/TODO_file_name", "refreshInterval": "", "alexaServiceHost": "TODO, see info", "amazonPage": "TODO, see info", "acceptLanguage": "TODO, see info", "userAgent": "", "useWsMqtt": "off", "autoInit": "off" } ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants