Salve a tutti, non ho mai scritto su questo blog e quindi vi prego di perdonarmi se sbaglio qualcosa.
Da poco ho iniziato ad usare Node-red e non sono molto esperto. Da circa 2 mesi ho installato e usato node-red-contrib-ewelink-copy e ha funzionato sempre bene. da qualche giorno non riesco più ad usare nessuno dei nodi in quanto sia il pc che il Raspberry mi vanno in crash: si scollegano dal server e fermano il programma con error 403. Con il comando Node-red -safe ho disinstallato dalla palette e ho provato a rimetterlo di nuovo, ma il problema si ripete. L'app Ewelink funziona bene e i comandi rispondono.
Potete aiutarmi?
Grazie
Welcome to the forum Mario, you will be more likely to get help here if you post in English. I have translated your post for you.
Hi everyone, I have never written on this blog so please forgive me if I do something wrong. I have recently started using Node-red and I am not very experienced. I have installed and used node-red-contrib-ewelink-copy for about 2 months and it has always worked well. For a few days I have not been able to use any of the nodes because both the PC and the Raspberry crash: they disconnect from the server and stop the program with error 403. With the command Node-red -safe I uninstalled from the palette and tried to put it back again, but the problem occurs again. The Ewelink app works well and the commands respond. Can you help me? Thanks
Assuming that you installed node-red on the pi using the recommended method (Running on Raspberry Pi : Node-RED) then start node-red using node-red-start
and post what that command shows here. Copy/paste please, not screenshot.
Good morning Colin and thank you for the help you are giving me.
The installation was done following the recommended method and it worked perfectly for about 4 months.
I started now with the command you recommended and it gives me this error then the program closes: 19 Aug 15:15:06 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "{"error":403,"msg":"Sign:oauthClient enable invalid"}".
at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)*
at processPromiseRejections (node:internal/process/promises:470:17)*
at process.processTicksAndRejections (node:internal/process/task_queues:96:32)*
I also tried to change ewelink account but the result is identical.
Thank you.
Mario
I had intended to just post the error message.
There he is:
mario@raspberrypi:~ $ node-red-start
Start Node-RED
Once Node-RED has started, point a browser at http://192.168.1.4:1880
On Pi Node-RED works better with the Firefox or Chrome browser
Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot
Starting as a systemd service.
19 Aug 15:54:14 - [info]
Welcome to Node-RED
19 Aug 15:54:14 - [info] Node-RED version: v4.0.2
19 Aug 15:54:14 - [info] Node.js version: v20.16.0
19 Aug 15:54:14 - [info] Linux 6.6.31+rpt-rpi-v7 arm LE
19 Aug 15:54:16 - [info] Loading palette nodes
19 Aug 15:54:23 - [info] Dashboard version 3.6.5 started at /ui
19 Aug 15:54:24 - [info] Settings file : /home/mario/.node-red/settings.js
19 Aug 15:54:24 - [info] Context store : 'default' [module=memory]
19 Aug 15:54:24 - [info] User directory : /home/mario/.node-red
19 Aug 15:54:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
19 Aug 15:54:24 - [info] Flows file : /home/mario/.node-red/flows.json
19 Aug 15:54:24 - [info] Server now running at http://127.0.0.1:1880/
19 Aug 15:54:24 - [warn] Using unencrypted credentials
19 Aug 15:54:24 - [info] Starting flows
19 Aug 15:54:24 - [info] [remote-access:Remote RbPI3] Server: nodered02.remote-red.com InstanceHash: jssfso5ipnf2sc5vhip4vza66p4e6mtahn8d3s59r8zs0zhsayouamdcsugybs2e
19 Aug 15:54:25 - [info] Started flows
19 Aug 15:54:26 - [info] [remote-access:Remote RbPI3] Using nodered02.remote-red.com on port 50894
19 Aug 15:54:26 - [info] [remote-access:Remote RbPI3] starting ssh process
19 Aug 15:54:26 - [red] Uncaught Exception:
19 Aug 15:54:26 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "{"error":403,"msg":"Sign:oauthClient enable invalid"}".
at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
at processPromiseRejections (node:internal/process/promises:470:17)
at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Consumed 18.897s CPU time.
nodered.service: Scheduled restart job, restart counter is at 9.
Stopped nodered.service - Node-RED graphical event wiring tool.
nodered.service: Consumed 18.897s CPU time.
Started nodered.service - Node-RED graphical event wiring tool.
19 Aug 15:54:50 - [info]
Thanks for the reply.
Remote-access is used to manage the dashboard on the mobile phone display.
The nodes are updated to the latest version.
""error":403,"msg":"Sign:oauthClient enable invalid"}"
it only appears when I log in to the ewelink account. Then the system crashes and I have to uninstall the Ewelink nodes with Node-red -safe and restart.
This happens on both the Raspberry Pi4 and Windows. I think it's a Node-red error in managing Ewelink. Do you have any recent information on this?
Thanks for the advice. I also tried with another account but the result doesn't change. I will do more tests or I will give up on using this node.
Thank you for the time you dedicated to me.
Mario
