Release Notes

The rest of this wiki is deliberately version-silent — it always describes the currently published behavior. This page is where version specifics live: every release is listed here, newest first, and any behavioral change between versions is documented only here.

0.1.0

Initial release.

• Core: triggers an output after a configured number of messages arrive within a configured time window. Count limit and window duration configurable in the editor and overridable at runtime (setcountlimit / setwindow).
• Two window modes: fixed (one shared clock anchored to the first message of a cycle) and sliding (each message ages out individually; the count decays stepwise, with an event only on decay to zero).
• Three outputs: Trigger (genuine triggers only), Query (state snapshots — requested or via Heartbeat), Events (everything, including ignored: true copies of every blocked or redundant attempt).
• Event envelope on every output message — timerEvent, timerState, count, countLimit, windowMode, windowDuration, windowRemaining, cooldownRemaining, ignoredCount, lastIgnoredTime, disabled, ignored, source — with property names shared with the sibling node-red-contrib-timer-events node.
• Commands (case-insensitive): stop, reset, query, disable, enable, setcountlimit, setwindow.
• Cooldown: optional timed block on counting after each Trigger; 0 disables (simple-reset behavior). Cancellable only by stop.
• Heartbeat: optional fixed-interval state snapshots on the Query output while a cycle is active, continuing through cooldown.
• Status reporting: optional counting-down status label under the node (never / every second / adaptive minute-then-second cadence), in HH:MM:SS or raw seconds/minutes/hours.
• Persistence: optional resume across deploys and restarts — sliding timestamps pruned against the wall clock, fixed windows recalculated from their anchor (with the 3–8 second anti-flood randomization when nearly expired), cooldowns resumed, and idle context (disabled flag, runtime overrides) restored. A restore never fires the Trigger and never emits events.
• Packaged examples: four importable flows (basic-usage, sliding-window, cooldown, runtime-commands), each with a walkthrough page in this wiki.
• Testing: a 90-assertion test harness ships in the repository (test-scripts/test-harness.js), wired to npm test and run automatically before every publish.

Requires Node-RED 2.0.0+ and Node.js 12.0.0+.