hi, the cronplus node does not retain the stop/start state of the schedules after a reboot. i have a cronplus node set up with 3 different schedules and if i stop let's say the first then reboot the raspberry pi, all 3 schedules will run on after boot. context memory is enabled, i followed the in…

[image] biros: also the lowest delay i could go was 60 seconds. The log should not be much bigger than 100 lines. It is no problem to post that here. However, have a look for a message like this. [info] [cronplus:SimCron] System Time Change Detected - refreshing schedules! If the system ti…

It works for me, I get events during the first three seconds then the status shows all stopped. Does it stop if you manually click the stop node? What is it showing in the persist state dropdown? Set the persist state to none and see if anything changes.

That is weird, Yes it stops when i stop it manually. This is the persists state (also tried with "none"): [image] I don't know what to do ... Here is a screen before a reboot, the cronplus node status is "All stopped" and the debug node on the inject node has nothing; [image] And here is a sc…

What happens if you click the down arrow on the Deploy button and select Restart Flows?

The flow behaves as it should, timers start, then after 3 seconds the inject once node stops them. But why like this and not on system reboot?

[image] biros: But why like this and not on system reboot? I have no idea. What OS are you running on, how did you install node-red and how are you making node-red start on boot?

[image] biros: i doing something wrong? Apparently not. As an experiment, just to rule it out, comment out the context memory bit in settings and try again. Assuming that doesn't make a difference, enable both the debug nodes and set them to output to the console. Then after boot look back…

i think the 120 sec delay did its trick. also checked the console log and when the delay was 3 sec, the inject once command was done before the cronplus things in the log. can it be that the cronplus thingy loads waaay after boot? in this case i have to adjust the delay for a longer one. (i tried…

Are you connected via wifi? I have a suspicion that I know the problem. Please set it back to three seconds, reboot, wait a few minutes, then run this command and paste the full output here. journalctl -b -u nodered --no-pager

yes i am on wifi. i assume that command has to be run in terminal, but the output is really big, the output did not fit in my terminal and i doubt it will fit here. also the lowest delay i could go was 60 seconds. with a 60 second delay the cronplus node stops the timers and the output shows up a…

Cronplus node schedule(s) state at boot

General

biros 5 November 2023 12:32 13

setup is pretty generic, raspberry pi os (64bit) latest and installed by using that bash curl command from the manual, then i uncomment the context memory part in the config file.
i enable it with systemctl then start.
after this it runs on boot automatically.
am i doing something wrong?

Topic		Replies	Views
Node-red-contrib-cron-plus and Save State General cron-plus	6	112	3 May 2025
Cron-plus can't start a paused schedule again General home-assistant	72	936	20 October 2025
Cronplus node input settings dont work General	20	278	6 October 2023
Cronplus no message after node-red reboot General	5	136	5 November 2023
Bug with node-red-contrib-cron-plus? General home-assistant	25	1350	10 June 2022

Cronplus node schedule(s) state at boot

Related topics