I am currently testing a flow that has multiple 'eztimer' nodes in it. These work great for scheduling something to run once a day, but as soon as they have triggered for the day, they won't trigger again until the next day.
For testing, this is a little too long to wait, so looking for a way to reset a node's internal state, even if it is a little brutal.
I have tried sending it a msg.reset but the node doesn't handle them. Restarting node-red doesn't reset them (nor should it). Changing the time in the node properties only changes the next day's scheduled time. The only workaround I have at the moment is to delete the nodes and re-wire them into the flow and set their properties again. Yes, I could inject msgs to simulate a trigger, but given this is for feeding animals, I want to be sure that the flow and the nodes work end-to-end before I put it into 'production'.
Is there a way to reset a node, or even all nodes to help with testing (I could then use a function to continuously inject new schedules into nodes to have them trigger within minutes).
Perhaps I need to temporarily hack the node to respond to a message and 'restart the schedules'.