-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting & FAQ
Common issues and questions. If your problem isn't here, check Settings → System → Logs for suunto_app and open an issue.
"Login was rejected." Wrong email/password, or two-factor authentication on the account is blocking the API login. Double-check the credentials in the Suunto app; if 2FA is the cause, that's a known limitation of this unofficial login path.
"Could not reach the Suunto/Sports Tracker servers." Network/DNS problem from your HA host, or the backend is temporarily down. Retry later.
"Reauthentication required" keeps appearing. The server invalidated your session token. Enter your password once (reauth) to get a fresh token. If it recurs immediately, the account may be rejecting logins (2FA / rate limiting / a Suunto app update that rotated keys - see Architecture).
Do I get an email every time it fetches data? No. Suunto emails on login only. The integration caches the token and reuses it across restarts, so you should see a login email only at first setup and on reauth - not during normal polling. See Configuration.
Light sleep / REM / SpO₂ / HRV show unknown.
Your watch model doesn't report those fields. That's expected - the sensors exist but stay empty.
Heart rate history has gaps / the live sensor jumps.
The live current_hr sensor only records the value present at poll time and cannot backfill. Use the suunto_app:hr statistic for a gap-free intraday curve with workout peaks. See Long-term Statistics.
My HR/energy numbers look off by a factor. Units are tricky on the backend (HR in Hz in some streams, calories vs kcal). The integration already converts them; if you're reading raw values in templates, see the unit table in Data & Units.
A weekly count dipped by one then recovered. The Sports Tracker workouts list is occasionally eventually-consistent - a workout can vanish for one cycle. The integration caches workouts with a 24-hour grace window to absorb this; a single flaky fetch shouldn't move the sensors. See Data & Units → eventual consistency.
A workout shows as Activity 81 (a number).
That activityId isn't in the curated name map yet. See Activity Types - open an issue with the id and what the app calls it.
Stride length is empty for my ride. By design - stride length is only computed for foot-based activities. See Activity Types.
The long-term statistics aren't appearing.
They are external statistics, not entities - find them in a Statistics Graph card or Developer Tools → Statistics, searching suunto_app:. They also require the Recorder integration (enabled by default). Give it a history cycle (default 60 min) to import.
A late watch sync - will the missed hours show up? Yes, if the sync lands within the ~5-day backfill window. Older than that won't backfill. See Long-term Statistics.
That is the fix, not a regression. The 24/7 stream sends energyConsumption in joules; the integration previously read it as calories, inflating every figure by 4.19x. It is active energy (above resting), so it is meant to sit well below your total daily burn - idle intervals are exactly 0.
Existing history is not rewritten, so expect a step in the graph. You can clear the old rows in Developer Tools > Statistics. See Data & Units.
Intended. Altitude comes from the barometer/GPS, and an indoor session has neither - the API sends a 0/0 pair. Reporting 0 m would claim you trained at sea level, so the sensors stay empty instead.
Also intended - it is only computed for foot-based activities. For cycling, cadence is pedal RPM, so a "stride" has no meaning. See Activity Types.
The integration doesn't appear in "Add Integration".
Confirm the files are at custom_components/suunto_app/ and that you restarted HA after installing. Check the logs for load errors. See Installation.
HACS shows "icon not available" for this repo. A known HACS-frontend issue unrelated to this integration; the icon shows fine on the integration page in HA. Cosmetic only.
Which Home Assistant version do I need? 2024.12.0 or newer. See Installation.
Is this official / will it keep working? No, it's unofficial and talks to a private API - a Suunto app update can break it at any time. See Privacy & Disclaimer.
Can I track someone else's account? Use it only for your own account/data. See Privacy & Disclaimer.
How often should I poll? Leave the history interval at ~60 min; the backfill makes faster polling pointless and it's an unofficial API. Live can be 5-15 min. See Configuration.
ha-suunto - Unofficial Suunto integration for Home Assistant - Not affiliated with Suunto / Amer Sports / Sports-Tracker - Report an issue
Getting started
Reference
Build with it
Under the hood
Help