VOLTRA Device Status
Read and summarize VOLTRA device state through Cortex. **Read-only — does not issue control commands.** Use when the user asks about connected devices, battery level, training mode, power/load state, cable zero position, saved devices, nearby devices, or wants an AI agent to inspect device readiness before taking action. To actually change a setting or start training, use `voltra-device-training`.
Use the local voltra command as the source of truth. Prefer JSON output for machine parsing, and avoid inferring live device state from cached local files unless the user explicitly asks about storage.
Workflow
- Confirm Cortex resolves:
where.exe voltra
voltra --version
voltra -v- Check the current session:
voltra status --json- If disconnected, list known devices and reconnect only when the user asked to inspect a device:
voltra list-known --json
voltra reconnect --jsonUse voltra disconnect --json only when the user asks to end the local Cortex session or switch devices.
- Refresh live device state before reporting readiness:
voltra refresh <scope> --json # e.g. all, epStatus
voltra status --json- For cable readiness, use the explicit command:
voltra check-cable-zero --jsonWhat To Report
Summarize only fields observed from Cortex output:
- Connection: connected/disconnected and device name/id.
- Battery: battery percent when present; say
unknownif not present. - Mode:
none,weightTraining,resistanceBand,damper,isokinetic,isometric,customCurve/Professional,rowing, orskiingwhen exposed. - Power/load:
powerEnabledtrue/false/unknown. - Cable: result of
check-cable-zerowhen relevant. - Dock/readiness: only report dock state when Cortex output exposes it directly or a guarded command returns a clear dock message.
- Twin topology: report the explicit
topology/pairing state when present; do not infer a confirmed pair from two independently connected devices. - Blocking state: repeat Cortex's explicit message when command output says blocked.
Guardrails
- Do not repeatedly retry a command that returns a clear blocked reason such as
place the device on the dock first,cable-not-zero, orworkout-mode-none. - Do not claim the device is on the dock unless Cortex exposes that state or a control command succeeds after its dock guard.
- Do not use
.voltrastorage as live battery, dock, or power state. Treat it as saved-device metadata only. - Do not treat battery below 20% as a Cortex blocker. Cortex does not enforce a low-battery training gate; report battery level as-is and only block if the device or Cortex explicitly rejects a command for low battery.
- For confirmed Twin topology, inspect the connected logical master with
voltra twin status --json. The--master <MASTER>selector is optional and is only needed to disambiguate multiple connected sessions or pairs. Pairing, unpairing, and Twin telemetry control belong tovoltra-device-training; do not infer Twin state from two ordinarystatusresponses. - If
voltrais not found, diagnose install/PATH before discussing device state. - If the device reports unexpected blocking states or connection issues that persist, load
voltra-cli-troubleshootingfor systematic diagnosis. - For first-time setup, use
voltra-getting-started. - For training control, use
voltra-device-training. - For workout data, use
voltra-workout-data.
Useful Commands
voltra scan --json
voltra list-known --json # alias: voltra devices
voltra connect <device-id-or-name> --json
voltra reconnect --json
voltra disconnect --json
voltra refresh <scope> --json # scopes include all, epStatus, trainingMode, resistanceBand, autoUnload, weightTraining, damper, isokinetic, cableLength, workoutState
voltra status --json
voltra check-cable-zero --json
voltra twin status --jsonVOLTRA User Live Training Stream
Use when a user wants live VOLTRA training telemetry for real-time analysis, dashboards, control-room displays, recording/replay, or custom pipelines. Subscribe through the daemon-owned NDJSON stream; do not use this for workout history or device control.
VOLTRA I Training Modes
VOLTRA I training modes knowledge base — device overview, all training modes (basic, advanced, cardio), including how VOLTRA Cardio Rowing/Skiing differs from Concept2 Rowing/Ski records, variable resistance features (eccentric, chains, inverse chains), drop sets, circuit training, session templates, twin mode, and Cortex command mapping. **Knowledge and explanation only** — does not issue commands. Use when the user asks what VOLTRA I is, what training modes are available, how VOLTRA and Concept2 cardio activities differ, how eccentric/chains/inverse chains work, what drop sets or circuits are, which mode suits a specific exercise, how session templates work, how twin mode pairing works, or wants a training recommendation. For actually operating the device or writing session/curve payloads, use `voltra-device-training`.