What I’m asking for is not lower accuracy during activities, but a different operating logic between activity mode and 24/7 tracking.
During activities:
Keep the current strict SNR threshold.
Prioritize signal quality and accuracy.
If conditions are sub-optimal, the user can rely on a chest strap anyway.
During 24/7 and night tracking:
Use a more conservative and tolerant algorithm.
Accept a slightly noisier signal instead of shutting the sensor down.
Apply stronger temporal smoothing and trend-based validation rather than instant SNR rejection.
Never fully disable the sensor unless there is a true hardware failure.
From a user perspective, this would solve the real problem:
In daily life the watch inevitably moves, rotates, and loosens.
Micro-motion, skin compression, sweat, temperature changes and external contacts are normal.
A minimal tattoo, as shown in the photo, is irrelevant from a physiological point of view and should not trigger a sensor shutdown.
Right now the behavior is binary:
Good conditions → excellent HR detection.
Slightly imperfect conditions → sensor off, sometimes for hours.
This is not acceptable for a device that is marketed with:
24/7 HR
Sleep tracking
Recovery metrics
Stress and resources monitoring
A more fault-tolerant logic would:
Preserve all activity tracking features.
Restore reliability of h24 metrics.
Reduce user frustration and false “no data” periods.
Align the device behavior with real-world usage.
From a technical standpoint, this looks like a software policy choice, not a hardware limitation.
Other manufacturers already differentiate thresholds and filters between:
Workout HR
Background HR
Sleep HR
I’m confident Suunto can do the same.
I’m not asking for perfection.
I’m asking for continuity instead of shutdown.
Best regards.
