Node Red crashes - Githubissues

morpheus1984 commented 1 year ago

Hi, i am a Basic user with not that much know how. Since the change to OAuth2 i have problems with node red, it crashes several times a day. After restart everything works Fine again until the next exit.

are there some tips and tricks to avoid that?

Would be great if someone can help me.

greets Jan

Here the log:

Feb 19 09:52:00 homematic-raspi daemon.err node-red: 19 Feb 09:52:00 - [red] Uncaught Exception: Feb 19 09:52:00 homematic-raspi daemon.err node-red: 19 Feb 09:52:00 - ReferenceError: callback is not defined Feb 19 09:52:00 homematic-raspi daemon.err node-red: at ClientRequest. (/usr/local/addons/redmatic/var/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9) Feb 19 09:52:00 homematic-raspi daemon.err node-red: at ClientRequest.emit (events.js:315:20) Feb 19 09:52:00 homematic-raspi daemon.err node-red: at TLSSocket.socketErrorListener (_http_client.js:469:9) Feb 19 09:52:00 homematic-raspi daemon.err node-red: at TLSSocket.emit (events.js:315:20) Feb 19 09:52:00 homematic-raspi daemon.err node-red: at emitErrorNT (internal/streams/destroy.js:106:8) Feb 19 09:52:00 homematic-raspi daemon.err node-red: at emitErrorCloseNT (internal/streams/destroy.js:74:3) Feb 19 09:52:00 homematic-raspi daemon.err node-red: at processTicksAndRejections (internal/process/task_queues.js:80:21) Feb 19 09:52:00 homematic-raspi daemon.err node-red: Node-RED exited with non-zero exit status 1

tom666-debug commented 1 year ago

I am facing the same issue with Node-RED is crashing/restarting caused by the netatmo-dashboard node. This is what I have found in the Node-RED logfile:

24 Feb 12:32:27 - [red] Uncaught Exception: 24 Feb 12:32:27 - [error] TypeError: Cannot read properties of undefined (reading 'devices') at NetatmoDashboard._inputCallback (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:96:19) at runMicrotasks () at processTicksAndRejections (node:internal/process/task_queues:96:5)

morpheus1984 commented 1 year ago

And what does that error mean? You have some idea?

AleksCee commented 1 year ago

@tom666-debug Line 96 is _(data.body.devices).each(function (station) { So I think in your response is no data, perhaps Netatmo api was down or has no read permission to get the requested data in devices. Has your app the permission scope to read all?

@morpheus1984 In your case it’s at .setTimeout(0) .on('error', (error) => { callback(error); });

While fetching the access token. The code ends in the catch block an the callback Funktion is not exist. I think this is an bug. In the other error case the code will only wire a node.log() and not call callback Funktion.

tom666-debug commented 1 year ago

perhaps Netatmo api was down

This is really an issue :-(

Today my Node-RED Instance crashed 6 times in a row because of this. Srsly, is there a chance to make this node a bit more robust?

Mike4466 commented 10 months ago

Hello, I use this node because node-red-contrib-netatmo had not implemented the new authorization and I urgently needed another node. So I switched to this node only a few months ago.

My Node Red also crashes from time to time. It runs under RaspberryMatic. Often during internet interruptions but probably otherwise as well. My problem is that I have to start Node Red manually afterwards, because it crashes so many times in a row.

I have now set that Node Red does not give up after 3 times reboot but endlessly tries to start Node Red after crashes. Whether this is smart, I do not know, but if the home automation does not work all day, only because the Netatmo Node crashd when authorizing, is worse for me.

If anyone can give me a suggestion on where I can change something to work around the problem, I would be grateful.

Greetings, Mike

Here the relevant part of the log: Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: 25 Aug 08:14:22 - [red] Uncaught Exception: Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: 25 Aug 08:14:22 - ReferenceError: callback is not defined Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at ClientRequest. (/usr/local/addons/redmatic/var/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at ClientRequest.emit (events.js:315:20) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at TLSSocket.socketErrorListener (_http_client.js:469:9) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at TLSSocket.emit (events.js:315:20) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at emitErrorNT (internal/streams/destroy.js:106:8) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at emitErrorCloseNT (internal/streams/destroy.js:74:3) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: at processTicksAndRejections (internal/process/task_queues.js:80:21) Aug 25 08:14:22 homematic-ccu2 daemon.err node-red: Node-RED exited with non-zero exit status 1 Aug 25 08:14:22 homematic-ccu2 daemon.err redmatic: Maximum Node-RED restarts exceeded

morpheus1984 commented 10 months ago

Hi Mike, i also found out that this Happens when my Internet Connection gets lost. I did the same, ebdless restarts After crash. But i think its not normal that complete Node red crashes if one node cant work fine. All my other nodes dont really care if Connection fails for some minutes.

tom666-debug commented 10 months ago

Of course, it's not the nodes fault that there are outages from time to time on Netatmo-side (or if the connection to the internet is down). But it cannot be that for such a reason complete NoreRED is crashing. This node needs better exception handling urgently.

S474N commented 10 months ago

Also have every day crash of NodeRED:

2023-07-24T14:42:05.034968916Z 24 Jul 16:42:05 - [red] Uncaught Exception:
2023-07-24T14:42:05.035452838Z 24 Jul 16:42:05 - [error] ReferenceError: callback is not defined
2023-07-24T14:42:05.035506670Z     at ClientRequest.<anonymous> (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9)
2023-07-24T14:42:05.035523744Z     at ClientRequest.emit (events.js:400:28)
2023-07-24T14:42:05.035538059Z     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2023-07-24T14:42:05.035551892Z     at TLSSocket.emit (events.js:400:28)
2023-07-24T14:42:05.035574948Z     at emitErrorNT (internal/streams/destroy.js:106:8)
2023-07-24T14:42:05.035589985Z     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2023-07-24T14:42:05.035603892Z     at processTicksAndRejections (internal/process/task_queues.js:82:21)
2023-07-24T14:42:10.661695409Z 24 Jul 16:42:10 - [info] 

2023-07-24T14:44:05.069983517Z 24 Jul 16:44:05 - [red] Uncaught Exception:
2023-07-24T14:44:05.070552734Z 24 Jul 16:44:05 - [error] ReferenceError: callback is not defined
2023-07-24T14:44:05.070608826Z     at ClientRequest.<anonymous> (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9)
2023-07-24T14:44:05.070625419Z     at ClientRequest.emit (events.js:400:28)
2023-07-24T14:44:05.070639752Z     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2023-07-24T14:44:05.070654270Z     at TLSSocket.emit (events.js:400:28)
2023-07-24T14:44:05.070667937Z     at emitErrorNT (internal/streams/destroy.js:106:8)
2023-07-24T14:44:05.070681529Z     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2023-07-24T14:44:05.070695233Z     at processTicksAndRejections (internal/process/task_queues.js:82:21)
2023-07-24T14:44:07.529093361Z 24 Jul 16:44:07 - [info] 

2023-07-25T09:00:09.540446829Z 25 Jul 11:00:09 - [red] Uncaught Exception:
2023-07-25T09:00:09.541065305Z 25 Jul 11:00:09 - [error] ReferenceError: callback is not defined
2023-07-25T09:00:09.541131175Z     at ClientRequest.<anonymous> (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9)
2023-07-25T09:00:09.541148045Z     at ClientRequest.emit (events.js:400:28)
2023-07-25T09:00:09.541162563Z     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2023-07-25T09:00:09.541177193Z     at TLSSocket.emit (events.js:400:28)
2023-07-25T09:00:09.541190989Z     at emitErrorNT (internal/streams/destroy.js:106:8)
2023-07-25T09:00:09.541204896Z     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2023-07-25T09:00:09.541218674Z     at processTicksAndRejec

2023-07-28T03:26:10.883676632Z 28 Jul 05:26:10 - [red] Uncaught Exception:
2023-07-28T03:26:10.884243071Z 28 Jul 05:26:10 - [error] ReferenceError: callback is not defined
2023-07-28T03:26:10.884311367Z     at ClientRequest.<anonymous> (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9)
2023-07-28T03:26:10.884329163Z     at ClientRequest.emit (events.js:400:28)
2023-07-28T03:26:10.884343514Z     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2023-07-28T03:26:10.884357811Z     at TLSSocket.emit (events.js:400:28)
2023-07-28T03:26:10.884371496Z     at emitErrorNT (internal/streams/destroy.js:106:8)
2023-07-28T03:26:10.884385051Z     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2023-07-28T03:26:10.884398625Z     at processTicksAndRejections (internal/process/task_queues.js:82:21)
2023-07-28T03:26:13.835490094Z 28 Jul 05:26:13 - [info] 

2023-08-28T04:54:09.598840260Z 28 Aug 06:54:09 - [red] Uncaught Exception:
2023-08-28T04:54:09.599820362Z 28 Aug 06:54:09 - [error] ReferenceError: callback is not defined
2023-08-28T04:54:09.599892361Z     at ClientRequest.<anonymous> (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9)
2023-08-28T04:54:09.599966027Z     at ClientRequest.emit (events.js:400:28)
2023-08-28T04:54:09.599981971Z     at TLSSocket.socketErrorListener (_http_client.js:475:9)
2023-08-28T04:54:09.599995879Z     at TLSSocket.emit (events.js:400:28)
2023-08-28T04:54:09.600009341Z     at emitErrorNT (internal/streams/destroy.js:106:8)
2023-08-28T04:54:09.600022675Z     at emitErrorCloseNT (internal/streams/destroy.js:74:3)
2023-08-28T04:54:09.600036286Z     at processTicksAndRejections (internal/process/task_queues.js:82:21)
2023-08-28T04:54:12.518238804Z 28 Aug 06:54:12 - [info]

S474N commented 9 months ago

It's really unbearable, there are very frequent restarts of Nodered. Would it be possible to fix it somehow?!

This is just for today:

tom666-debug commented 9 months ago

Seems owner of this project is not able or willing to fix this (improved exception handling). Pretty sad ...

hflatoey commented 7 months ago

Same problem here, restarts about once every day...

7 Nov 13:19:03 - [red] Uncaught Exception: 7 Nov 13:19:03 - [error] ReferenceError: callback is not defined at ClientRequest. (/data/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9) at ClientRequest.emit (node:events:513:28) at TLSSocket.socketErrorListener (node:_http_client:494:9) at TLSSocket.emit (node:events:513:28) at emitErrorNT (node:internal/streams/destroy:157:8) at emitErrorCloseNT (node:internal/streams/destroy:122:3) at processTicksAndRejections (node:internal/process/task_queues:83:21) 7 Nov 13:19:07 - [info]

Welcome to Node-RED 7 Nov 13:19:07 - [info] Node-RED version: v3.1.0 7 Nov 13:19:07 - [info] Node.js version: v16.20.2 7 Nov 13:19:07 - [info] Linux 6.1.49-Unraid x64 LE

matz33 commented 7 months ago

Hi,

Same problem here. This module makes my Nodred crash several times a day. And unfortunately the guy behind this module is not willing to fix anything here. It is pretty simple to get rid of this module with a simple http request. Here is what I'm using and I have the exact same info, using http request :

The URL is : https://api.netatmo.com/api/getstationsdata The token is the one returned by netatmo when you authenticate to the site like explained in the doc of this module

Et voilà ! It gives me exactly the same json as the "detailed" section of the json returned by this buggy module.

You can get more URL exemples from API Netatmo here : https://cbornet.github.io/netatmo-swagger-decl/swagger-ui/ To use this page :

for exemple click on "Show/Hide" in front of "Station : Weather station specific methods"
click on "GET / getstationdata"
you will see a red exclamation mark : click on it. In the form, check "read_station" then "Authorize"
this will bring you to Netatmo authentication page, enter your credentials. Click accept
then the red exclamation mark is now a blue "i"
you can then click on "Try it out" below. This will return the data. In "Curl" part just below the button "Try it out" you have the URL to enter in the http request node.
For exemple : curl -X GET --header 'Accept: application/json' 'https://api.netatmo.net/api/getstationsdata?access_token=5.... The url you want to put in the request http node is here : https://api.netatmo.net/api/getstationsdata

tom666-debug commented 7 months ago

@matz33 Works like charme ... Thank you so much for sharing this with us! Finally I can get rid of the piece of trash module

ceLeXo114 commented 7 months ago

Was affected by the same errors as described above. The workaround from matz33 seems to be working for me so far. I just had to adjust the path (leave out .detailed) when reading out the individual values.

Thank you @matz33!

morpheus1984 commented 7 months ago

Hi guys, could maybe anyone help me with the token topic. I tried it, but I think I did not get the topic. I see the access and refresh token on the Netatmo api page, but I expires quit fast. What do I exactly need to do to get the right key? could you maybe help me to get it running?Thanks a lot.

tom666-debug commented 7 months ago

Hi guys, could maybe anyone help me with the token topic. I tried it, but I think I did not get the topic. I see the access and refresh token on the Netatmo api page, but I expires quit fast. What do I exactly need to do to get the right key? could you maybe help me to get it running?Thanks a lot.

I am facing the same issue. Regarding to the NetAtmo description, the token must be refreshed every 3 hours. Therefore the "refresh token" must be used.

Refreshing a token When you request a token (via grant type credentials or authorization code) you retrieve as well the validity timelapse and a refresh token. Once your token has expired, you'll have to request a new one using the grant_type refresh_token.

Endpoint: https://api.netatmo.com/oauth2/token Method: POST

Any ideas how this could be achieved?

matz33 commented 7 months ago

You are right : the token needs to be refreshed. You will find at the end of this post my flow to get the token refreshed. I've just finished it, and the token works 3 hours, so I will know in 3 hours if it refreshes correctly :)

Here is how it works :

Enter your token and refresh token + client id and client secrect in the node "Set Netatmo Creds & Tokens"
Trigger the inject node "Set first info"
Then, the inject node "Start" can be triggered either automatically after a deploy like I configured it (prefered method), or manually if needed
It will get the token, refresh token, and will refresh them after the expiration (returned in the payload by Netatmo) - 5 minutes
If error in getting the token it will retry after 1 hour. You can add here any kind of alert (email, etc) after node "Delay 1 hour on error" to alert you that there is an error and token was not returned (time out etc)
The node "Next refresh in..." displays the next time the refresh will occur
The token you need to use in the http request above is in Global "NetatmoAccessToken"
This is what I do after the node "Get Netatmo Data" : it gets the data needed

Hope that helps

matz33 commented 7 months ago

I created a flow here so eveybody can use it : https://flows.nodered.org/flow/843165d0046cac534864b65e633801a5

tom666-debug commented 7 months ago

@matz33 Just in case of a Node-RED restart, would it be an option to store/read the tokens values to/from a file instead of setting global variables?

matz33 commented 7 months ago

Good idea, I will try to work on this

matz33 commented 7 months ago

BTW after several hours and refresh, it seems to work well.

tom666-debug commented 7 months ago

it seems to work well.

Confirmed, also on my end its running stable since yesterday afternoon. I have noticed that the token and the refreshtoken as well didnt changed - My expectation was that every time I send a "refresh request" I will get a new token ... strange.

matz33 commented 7 months ago

Same here. Maybe they just want us to call the authent url regularly with both token and that is the refreshing the tokens themselves, without changing them

tom666-debug commented 7 months ago

just came across this:

https://www.oauth.com/oauth2-servers/access-tokens/refreshing-access-tokens/

If everything checks out, the service can generate an access token and respond. The server may issue a new refresh token in the response, but if the response does not include a new refresh token, the client assumes the existing refresh token will still be valid.

matz33 commented 7 months ago

@matz33 Just in case of a Node-RED restart, would it be an option to store/read the tokens values to/from a file instead of setting global variables?

For this, I'm using the option to save context data to the file-system described here : https://nodered.org/docs/user-guide/context#saving-context-data-to-the-file-system. After a restart, eveyrhing is restored in global variables

morpheus1984 commented 7 months ago

Hi Matz, I tried it, but something won't work. Maybe you can help me? 27.11.2023, 17:26:45node: Netatmo Data msg : Object object _msgid: "f412923e.50d37" payload: object error: object code: 1 message: "Access token is missing" topic: "" token: "Bearer XXXXXXXXXXX" statusCode: 400 headers: object server: "nginx" date: "Mon, 27 Nov 2023 16:26:45 GMT" content-type: "application/json; charset=utf-8" transfer-encoding: "chunked" connection: "close" cache-control: "no-cache, must-revalidate" expires: "0" x-xss-protection: "1; mode=block" access-control-allow-origin: "*" strict-transport-security: "max-age=31536000; includeSubDomains" x-powered-by: "Netatmo" x-node-red-request-node: "a23e33dc" responseUrl: "https://api.netatmo.com/api/getstationsdata" redirectList: array[0]

tom666-debug commented 7 months ago

@morpheus1984 Have you tried to generate a new pair of token/refreshtoken on the Netatmo Website (https://dev.netatmo.com)? I was also forced to do so because my "old" tokens didnt work anymore.

morpheus1984 commented 6 months ago

Hi, maybe I am not known enough, just refreshed the complete data on the NetAtmo sie, but I get the same response.

djiwondee commented 4 months ago

Coming back to the initial post from @morpheus1984. I have configured a complete new config with this node-red-contrib and it works quite well. But the incomprehensible and inexplicable crashes still happens some times

2024-02-18T20:11:16.469317+01:00 {{hostname}} Node-RED[2085783]: 18 Feb 20:11:16 - [red] Uncaught Exception:
2024-02-18T20:11:16.469942+01:00 {{hostname}} Node-RED[2085783]: 18 Feb 20:11:16 - [error] ReferenceError: callback is not defined
2024-02-18T20:11:16.470184+01:00 {{hostname}} Node-RED[2085783]:     at ClientRequest.<anonymous> (/home/pi/.node-red/node_modules/node-red-contrib-netatmo-dashboard/netatmo-dashboard.js:46:9)
2024-02-18T20:11:16.470353+01:00 {{hostname}} Node-RED[2085783]:     at ClientRequest.emit (node:events:518:28)
2024-02-18T20:11:16.470519+01:00 {{hostname}} Node-RED[2085783]:     at TLSSocket.socketErrorListener (node:_http_client:495:9)
2024-02-18T20:11:16.470681+01:00 {{hostname}} Node-RED[2085783]:     at TLSSocket.emit (node:events:518:28)
2024-02-18T20:11:16.470885+01:00 {{hostname}} Node-RED[2085783]:     at emitErrorNT (node:internal/streams/destroy:169:8)
2024-02-18T20:11:16.471046+01:00 {{hostname}} Node-RED[2085783]:     at emitErrorCloseNT (node:internal/streams/destroy:128:3)
2024-02-18T20:11:16.471236+01:00 {{hostname}} Node-RED[2085783]:     at processTicksAndRejections (node:internal/process/task_queues:82:21)
2024-02-18T20:11:16.616556+01:00 {{hostname}} systemd[1]: nodered.service: Main process exited, code=exited, status=1/FAILURE
2024-02-18T20:11:16.617069+01:00 {{hostname}} systemd[1]: nodered.service: Failed with result 'exit-code'.
2024-02-18T20:11:16.617429+01:00 {{hostname}} systemd[1]: nodered.service: Consumed 6h 16min 51.144s CPU time.
2024-02-18T20:11:36.857489+01:00 {{hostname}} systemd[1]: nodered.service: Scheduled restart job, restart counter is at 1.
2024-02-18T20:11:36.858498+01:00 {{hostname}} systemd[1]: Stopped nodered.service - Node-RED graphical event wiring tool.

matz33 commented 4 months ago

I think you should definitely abandon this shitty node and use my exemple here https://gist.github.com/matz33/843165d0046cac534864b65e633801a5. Several users succeeded in using it. Have you tried to find a solution in getting the access token on netatmo website and add them in my flow ? On my side, it is working without any errors since several months

djiwondee commented 4 months ago

@matz33 Thanks for pointing me to the gist. Have it implemented just right and it is working as expected. Haven't had so much to change related to the slightly different payload keys.

Have you tried to find a solution in getting the access token on netatmo website and add them in my flow ?

Yes, I did. There is an app management available at https://dev.netatmo.com/apps/

morpheus1984 commented 3 weeks ago

Hi,

I now tried to use your nodes, unfortunately its not working, maybe its because I am not a pro, just a copier. :)

I ve put my information in the node, but I always get the follwoing error:

{"_msgid":"1172705c.dd29b","payload":{"error":{"code":1,"message":"Access token is missing"}},"topic":"","token":"Bearer 5656ab5465d1cXXXXXXXXXXXd1c471498b463a|0ca84edfcfa8fb1b1dXXXXXXXXXX","statusCode":400,"headers":{"server":"nginx","date":"Tue, 04 Jun 2024 14:11:04 GMT","content-type":"application/json; charset=utf-8","transfer-encoding":"chunked","connection":"close","cache-control":"no-cache, must-revalidate","expires":"0","x-xss-protection":"1; mode=block","access-control-allow-origin":"*","strict-transport-security":"max-age=31536000; includeSubDomains","x-powered-by":"Netatmo","x-node-red-request-node":"e0fa9ff4"},"responseUrl":"https://api.netatmo.com/api/getstationsdata","redirectList":[]}

Are there any tips you can give to me?

Am 19.02.2024 um 09:43 schrieb matz33 @.***>:

I think you should definitely abandon this shitty node and use my exemple here https://gist.github.com/matz33/843165d0046cac534864b65e633801a5 https://gist.github.com/matz33/843165d0046cac534864b65e633801a5. Several users succeeded in using it. Have you tried to find a solution in getting the access token on netatmo website and add them in my flow ? On my side, it is working without any errors since several months

— Reply to this email directly, view it on GitHub https://github.com/guidone/node-red-contrib-netatmo-dashboard/issues/21#issuecomment-1951956165, or unsubscribe https://github.com/notifications/unsubscribe-auth/A57YP3WWVMHLN4N3TQQNKA3YUMGBNAVCNFSM6AAAAAAVA5HPIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJRHE2TMMJWGU. You are receiving this because you were mentioned.

Mike4466 commented 2 weeks ago

After I couldn't get matz33's solution to work a few months ago, I finally succeeded. However, I had to generate several different tokens at https://dev.netatmo.com/apps/ until the communication to the Netatmo server finally worked. Previously, the tokens were denied. The paths to the values are slightly different from the old solution, but the modification took about 10 minutes for my setup. I hope that this will now work permanently. Thank you @matz33 for your work!

ceLeXo114 commented 5 days ago

Is it just me or others too?

Since @morpheus1984 wrote his post 3 weeks ago, I have had problems again with @matz33's previously smooth solution.

Every time I deploy in Nodered, the Netatmo- Tokens are valid and Nodered thus grants access to the Netatmo API. I then have to regenerate the tokens in the Netatmo app I created (at https://dev.netatmo.com/apps/ see https://github.com/guidone/node-red-contrib-netatmo-dashboard /issues/21#issuecomment-1952325080 and then enter this again in the node of @matz33 and deploy it once - then everything works normally again until I deploy again.

Does this happen to anyone else and are there any solutions? That wasn't the case before. Maybe Netatmo has changed something about it?

tom666-debug commented 5 days ago

I was facing the same issue.

In order to solve this I am writing the intial or updated tokens to a file now. Please be aware whenever you send a "refresh request" it is highly likley that the Netatmo API will provide you with a new pair of tokens. On redeploy or NodeRED startup the flow reads the last updated tokens from the file now. Since then no more issues with obsolete tokens.

My complete flow looks like this now:

matz33 commented 2 days ago

@tom666-debug I don't understand why you store the tokens on a local file. Saving context data in file system like described here https://github.com/guidone/node-red-contrib-netatmo-dashboard/issues/21#issuecomment-1826865752 will have the same result : each time nodered is restarted or redeployed, it will read the tokens from the file system and store them in variables, and the flow will work.

Have you enabled this option in nodered ?

matz33 commented 2 days ago

This has been discussed here also : https://gist.github.com/matz33/843165d0046cac534864b65e633801a5?permalink_comment_id=5078020#gistcomment-5078020

tom666-debug commented 2 days ago

Have you enabled this option in nodered ?

No, I was not aware of this. Seems I have developed my own solution ;-) I will give it a try and let you know.

morpheus1984 commented 1 day ago

Is anyone using the flows with Node Red Version 1.29?

guidone / node-red-contrib-netatmo-dashboard

Node Red crashes #21