[joshualambert]

An OBSBOT Tiny 3 Lite configured to stay Awake still parked itself every 124–126 seconds. The guard woke it after each sleep, creating repeated visible off/on cycles. USB stayed active and ALSA capture stayed RUNNING: the independent firmware auto-sleep timer was set to 120 seconds, so holding a video control descriptor did not prevent the countdown.

Disable and verify the firmware timer whenever the guard requires Awake, including active Auto calls. Recheck during use to handle app/firmware resets. CLI Wake, wake-toggle and Reset disable the timer before waking. Explicit Sleep remains available. Status now reports auto_sleep_seconds; protocol documentation records the verified selector-6 TLV and readback offsets.

Validation on the affected Tiny 3 Lite:

• Read firmware timer 120 seconds, sent 0b 02 00 00, verified zero.
• Seven-minute observation: 1,638 status samples, zero sleeps, timer stayed zero; no reactive wake messages afterward.
• Installed new guard, injected a 600-second timer, verified full little-endian readback and automatic clearing without sleeping.
• 12 Rust tests, strict Clippy, formatting and release build passed.

This corrects the reactive-only power protection in #1. Timer mapping is hardware-verified for Tiny 3 Lite; other model mappings remain unverified. Disabling this timer does not disable separate firmware voice/gesture triggers.