Cron-plus 2.1.0 - system time change detected?

General
21

Hi!
I'm not convinced this is my best idea - but I've created that fork & modified it as proposed.
You need to install it with

npm install https://github.com/ralphwetzel/node-red-contrib-netatmo-dashboard.git#dev

Testing this is on you. If positive, I'll create a PR.

1 Like
22

thanks,
I will try it and let you know the result.

23

Hi Ralph,

It is installed and running.
As the error sometimes took very long before it crashed, I will observe it at least 48 hours.
Many thanks for your quick support!
I will keep you updated...

Hannes

24

Hi Ralph,

good job!
48 hours without a problem! Many thanks for your suport and software fix!

Hannes

25

Hi Ralph,
unfortunately I am receiving this http request error message from netatmodashboard node with a strange adress (looks like its including the year). This does not stop Netatmo working. The next call to Netatmo is ok. My this have something to do with the last patch?

Fehlerzeitpunkt: 04-12-2023 @ 02:07:47 / RPI: Heizung / Flow: sensors NetAtmo / Fehlermeldung: Error: connect ETIMEDOUT 20.23.199.179:443 / Fehler ID: 7f1769fefb186826 / Fehlertyp: netatmo-dashboard / Fehlernode: undefined / Fehlerzähler: 1

I comes nearly at the same period then the error above but it does not reboot node-red.
Please have a look at the code you changed.

26

Don't think so.

This looks like something is trying to connect to a https (443) service at netatmo (20.23.199.179) ... and this request times out.
Given that the node works correct (which it does!), this seems to be rather a server side error than sth on the client (your) side.
It might be, that this ETIMEDOUT error used to be the trigger of the callback case (as reported before). With the change made, this error is now handled appropriately. It's still an error reported - but the code seems to be able to manage it.

27

now I get this message:

Fehlerzeitpunkt: 04-12-2023 @ 16:50:11 / RPI: Heizung / Flow: sensors / Fehlermeldung: Unable to refresh the access token / Fehler ID: 1e031489dbb28d31 / Fehlertyp: netatmo-dashboard / Fehlernode: undefined / Fehlerzähler: 1

I generated a new refresh token with postman as usual. It works for a little while and then the above error message appears. How would you fix this error?

28

Again - this looks like another server side error.
If it works for a while and then errors, there's nothing to fix on your end.
The only possible action is to accept & then retry...

29

Hi Ralph,
I change to a new NetAtmo flow which works better. Manages the authorization perfectly

30

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.