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
Node Red crashes #21
Comments
I am facing the same issue with Node-RED is crashing/restarting caused by the netatmo-dashboard node. 24 Feb 12:32:27 - [red] Uncaught Exception: |
And what does that error mean? You have some idea? |
@tom666-debug @morpheus1984 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. |
This is really an issue :-( Today my Node-RED Instance crashed 6 times in a row because of this. |
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. I have now set that Node Red does not give up after 3 times reboot but endlessly tries to start Node Red after crashes. 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: |
Hi Mike, i also found out that this Happens when my Internet Connection gets lost. |
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. |
Also have every day crash of NodeRED:
|
Seems owner of this project is not able or willing to fix this (improved exception handling). Pretty sad ... |
Same problem here, restarts about once every day... 7 Nov 13:19:03 - [red] Uncaught Exception: Welcome to Node-RED |
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 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/
|
@matz33 |
Was affected by the same errors as described above. Thank you @matz33! |
Hi guys, could maybe anyone help me with the token topic. I tried it, but I think I did not get the topic. |
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 Endpoint: https://api.netatmo.com/oauth2/token Any ideas how this could be achieved? |
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 :
Hope that helps
|
I created a flow here so eveybody can use it : https://flows.nodered.org/flow/843165d0046cac534864b65e633801a5 |
@matz33 |
Good idea, I will try to work on this |
BTW after several hours and refresh, it seems to work well. |
Confirmed, also on my end its running stable since yesterday afternoon. |
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 |
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. |
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 |
Hi Matz, I tried it, but something won't work. Maybe you can help me? |
@morpheus1984 |
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
|
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 ? |
@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.
Yes, I did. There is an app management available at https://dev.netatmo.com/apps/ |
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
The text was updated successfully, but these errors were encountered: