# Cron-plus 2.1.0 - system time change detected?

**URL:** <https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041>\
**Category:** General\
**Created:** [20 November 2023 19:44 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041 "2023-11-20T19:44:32Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Post date:** [22 November 2023 19:42 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/21 "2023-11-22T19:42:47Z")

</div>

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

```auto
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.

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [22 November 2023 21:54 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/22 "2023-11-22T21:54:23Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [23 November 2023 10:52 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/23 "2023-11-23T10:52:14Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [25 November 2023 10:03 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/24 "2023-11-25T10:03:19Z")

</div>

Hi Ralph,

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

Hannes

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [4 December 2023 12:25 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/25 "2023-12-04T12:25:16Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Post date:** [4 December 2023 12:50 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/26 "2023-12-04T12:50:06Z")

</div>

> [@juntiedt](#):
>
> My this have something to do with the last patch?

Don't think so.

> [@juntiedt](#):
>
> ETIMEDOUT 20.23.199.179:443

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.

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [4 December 2023 15:57 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/27 "2023-12-04T15:57:37Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![ralphwetzel](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ralphwetzel/32/53713_2.png) [@ralphwetzel](https://discourse.nodered.org/u/ralphwetzel)\
**Post date:** [4 December 2023 17:03 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/28 "2023-12-04T17:03:33Z")

</div>

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...

---

<div class="post-metadata">

**Author:** ![juntiedt](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/juntiedt/32/58357_2.png) [@juntiedt](https://discourse.nodered.org/u/juntiedt)\
**Post date:** [5 December 2023 10:23 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/29 "2023-12-05T10:23:46Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [19 December 2023 10:24 UTC](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041/30 "2023-12-19T10:24:14Z")

</div>

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

[Previous page](https://discourse.nodered.org/t/cron-plus-2-1-0-system-time-change-detected/83041.md?page=1)