h4 - Wireless Reset Button

The h4 traffic system keeps a loop counter in memory that the Router, Merge, and Cop nodes use to decide "first run" vs "loop run." Normally you reset that counter with the restart_on_true / restart toggle on each traffic node. H4_WirelessResetButton does it without touching those nodes at all: it's a single checkbox that, when switched on, broadcasts a reset flag through h4's shared memory - no wires involved.

It's a deliberately small node. One input, one output, one job.

How it works

Toggle trigger_reset ON and the node writes a flag into h4's internal "orbit" storage - a little key-value memory space the pack's nodes share. It returns a status string to tell you what it did. In the code:

• Flag set → returns "✅ RESET SENT"
• Idle → returns "Idle..."

Who picks up that flag? The tooltip says it's "wireless to H4_LoopIncrementer" - that's the node that bumps the counter on its own, separate from the traffic nodes. So the intended pairing is: H4_LoopIncrementer to advance the count, H4_WirelessResetButton to zero it, both talking through shared memory instead of long wires dragged back across a sprawling graph.

That's the honest scope here, and it's worth knowing: if your loop is built on TrafficRouter/TrafficMerge/TrafficCop (the more common setup), the reset flag from this button is not what zeroes their count - their reset is the restart / restart_on_true boolean on the node itself. This button is the companion for the LoopIncrementer branch of the h4 family, and for workflows where you want one visible "reset" control that doesn't require routing a wire to wherever the counter lives.

The output, reset_status (STRING), is mostly for your own sanity - you can wire it to a display or just read it. There's no reset state on the output; it's a report of the last press, not a persistent signal.

Installing h4_Live

One install gets the whole pack. ComfyUI Manager: search h4_Live, install, restart. Or by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/m3rr/h4_Live

Restart, no model downloads, no extra dependencies. The pack declares zero pip requirements beyond ComfyUI's own.

Common issues

• It's a pulse, not a persistent state. The flag is written when you toggle ON and stays in h4's shared memory until a LoopIncrementer with wireless_reset switched on consumes it - that node clears the flag when it sees it. So flip it ON, run, and let the incrementer eat it; if you toggle it back OFF first, the pending flag still fires on the next run. A small quirk, but it's caught people out.
• Expect it to feel wireless but not magic. Because it's a global in-memory flag, anything in the h4 family can read it. That's convenient and also means one reset button affects every h4 counter in the workflow, not just "your" loop. Same shared-state caveat as the rest of the traffic family: one loop per workflow unless you're careful.
• ComfyUI Desktop Edition. The README is upfront that CDE's sandboxed renderer can disable the fancier h4 UI flourishes. A plain toggle like this usually survives, but if a node's widgets look degraded, that's the known cause.