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

SMO2 sensor no longer exists on Forerunner 965 (as native sensor) ??? Either need it back or need a 3rd data field allowed (like on Garmin 735 XT in the old days)

pyfacomprez

Asked this question in the Beta program, but I think it will interest also "non beta" users : 

Hi,

Long time Garmin Forerunner user... lately been using 955, then 965 because they were the only watches that allow me to use STRYD (with STRYD data field), CORE Sensor (with CORE data field) and MOXY (as a native sensor so no IQ data field required) combined which was absolutely great...

I stopped using Moxy and Core a bit during the winter/spring as I was not in a serious training block. Then when I came back to it,I found out on the screen that had SMO2 (again native field) as it was replaced by time. Then saw my Moxy would not connect... then after searching a bit I saw Moxy was not in my sensors anymore but I could not reconnect it as SMO2 sensors are not an option anymore !!! And the SMO2 native fields disappeared as well of course.

It means having the 965 for training and a 265s lighter and more compact watch for racing is completely stupid now because I can't connect the 3 sensors at the same time on either watch. Such a huge huge stepback.

There are only two options : 

1) can Garmin re-introduce SMO2 sensors and data fields as native sensors and fields ?

2) considering how powerful 965 is, is there any chance Garmin could allow 3 data fields from 3rd parties (IQ store) to be used ? It was possible a long time ago on Garmin 735 XT but has not been possible ever since (all watches after that were limited to 2 IQ data fields).

I really hope one of this two options is possible, if not, there won't be real reasons for me to justify Garmin 965 anymore, it's a nice watch... but a bit heavier and thicker than watches from the 255 and 265 ranges, so this move killed for me it's one big advantage.

Hope this feedback can be listened to. But really removing options along the way is something I have not seen before, and when removing an option that was the exact reason that created the purchasing decision for the higher end watch I find it's really unfair.

Thanks for reading.

Pierre

Ps : Garmin manuals website still showing muscle oxygen as native data fields for Garmin 965 here https://www8.garmin.com/manuals/webhelp/GUID-0221611A-992D-495E-8DED-1DD448F7A066/EN-US/GUID-73BCE454-042E-420D-96A4-9DBA46626CD4.html

  • 0

    I'm in the same exact situation.  I noticed that Muscle O2 is not in the listed supported wireless sensors for the 970, so it seems like it's not on their roadmap anymore.  If we aren't going to get the features of the new watches, it would be nice to at least keep the current features we purchased.

  • 0 in reply to RichardB

    Unfortunately, I don't have space for another data field since I'm using Stryd and Core sensors and their corresponding data fields. 

  • 0 in reply to rbf2000

    Can’t agree with you more. I replaced 265 with 965 for one and only one reason : native support of muscle oxygen whereas on 265 I had to use Stryd + Core on some days, Stryd + Moxy on some other days. Now with the update to 965 it does nothing more for my training than 265 or even 255 can do. I know there is map and a few other things on 965… but training for marathons mostly, the only advantage for what I was doing on 965 was native muscle oxygen, this was worth paying the extra. Now I’m completely fine going back to 255 music, it does all I need and I will get exactly the same functions I would get from 965 for my training (multi band gps, music, 2 iq fields). Garmin move here was very disrespectful of muscle oxygen users.

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries