• State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 1025 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HRM RUN not found when start a new run activity after a previous run activity with HRM Run and bluetooth headphone

Richy
over 5 years ago

Hi,

Watch : Fenix 5plus Saphire.Firmware 9.00. But was the same with previous FW Versions.

I start a run activity, connecting my HRM RUN, STRYD and a bluetooth headset and hear music via Amazon music during the run.

Next day when I start a run activity my HRM RUN ist not found by the watch. I have to reboot the watch and the HRM is directly connected.

This happens only when I heard music via headset. 

Any ideas how to fix it ?

Regards


Richard

  • 0 over 5 years ago

    I've had the exact same issue you are describing a few times lately. A hard reboot always fixes it immediately.

    Unfortunately I'm not aware of any permanent fix, I just wanted to confirm that you are not the only one experiencing this

  • Former Member
    +1 Former Member over 5 years ago

    I've had this happen one time recently. I thought my HRM-Run was finally dead as it's on its third watch.  Replaced the batteries and had about given up. Last ditch I rebooted the watch, and poof it's been fine since.  I assume it's a similar/same bug.

  • 0 over 5 years ago

    I can reproduce it as often I want.

    Start run, connect HRM Run, Stryd an headset.

    Hear music 1 Minute.

    Stop run. Disconnect all.

    Try to connect HRM Run agin. Device not found !

    Reboot watch . Device connected

  • Former Member
    0 Former Member over 5 years ago in reply to Richy

    That feels like my normal process.  I typically connect my HRM before going into run activity.  However I sometimes start music first, sometimes go into the activity first.  But it's only stopped connecting that one time.