EDIT: PLEASE DO NOT PANIC! THERE IS A SUPER EASY FIX - JUST READ THE THREAD AND ADD ANY CONSTRUCTIVE FEEDBACK
This morning I saw that Node Red update to version 12.x removed the STOPTIMER node as it is not used much and has not been updated in over 5 years. This made me wonder whether there is a better, or more conventional way, of doing what I do using the STOPTIMER node.
A typical example of how I use it is to turn off something after a period of time. The delay can be reset by, for example, new motion events. If the device needing to be turned off gets turned off in some other way, the timer is cancelled so that the turn off command is not fired over the already busy Z* mesh network.
Are there better ways of doing the above without using the STOPTIMER node?
Is there a better node to use with the same functionality? I found a few that appear to be forks of this one, but they too seem to have low usage so I worry I will find myself with lots of flows using an unsupported node. In other words I am trying to reduce my exposure to the risk of needing to update a large number of nodes all of a sudden.
Edit: I am aware the STOPTIMER node can be re-installed, and I did, but now that I saw the last update was over 5 years ago, and that it is no longer installed by default with Node Red, I would prefer to adopt a more recent/supported alternative.
EDIT AFTER LOTS OF POSTS IN THIS THREAD:
As discussed in the thread below, the trigger node is a far superior node than StopTimer. I updated all my flows to use the trigger node and everything works fine. To mimic the StopTimer node minimizing any other changes you will need to set it up like this (thanks to @Mikefila @quizzical @mchinery):
This is one of my simple flows where I replaced one node for the other with no other changes. One could change the change node (see below in yellow) sending msg.payload: STOP to sending msg.reset: true to reset the trigger eliminating the need to add STOP inside the trigger node.