feat: Gyro Controller — Active/Inactive state, auto-lock every 5s, in-place save, drop Send Lock button

[SlyWombat]

Summary

Rework the Gyro Controller configuration UX on the Setup tab. Switch to a state-driven enable/disable model — the orchestrator only attempts to bind a gyro to its assigned mover when the controller is explicitly Active. Remove the manual "Send Lock" button; replace with automatic re-bind attempts every 5 seconds while Active+disconnected.

Configuration page UX

When the operator opens a Gyro Controller's config on the Setup tab, the page presents:

• Enable switch at the top — toggles the controller between Active and Inactive. Default: Inactive for newly added gyros.
• Mover assignment — picker for the moving-head fixture this gyro drives.
• Save button — persists the current Enable + mover assignment.
• Unassign button — clears the mover assignment without leaving the page.
• Smoothing slider — current behaviour kept; persisted with the rest of the config.

Removed: the "Send Lock" button. The orchestrator handles lock packets automatically based on Active state (see below).

Save behaviour

After Save, the screen does not navigate away. It updates in place to show the current saved state (Active toggle position, assigned mover, smoothing value, plus a live status indicator showing whether the gyro is currently connected). The operator can adjust and re-save without re-navigating; the Enable switch / mover picker / smoothing / save / unassign buttons all stay on the page.

Active vs Inactive — orchestrator behaviour

Gyro state	Connected?	Lock packet behaviour	Connections accepted?
Active	No	Send lock every 5 seconds (until connection establishes or state changes to Inactive)	Yes
Active	Yes	No lock packets needed (connection already live)	Yes (re-connect if dropped)
Inactive	No	No lock packets sent	No
Inactive	Yes	Connection forcibly broken on transition to Inactive	No

Active + disconnected — auto re-bind every 5 s

The orchestrator's gyro-control loop checks each Active gyro every 5 seconds. If the gyro hasn't reported in (no recent UDP traffic, claim not registered server-side, or connection dropped), the orchestrator sends a fresh lock packet to the gyro's last-known IP/hostname (or broadcasts if unknown). The gyro firmware receives the lock, registers a claim against the assigned mover, and resumes orient streaming.

Inactive — no traffic, force-disconnect

Setting the gyro to Inactive must:

1. Stop the auto-lock-every-5s loop for that gyro immediately.
2. Refuse any incoming connection attempt from that gyro's device ID — the orchestrator returns a "device not active" response.
3. If a connection is already live, break it: release the mover-control claim, send a "release" packet to the gyro, and stop the engine pump's writes for that mover.

Acceptance

1. Newly added gyro defaults to Inactive. Orchestrator sends zero lock packets to it. Powering up the device produces no claim binding.
2. Operator toggles Enable to Active, picks a mover, clicks Save. Page does not navigate; updates in place to show saved state with Enable=Active.
3. Within 5 seconds of save, the orchestrator's lock-loop sends a lock packet. If the device is online, claim binds and the gyro starts streaming.
4. If the gyro is offline at save time, the orchestrator sends a lock every 5 seconds. Once the gyro powers up, it picks up the next lock and binds.
5. Operator toggles Enable to Inactive during an active connection. Orchestrator releases the claim, sends a release packet, gyro disconnects. Subsequent gyro power-cycles do NOT result in a claim — orchestrator refuses.
6. Operator changes the assigned mover via the picker → clicks Save → page stays put → next 5-second lock cycle binds the gyro to the new mover (releasing the old binding atomically).
7. The Send Lock button is gone from the config page.

Implementation notes

• The 5-second lock cadence sits in the orchestrator's main background loop (or a dedicated gyro-control thread). State change to Active starts the loop; state change to Inactive stops it.
• "Lock packet" is the existing UDP-port-4210 binding-handshake message the gyro firmware already understands; no protocol change. Just automation of when it's sent.
• The "device not active" refusal on Inactive is implemented at the orchestrator's UDP claim-handshake handler — same handler that processes incoming gyro connection requests.

Related

• fix: claim/start must park head at home before orient stream begins #800 — park-at-home behaviour applies to the gyro's assigned mover when the gyro disconnects (claim release event triggers home).
• Gyro: Settings page WiFi line should show IP address (and hostname/RSSI) when connected #778 — Gyro Settings page should show IP/hostname/RSSI when connected. The status indicator on this page (per UX above) overlaps; consider rendering connection state with the same data shape.
• Mover control: multi-fixture claim (one phone / gyro → N movers in cluster) #642 — multi-fixture claim (one gyro → N movers). Future feature; this issue's UX assumes one gyro = one mover for now, but the data model should be extensible (mover assignment as a list, not a scalar).
• SPA/Android: orientation indicator drifts independently of physical mover after calibrate #757 Issue A — phone + gyro coordinate-system unification. Separate work.

[SlyWombat]

Fixed in v1.7.41 (commit aa73a28 — orchestrator + SPA — and bundled into the v1.7.41 release).

Shipped:

• SPA gyro-config modal leads with an Active/Inactive toggle (Setup tab → Configure on a gyro row). Default Inactive for newly-added gyros.
• Send Lock button removed. _gyroSendLock deleted; orchestrator handles all lock packets automatically.
• Auto-lock every 5 s while Active + disconnected: _gyro_active_lock_loop daemon thread sends CMD_GYRO_CTRL(enabled=1, fps=20) to any Active gyro that hasn't reported orient data in the last 7 s. Cheap — skips Inactive and connected gyros immediately.
• Active → Inactive transition (_gyro_inactive_transition): releases the assigned mover's claim and sends CMD_GYRO_CTRL(enabled=0) to the gyro IP. Wired into PUT /api/fixtures/<fid> whenever gyroEnabled flips True→False.
• Inactive refusal: incoming CMD_GYRO_START is rejected with the same _send_gyro_claim_denied(ip) packet as a busy claim. Orient-driven auto-claim path was already gated.
• In-place save: _gyroConfigSave reloads _fixtures and re-opens the modal so the operator stays on the page with fresh saved state.
• Unassign button clears assignedMoverId without deleting the fixture record.

Constants: _GYRO_AUTO_LOCK_PERIOD_S = 5.0, _GYRO_DISCONNECTED_AFTER_S = 7.0.

Release: https://github.com/SlyWombat/SlyLED/releases/tag/v1.7.41

[SlyWombat]

Reopen — UX defects in v1 implementation

Functional behaviour is in place (Enable state, auto-lock-every-5s, in-place save, Send Lock button removed), but two UX details from the issue body were missed:

1. Switch styling — setup-ui.js:2680 uses a default HTML <input type="checkbox"> (a square checkbox). The issue spec says "Enable switch at the top — toggles the controller between Active and Inactive" — operator expects a CSS-styled toggle switch (sliding control). Replace the bare checkbox with a properly-styled switch widget. Even just CSS to make the <input type="checkbox"> render as a slider would suffice.

2. Position — switch is currently placed AFTER the Hostname/IP/Firmware/Device-Name/Mover-assignment fields. The issue spec says "top of the configure page." Move it above all of those — first thing the operator sees when opening the config modal.

Operator observation 2026-05-04: "I don't see the Active toggle, there is something that is a checkbox, but not really a switch at the top of the page like asked for."

These are the only two outstanding items; functional verification of the auto-lock loop / Inactive force-disconnect / in-place save is still possible once the visual is corrected.