# Node-Red on RPi restarts after ~2 weeks

**URL:** <https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210>\
**Category:** General\
**Created:** [23 September 2024 16:27 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210 "2024-09-23T16:27:41Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [19 October 2024 12:24 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/21 "2024-10-19T12:24:47Z")

</div>

I would start by removing the following nodes (in order, not at the same time)

- calculate
- smooth
- counter

The first 2 store data in an internal array for later computation

In fact, looking at the src of the calculate node, it (for some reason) stores the entire `msg` object (even though it only appears to use `payload` in computing the averages!).

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [19 October 2024 12:37 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/22 "2024-10-19T12:37:01Z")

</div>

Also, do you actually use play audio on all of them?

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [19 October 2024 18:47 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/23 "2024-10-19T18:47:16Z")

</div>

@Steve-Mcl i just deactived these three one after one. Ram was at 34%, after deactivating it rises up to 47% (in 3 minutes)

@Colin I don´t use play audio.

Could it theoretically be a hardware defect of the ram?

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [21 October 2024 05:58 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/24 "2024-10-21T05:58:10Z")

</div>

> [@Steve-Mcl](#):
>
> - calculate
> - smooth
> - counter

I use only one calculate node in this flow.  
in my other node-red I use \> 10 without problems.

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/8/d846631e3ff23ef9a2f67b81cada055e448c774e.png)  
the calculate gets every 2s this msg.object

in my other node-red the calculate gets much more crap in msg.object

I use only one smooth node in this flow, in my other node-red I use \> 20 without problems.  
it´s 100% the same input like in my other node-red:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/5/e5c10a6263052a06bd1b0cb8c02ddc9c17ef525c.png)  
every hour max. 35 msg

and I also use only one counter node, which has actually not been used since the reboot.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [21 October 2024 18:45 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/25 "2024-10-21T18:45:02Z")

</div>

The only major difference to the other systems and my last idea is the following:

boot/config.txt add:

```auto
[all]
gpio=4,5,7,11,17,22,23,24,25,26,27=op,dl
gpio=6,8,9,10,12,13,16,21=ip,pu

```

and some gpio nodes:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/d/6da5a4c5bd1c1d9fc4eeb0ccae948a2fe64933ad.png)

with initialization

Can this be ruled out as a reason?

next step: 2nd RPi as a pure simulator (without modbus)

is it completely impossible to see a detailed RAM listing in the Node Red core?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [22 October 2024 14:27 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/26 "2024-10-22T14:27:00Z")

</div>

> [@Becker](#):
>
> Can this be ruled out as a reason?

It isn't going to be a fundamental config issue, it is what is being done with the data.

You showed an installed node list earlier, but said that some of them are unused. I would start by removing all those that are not used and making sure all the rest are up to date.

You showed earlier you were getting regular modbus timeouts. Do the other systems suffer from this too? It is certainly not impossible that something like this could find a memory leak that has not been noticed previously.

Next time you restart could you show us the full node red startup log please.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [22 October 2024 16:27 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/27 "2024-10-22T16:27:18Z")

</div>

> [@Colin](#):
>
> Next time you restart could you show us the full node red startup log please.

of course.

I´ve some other systems with much more modbus read errors ! (without ram problem)

the most similar system, which has no problems with ram, has no gpio and no modbus.

So yesterday I took a old RPi2 with bookworm + NR and insert my flow without modbus,  
the ram rose and rose overnight !  
today I deleted all gpio nodes and restarted the RPi2.  
I´ll now delete one after one node to find the problem.

One more thing occurs to me: my other RPi with gpio nodes (and 5 modbus devices), wich has no problem with ram, has installed Node JS 18,x.

I could also test a downgrade from 20,x to 18,x.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [22 October 2024 19:33 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/28 "2024-10-22T19:33:41Z")

</div>

Did you uninstall the unused node types and check the others are up to date?

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [23 October 2024 05:57 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/29 "2024-10-23T05:57:24Z")

</div>

I did not uninstall the pre-installed nodes (ping, serialport, audio, random) - every RPi got these, sorry, I see no sense.  
the installation is 1 day old, of course all nodes are up to date.

today I compared my flow with the customer flow again.  
I came across a function that only I have:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/c/7/c73e195d8ad21d904cb6bb578f81cde46f40c7d7.png)  
after a reboot/restart msg.payload.S is undefined:  
 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/f/1fdf778c75cf2409e439c857d5b1b6c4db60a331.png)  
