Bay automation configuration

Timing, retries, provider settings, fallback behavior. Each setting cascades to every bay unless an override below says otherwise.

Cancel
Club-wide defaults · per-bay overrides below
Set the timing, providers, retries, and fallback behavior for every bay
Default values work for most clubs. Tune anything here without paging an engineer to change a timeout. Runbook documents the live values: read the runbook ›
Saved Last saved Jun 2 8:14 PM by Mike Smith · 3 changes today ›
Dry-run before saving Test a config change against the next 3 scheduled bookings to see what would have fired and whether anything would have failed. Catches typos before they cost a session.
Dry-run config →

1 · Timing

Click defaults › to reset

Lead times set how far in advance each command fires. Idle shutdown controls how long bays stay warm after a session ends.

min before start
Slow-booting hardware? Bump to 15.
min before start
HDMI handshake can be slow on cold start.
min before start
License-server handshake takes ~30s on cold launch.
min idle
0 = always on (keep bays warm). 5 = aggressive savings.

2 · Power provider

Per-bay overrides at §6

Which smart-plug provider controls bay power. Cloud auth credentials per-provider; framework is pluggable.

Last rotated May 18 · rotate ›

3 · Simulator software provider

Per-bay overrides at §6

Which sim software the lifecycle launches on each bay. Per-bay overrides allow mixed-vendor clubs.

What sim opens to when no customer preference set.

4 · Retries + timeouts

Apply to all commands

How many times the automation framework retries before escalating, and how long each command can take before timing out.

attempts
sec
After this, escalates to operator alert + falls through to behavior at §5.

5 · Fallback behavior

Fires when retries exhausted

What happens when automation fails. Affects customer experience — choose carefully.

6 · Per-bay overrides

2 active · cascades from defaults above

When a specific bay needs different timing or a different provider than the club-wide default. Most common: a slower bay PC that needs more lead time.

  • Bay 4
    Power-on lead time: 15 min (+5 from default) Older PC · cold-boots in ~6 min · added 2025-04-12 by Mike Smith
    Edit · remove
  • Bay 2
    Sim provider: Foresight FSX (overrides Trackman default) Mixed-vendor club · Bay 2 is the FSX bay · added 2025-03-01 by Mike Smith
    Edit · remove

7 · Alerting

Operator-facing only

How the operator gets paged when automation fails. Customer-facing notifications live under §5 fallback behavior.

How automation config works
Lives on club_automation_config (one row per club) + bay_automation_override (zero-or-more per bay, sparse). The framework loads club defaults first, then layers per-bay overrides, then per-booking ad-hoc settings (rare). Provider selection is hot-swappable — see PROVIDER_REGISTRY in the bay-automation provider extension runbook for the recipe to add a new provider (Kasa, Shelly, MQTT, Wemo, custom HTTP). Saves audit-logged with diff + operator id. PATCH /operator/automations/config takes effect for the NEXT scheduled command; in-flight retries finish under the prior config.
No unsaved changes · Saved Jun 2 8:14 PM by Mike Smith
Dry-run