v0.3.16 - Auxiliary switch repeat fix (stable)

What's New

This stable release finalises the complete fix for auxiliary switch repeat counts (switch_counts: N > 1) not working reliably. The issue was traced through six diagnostic/beta builds (v0.3.9 - v0.3.15) and all root causes are now resolved.

Fixed

Auxiliary switch repeat runs (switch_counts)

• Race condition on momentary switches - state-change listener is now registered before urn_on is called, so fast ON?OFF cycles are never missed.
• False immediate completion (idle-state bug) - completion tracking uses an unknown ? on ? done model. An entity that is already OFF at step start is treated as unknown, not done, so the done-signal only fires after an observed ON?OFF transition.
• Wrong completion signal - completion is now detected by watching machine_start_switch (the machine's own end-of-cycle signal) in addition to the aux switch itself; done fires only when both have completed an ON?OFF transition.
• Short inter-run settle pause - fixed 5-second pause between repeat activations ensures the machine is fully ready before the next urn_on command.

Changed

• Diagnostic [CRM] log statements that were added at WARNING level (v0.3.10) have been demoted to DEBUG level. They will no longer appear in default Home Assistant logs.

Upgrade Notes

If your recipe step has an explicit imeout: value that is shorter than the machine's actual cycle time, increase it to at least the longest expected single-run duration (e.g. imeout: 120). The default timeout is 120 seconds when no explicit value is set.