the object enters:

```auto
let Z = msg.payload.Z;
let S = msg.payload.S;
if (Z < S || S == null) {
    return;
}
else if (Z >= S) {
    msg.payload = 0;
} 
msg.topic = "aus";
return msg;

```

could this be the reason for the rising ram ?

I admit, I programmed it really badly 😖

I changed it on my Test-RPi2 and it stays at 17%.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2024 07:39 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/30 "2024-10-23T07:39:45Z")

</div>

> [@Becker](#):
>
> I did not uninstall the pre-installed nodes (ping, serialport, audio, random) - every RPi got these, sorry, I see no sense.

No they don't all have those nodes installed. The [recommended install script](https://nodered.org/docs/getting-started/raspberrypi) does not install them. How did you instal node-red? The sense is that they consume valuable memory even if not used and slow down the browser startup time every time you open the editor.

> [@Becker](#):
>
> the installation is 1 day old, of course all nodes are up to date.

That depends on how you installed node red. Some installations come with pre-installed old versions of nodes.

> [@Becker](#):
>
> could this be the reason for the rising ram

The code in that function will not cause a memory leak, but if you are sending erroneous data onwards to following nodes then I have no way of knowing what that might be doing.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [23 October 2024 08:01 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/31 "2024-10-23T08:01:31Z")

</div>

> [@Colin](#):
>
> The [recommended install script](https://nodered.org/docs/getting-started/raspberrypi) does not install them.

... it does install them if you choose to add Pi nodes. They will only fractionally slow down startup of Node-RED - little or no effect on opening editor.

I would more suspect the modbus node not cleaning up properly after the errors it seems to get occasionally. But even those I would expect to be garbage collected eventually.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [23 October 2024 08:14 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/32 "2024-10-23T08:14:49Z")

</div>

> [@dceejay](#):
>
> it does install them if you choose to add Pi nodes.

I did not realise that. Thanks for the correction.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [23 October 2024 11:18 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/33 "2024-10-23T11:18:44Z")

</div>

I installed NR with:

```auto
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)

```

always

no pre-installed !

@dceejay on the RPi2 (simulator) is modbus completely deactivated.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [27 October 2024 11:37 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/34 "2024-10-27T11:37:01Z")

</div>

I don´t understand NR behavior.

the other ("customer") node-red RPi3 runs over 20 days with constant 29% ram, after 20 days ram rose \>40%. I didn´t change anything, just look "top".

my RPi3 now rose over 40% too and what I also don't understand are these cpu peaks:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/4/4421d348af575a59a2a53cf380cbc9975878f713.png)  
every 3 min. I´ve no cron-plus with 3min.  
in the first days / after restart the peaks are very low, barely visible and with the length of the uptime they increase. 🧐  
after reboot:  
 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/8/e8f1af222b0dd8d018e6250717324e79f5e516fc.png)

> [@Colin](#):
>
> Next time you restart could you show us the full node red startup log please.

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/e/5eeb32754c6ee8747d16a0fa43d51cc1caa523d1.png)

After reboot in system journal:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/5/0526a9d99fd005806d0673ca0c602cc72c95c2f9.png)  
the cron-plus says:

```auto
System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application

```

what does that mean? could this be reason for cpu peaks or rising memory?

last idea: delete all cron-plus nodes and replace with inject (much work for me)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [27 October 2024 11:52 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/35 "2024-10-27T11:52:36Z")

</div>

> [@Becker](#):
>
> ```auto
> System Time Change Detected - refreshing schedules! If the system time was not changed then this typically occurs due to blocking code elsewhere in your application
> 
> ```
> 
> what does that mean? could this be reason for cpu peaks

Reason - no. Clue - yes. As it says, something is blocking/hogging the Node Event loop (i.e. high CPU usage) to the extent that nodejs didnt have a chance to see the system clock change for 5 seconds. That is highly indicative of a heavy synchronous process in your flows/nodes

> [@Becker](#):
>
> last idea: delete all cron-plus nodes and replace with inject (much work for me)

Sure, you can remove the thing informing you that there is a problem - but it wont fix your problem. The graph is backing up what cron-plus is telling you - that the NodeJS event loop is being blocked by a synchronous process.

As for what is hogging the CPU, only you can determine by looking at the flows you have written. Hints:

- Are you looping large data arrays?
- Are you processing large things like images or audio or files?
- Are you doing synchronous file reads or writes?
- It could even be the garbage collection kicking in
- It could be a badly written node. for example, the average or counter node I mentioned before - i.e. holding on to crap loads of memory for no reason.

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [27 October 2024 13:20 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/36 "2024-10-27T13:20:47Z")

</div>

I repeat 🥴 no audio, no images, no syn. file reads or writes, no larage arrays.

Now I deleted the average node (from simulator RPi2), and I have to wait for several days.

the average node gets every 5s:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/1/d15f27e95ccf23469ae75fbcfdf5aecb33da0bc8.png)

the counter node gets some crap from cronplus node:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/a/8aaa6dd854278cfbdd4ef164119902f952d601a9.png)

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [30 October 2024 08:13 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/37 "2024-10-30T08:13:38Z")

</div>

I came across a hot lead: I replaced all cronplus nodes by injects:

 ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/3/73e218ef99ec6087b7a4086660dbcff642594452.png)  
never saw such a low mem% and cpu load goes to 0 - 0,01

I think I have to talk to Maintainer steve-mcl 🫠

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [30 October 2024 09:45 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/38 "2024-10-30T09:45:30Z")

</div>

Could you restore the original flow and export all the cron nodes, then go back to the new flow and export all the equivalent Inject nodes please, so we can see what the difference is.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [30 October 2024 11:44 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/39 "2024-10-30T11:44:00Z")

</div>

> [@Becker](#):
>
> I came across a hot lead: I replaced all cronplus nodes by injects:
> 
> ![grafik](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/3/73e218ef99ec6087b7a4086660dbcff642594452.png)
> 
> never saw such a low mem% and cpu load goes to 0 - 0,01

You are simply masking the real issue.

Yes, Cron-plus has additional data in its msg (for advanced usage) - its what is holding on to extra data that is your issue. What you have done could easily been done with an inline function node to clean up the msg!

Also, did you re-enable all the stuff you disabled/deleted before coming to your final conclusion?

---

<div class="post-metadata">

**Author:** ![Becker](https://avatars.discourse-cdn.com/v4/letter/b/c77e96/32.png) [@Becker](https://discourse.nodered.org/u/Becker)\
**Post date:** [30 October 2024 12:23 UTC](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210/40 "2024-10-30T12:23:15Z")

</div>

two of several cronplus nodes for example:

```auto
[{"id":"f575aa0996438761","type":"cronplus","z":"5f6e5e5e2b5d2c03","name":"Daten","outputField":"payload","timeZone":"","storeName":"","commandResponseMsgOutput":"output1","defaultLocation":"","defaultLocationType":"default","outputs":1,"options":[{"name":"Modus","topic":"Modus","payloadType":"global","payload":"openwbModus","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"Überschuss","topic":"U","payloadType":"global","payload":"Übers-ohne-LP","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"Offset","topic":"offset","payloadType":"global","payload":"offset","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"Sofort","topic":"sofort","payloadType":"flow","payload":"sofort","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"min I","topic":"minI","payloadType":"flow","payload":"minI","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"frc","topic":"frc","payloadType":"flow","payload":"frc","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"go-e","topic":"goe","payloadType":"global","payload":"LP2-Leistung","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"Tibber","topic":"Tibber","payloadType":"flow","payload":"Tibber","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"I max","topic":"Imax","payloadType":"global","payload":"Imax","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"Phasen","topic":"phasig","payloadType":"flow","payload":"Phasen","expressionType":"cron","expression":"*/5 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}],"x":90,"y":1360,"wires":[["2bcf40094ea7e9ed"]]},{"id":"45417146841658f2","type":"cronplus","z":"5f6e5e5e2b5d2c03","name":"PV-laden","outputField":"payload","timeZone":"","storeName":"","commandResponseMsgOutput":"output1","defaultLocation":"","defaultLocationType":"default","outputs":1,"options":[{"name":"Überschuss","topic":"U","payloadType":"global","payload":"Übers-ohne-LP⌀","expressionType":"cron","expression":"*/10 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"PV-laden","topic":"PV","payloadType":"global","payload":"openwbModus","expressionType":"cron","expression":"*/10 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"SoC Freigabe","topic":"socfreigabe","payloadType":"global","payload":"socfreigabe","expressionType":"cron","expression":"*/10 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"},{"name":"Start PV","topic":"start","payloadType":"global","payload":"startpv","expressionType":"cron","expression":"*/10 * * * * *","location":"","offset":"0","solarType":"all","solarEvents":"sunrise,sunset"}],"x":100,"y":1140,"wires":[["d63e39946820db0a"]]}]

```

(you can see all if you would import my flow #19)

replaced on my RPi2 simulator by for example only one:

```auto
[{"id":"23f8c7079d1db506","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"Modus","payload":"goeModus","payloadType":"global","x":130,"y":860,"wires":[["1a3302883aa58f9f"]]},{"id":"73f0b8ed0105ee74","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"U","payload":"Übers-ohne-LP","payloadType":"global","x":150,"y":900,"wires":[["1a3302883aa58f9f"]]},{"id":"4b6e611ea9c0e3ff","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"offset","payload":"offset","payloadType":"global","x":120,"y":940,"wires":[["1a3302883aa58f9f"]]},{"id":"efdb2f8d99abbf97","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"sofort","payload":"sofort","payloadType":"flow","x":110,"y":980,"wires":[["1a3302883aa58f9f"]]},{"id":"cd5d0229634d636b","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"minI","payload":"minI","payloadType":"flow","x":100,"y":1020,"wires":[["1a3302883aa58f9f"]]},{"id":"579ca51ceec4eb8e","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"openwb","payload":"LP1-Leistung","payloadType":"global","x":140,"y":1060,"wires":[["1a3302883aa58f9f"]]},{"id":"7f7c6bb8ad586aeb","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"Tibber","payload":"Tibber","payloadType":"flow","x":110,"y":1100,"wires":[["1a3302883aa58f9f"]]},{"id":"8c9a7ebdb43eae65","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"Imax","payload":"Imax","payloadType":"global","x":110,"y":1140,"wires":[["1a3302883aa58f9f"]]},{"id":"80f73b02af4e7186","type":"inject","z":"c09741270c88473d","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"5","crontab":"","once":false,"onceDelay":0.1,"topic":"phasig","payload":"Phasen","payloadType":"flow","x":120,"y":1180,"wires":[["1a3302883aa58f9f"]]},{"id":"1a3302883aa58f9f","type":"join","z":"c09741270c88473d","name":"Objekt","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\\n","joinerType":"str","accumulate":false,"timeout":"","count":"9","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":520,"y":1000,"wires":[["a8e803f8e13c7275","0cabbb1ba85a5b9b"]]}]

```

> [@Steve-Mcl](#):
>
> Yes, Cron-plus has additional data in its msg (for advanced usage) - its what is holding on to extra data that is your issue. What you have done could easily been done with an inline function node to clean up the msg!

you mean delete:

```auto
[{"id":"d63e39946820db0a","type":"change","z":"5f6e5e5e2b5d2c03","name":"lösche","rules":[{"t":"delete","p":"cronplus","pt":"msg"},{"t":"delete","p":"scheduledEvent","pt":"msg"}],"action":"","property":"","from":"","to":"","reg":false,"x":90,"y":1200,"wires":[["86ef66a806be684d"]]}]

```

yes I added the delete node after every cronplus to be on the safe side!

the RPi3 runs now with cronplus + delete, I´ll see in a few days/weeks if mem is rising again.  
since yesterday it is at 26% - much more than the RPi2.  
the cpu peaks every 3min are still there at the RPi3.

I will let the RPi2 (simulator) run as well a few weeks (with the inject nodes instead of cronplus) - the graphical interface looks really bad without cronplus ☹

than I will decide, if I delete all cronplus on RPi3 (productiv system)

[Previous page](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210.md?page=1)

[Next page](https://discourse.nodered.org/t/node-red-on-rpi-restarts-after-2-weeks/91210.md?page=3)