Multiple sensor pairing doesn't work as expected
-
Switching from one HR sensor to another glitches every single time
Let’s say I go for a run and I bring another sensor - not the same I used on a previous run. Why? Because I rotate between Suunto HR chest sensor for shorter runs and Coros armband HR sensor for long runs.
So, first of all, the watch doesn’t automatically try to connect to another HR sensor and instead just uses the built-in optical HR sensor. Not the expected outcome, but OK - let’s go to Exercise Options --> Sensor Data menu and manually connect to the new sensor. That works and the new sensor successfully connects. However when I exit the Exercise Options menu, the watch still doesn’t use the external sensor and remains locked to the built-in sensor! Switching activity type and back or doing any other changes in activity options didn’t help either.
The only workaround that sometimes works is to exit the activity start screen and go back to watchface, and try to restart the activity again. This seems like a clear software bug to me. Please report it!
-
@sky-runner Hi, what works for me is to disable the OHR in the menu. Yes, it’s still a workaround but the ohr doesn’t work for me anyway. I am not sure if this is the wanted behavior that the OHR has always the priority. I guess that if you use external sensors than you can use this solution.
-
@sky-runner Same behavior here
-
@jjpaz can confirm.
-
@sky-runner no need to report, this should already be fixed in next version
Watch: Suunto Vertical Ti
Blog: isazi's home
-
@isazi good to know
-
@isazi any news of next version ETA?
-
@isazi ghost sensors (without name, just two dashes “–” without details) will also be removed by firmware upgrade? I would like to prevent hard reset…
-
@dombo no idea, I have one on my watch, will not hard reset for that (it does not do anything weird), and just wait next update
-
@dombo I got rid of my ghost sensor via a hard reset. The problem that my power meter is detected as a speed sensor that does not transmit data remained. So I decided to downgrade to the prior version because support advised me to do so.
