thanks for pointing this out, will do a search.
but my setup will not be connected always to the wifi/internet, is that an issue in my case?
How are you proposing to set the time? Unless you have an RTC it will lose the time each time you power off.
1 Like
If you want scheduled events - very much!
If you want reliable schedules you need WiFi or a RTC
Or get a Pi 5! The Pi 5 now has an RTC
(good luck getting one any time soon tho)
1 Like
yup, was thinking about the rpi5 too, i've seen that has an rtc.
anyway, thanks for the debug session guys, at least i know what's up now.
What are they showing? Hundreds of node red related lines in a few minutes suggests there may be some other problem going on.
The point was whether that line occurs before or after the boot inject after three seconds. If it had appeared before the inject then it would not cause a problem. If after then it might cause a problem.
There is line in the systemd script, /lib/systemd/system/nodered.service, that you can uncomment which is supposed to delay node-red startup until after the time is synced. There is a comment in the script indicating what to do.
i have two other flows with cronplus nodes and lot of 1 - 3 - 10 second, etc schedules, those are spamming the list too.
the line with the time update occurs after the inject msg so there is that.
thanks for the info on the systemd script i will look into that now.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
