I have looked at the NTPTime node for getting the time from an Internet time server, this node would work for me if I could make it not update as often. If seems that the slowest I can set is every 10 seconds.
I'm want to use a Raspberry Pi, and they will be used as an "Edge Of Network" device (very remote locations) I have 100's that I want to implement and I pay for bandwidth. If I have 100's of these units acessing the internet every 10 seconds that will consume a lot of bandwidth I don't want to pay for.
Linux has built-in NTP. Set the correct timezone and appropriate country NTP server (usually a group so that the NTP server can pick the best one). It should query no more than once an hour if I remember rightly, quite possibly only once a day. More than sufficient. No CRON, Node-RED or anything else needed.
The nodes are not intended to update the system time.
That's why the nodes work on every system.
The nodes aim to access the date and time elements for later processing.
If you have access to the internet, why not use NTP?
For example, the node-red-contrib-redplc-ntptime node stores in global context variables.
Therefore date/time queries can be made with it. @damica51 should use the node-red-contrib-redplc-systime or node-red-contrib-iiot-systime for time queries.
These query the system time.
Of course you can make a node that updates the system time via NTP.
But that is actually the task of the operating system.
node-red-contrib-cron-plus is a very general purpose node.
Of course, the nodes in the example can also compare other
number sources (e.g. from an analog-to-digital converter).
You can link the nodes in any combination (AND, OR ..).
Many roads lead to Rome
Except that the public NTP service most certainly should not be spammed for this purpose. That is why all OS's handle it at the OS level. The NTP services are run as a free public service. If you want to do more rapid scans of NTP, run your own local NTP service that links to a public one. In fact, if you read the terms of service for NTP servers I believe that you will find instructions in them not to repeated query them as this can block the service for other people.
Sorry, but I can't personally see any reason to use a node like that.
Don't do this.
Your node has got about 15 downloads per week over the last year; there seems to be an interest in it - despite some people here expressed strong arguments against using it.
That's yet the nature of free speech ... and a situation you have to cope with when trying to contribute to a community effort.