Tune the automation stack to the club's hardware reality
Default values work for most clubs; this page is for the times they don't. Anything settable in code is settable here so an operator never has to call an engineer to change a 30-second timeout.
- Timing — lead times — minutes before booking start to power on (default 10), minutes before to wake monitor (5), minutes before to launch sim (1). Operator overrides for slow-booting hardware.
- Timing — idle shutdown — minutes after session end to auto power-off (default 30). Set to 0 to keep bays warm; set to 5 for aggressive savings.
- Provider — power — TP-Link Kasa / Shelly / MQTT / Belkin Wemo / custom HTTP. Per-provider auth credentials + endpoint.
- Provider — sim software — Trackman / Foresight / GSPro / E6 Connect. Vendor account credentials. Default launch profile per provider.
- Retries + timeouts — max retries per command, backoff strategy, hard timeout (escalates to operator alert).
- Fallback behavior — what happens when an automation fails: notify operator only / notify customer + operator / mark booking as needs-manual-setup / proactively comp the session.
- Per-bay override — any setting can be customized for a specific bay (e.g. Bay 4 needs +20s power-on lead time).
- Alerting — channels (operator dashboard / SMS / email), severity thresholds, quiet hours.
- Test before saving — runs the diagnostics sheet with the new config in dry-run mode; shows what would have happened.
Backend wiring pending. PATCH /operator/automations/config in the live app; changes effective immediately unless marked future-dated.