Reference Updated March 10, 2026

Troubleshooting

Solutions to common issues with device syncing, scores, training plans, and the AI coach.

Device syncing

Data hasn’t synced

  1. Check your wearable app. Make sure your device has uploaded data to its cloud (Oura app, Garmin Connect, Whoop app). Omnio pulls from the cloud API, not directly from your device.
  2. Check account status. Go to Sources → Accounts. If the status shows “disconnected”, reconnect the account.
  3. Wait for the sync cycle. After the initial backfill, data syncs every ~2 hours. Oura with webhooks is faster (minutes).
  4. Force a sync. Click the sync button (⟳) on the Sources page to trigger an immediate sync.

Account shows “disconnected”

This means the OAuth token or session token has expired or been revoked.

  • Oura / Whoop — Click Reconnect to start a new OAuth flow.
  • Garmin — Re-enter your Garmin Connect credentials. If you have MFA enabled, you’ll need a fresh verification code.

Duplicate data

If you see doubled metrics, check whether you’ve connected the same device type twice (e.g. two Oura accounts). Go to Sources → Accounts and remove the duplicate.

BLE devices (Polar, Muse)

Device not appearing in scan

  1. Bluetooth must be enabled on your phone.
  2. Location permission is required on Android for BLE scanning (this is an Android OS requirement, not Omnio-specific).
  3. Polar H10 — Wet the electrode pads. The H10 only powers on when it detects skin contact.
  4. Polar Verity Sense — Press the side button to wake it. The LED should blink green.
  5. Muse S — Hold the power button for 2 seconds until you hear a tone. Disconnect from any other app (Muse app, system Bluetooth settings) first — the Muse only supports one active BLE connection at a time.

Connection drops frequently

  • Keep your phone within ~10 metres of the device. Walls and body position affect BLE signal strength.
  • On Android, Omnio requests high connection priority for the Muse to maintain stable high-throughput EEG streaming.
  • The app auto-reconnects with exponential backoff. If the device doesn’t reconnect after ~30 seconds, try manually reconnecting from Settings → Heart Rate Monitor.

Poor HR / HRV data from Polar

  • Chest strap (H10) — Re-wet the electrode pads. Dry electrodes cause poor contact and erratic readings. Consider electrode gel for extended sessions.
  • Optical sensor (Verity Sense) — Wear it snugly on the forearm. Avoid tattoos or very hairy areas. Too loose = signal dropout; too tight = restricted blood flow.

Poor EEG quality from Muse

  • Push hair aside so the forehead sensors (AF7, AF8) touch skin directly.
  • Ensure the ear sensors (TP9, TP10) sit snugly behind the earlobes.
  • Stay still during sessions — head movement corrupts EEG across all channels.
  • Check the Sensor Contact card: at least 3 of 4 channels should show green or yellow.

Forget and re-pair a device

Go to Settings → Heart Rate Monitor → tap Forget on the device, then scan again. For the Muse, power cycle the headband before re-scanning.

Sleep session not recording

  • Ensure you’ve started a sleep session from Settings → Heart Rate Monitor → Start Sleep Session.
  • The device must remain connected throughout the night. If the BLE link drops and can’t reconnect, data may be incomplete.
  • Sleep staging requires sufficient data quality. Check the sleep staging gate status — it shows which pipeline dependencies are met.

Scores

Score shows ”—”

Composite scores require a minimum confidence threshold (typically 30–40% of input weights must have data). Common causes:

  • Just connected — Give it 24 hours for enough data to accumulate.
  • Missing data source — Some scores need specific inputs. For example, the Nutrition score needs a food tracker. The Metabolic Health score needs uploaded bloodwork.
  • Stale data — If your wearable hasn’t synced in 48+ hours, scores may stop updating.

Score seems wrong

Each score tile shows which device sourced the data. If a score looks off:

  1. Check the individual metric values in the tile detail view.
  2. Compare against the source app (Oura, Garmin, Whoop).
  3. If there’s a genuine discrepancy, note the metric, date, and values from both Omnio and the source app, and email [email protected].

Readiness is low but I feel fine

The readiness score is biometric-based (HRV, RHR, sleep quality). It’s possible for biometrics to lag behind subjective feeling. If you consistently disagree with your readiness score, use the daily check-in to provide subjective readiness — this is weighted at 8% of the readiness score.

Training plans

”No plan” state

If the Training tab shows no plan:

  • If you have workout history — Omnio will show a detected schedule based on your last 60 days. Tap Confirm to create a plan.
  • If you’re new — Tap Create Plan and configure your goal, experience, and frequency.
  • Via AI coach — Ask the chat: “Create a hypertrophy plan for 4 days per week.”

Workout was adapted unexpectedly

Adaptations are triggered by your biometric state. The Adaptation Banner at the top of your workout shows why:

  • Readiness — Low readiness reduces volume or prescribes rest.
  • Nutrition — Caloric deficit reduces volume.
  • Recovery — Muscle group not recovered, session was swapped.
  • Load — ACWR above safe threshold.

Tap the banner for details.

Rotation seems stuck

The rotation advances when you complete a workout (tap Complete). If you skip without completing, the rotation stays at the same position. This is by design — so you don’t miss muscle groups.

AI chat

”Rate limit reached”

You’ve hit the daily message limit (30 messages) or tool call limit (90 calls). Limits reset at midnight in your timezone.

Responses seem generic

If the coach gives generic advice instead of data-specific answers:

  1. Be specific. Ask about concrete metrics, dates, or comparisons.
  2. Check that data exists. The coach can only query data that has been synced. If you ask about nutrition but haven’t connected a food tracker, it has nothing to query.
  3. Ask follow-ups. “Why?” and “Show me the data” prompt deeper tool use.

Chat is slow

AI responses stream in real-time but depend on the AI provider’s response time. During peak hours, responses may take 5–10 seconds to start. If a response seems stuck, click the stop button and try again.

Tool call failed

Occasionally a tool call may fail (e.g. if VictoriaMetrics is temporarily unavailable). The coach will mention this in its response. Try asking again in a few minutes.

Nutrition

MFP cookies expire periodically (typically every few weeks). When this happens:

  1. Go to Sources → Accounts.
  2. Click Reconnect on your MFP account.
  3. Follow the instructions to export a fresh cookie from your browser.

CSV import rejected

Common causes:

  • Missing required columns — Nutrition CSV needs at least date and calories. Strength CSV needs date, exercise, sets, reps, weight_kg.
  • Date format — Use YYYY-MM-DD (e.g. 2026-03-01).
  • Encoding — Save as UTF-8. Some spreadsheet apps export in non-standard encodings.
  • Empty rows — Remove any blank rows at the end of the file.

Account & general

Forgot password

Use the password reset flow on the login page. You’ll receive a reset link via email.

Change email or timezone

Contact [email protected]. Self-service profile editing is planned for general availability.

Delete account

Email [email protected] to request full account deletion. This removes all data including metrics, training plans, chat history, and credentials.

Still stuck?

Email [email protected] with:

  • What you were doing
  • What you expected
  • What actually happened
  • Screenshots if helpful
  • Your browser or device info

We typically respond within 24 hours.

← All docs Something wrong? Let us know