Maximum number of connected sensors limit reached?

You are my gadget Idol!

Ha ha, well I've been tracking my workouts with Garmin/GPS devices since (2012? when the Fenix 2 came out?, and Edge 810 in 2013?) so ~2 sensors a year at $20-30/sensor and careful hunting for used/refurbished power meters/trainers once every few years, and it's not so hard to max out over a decade!

ia_triguy said:

I tried to connect an In-Reach device to my F7x yesterday and received an error that I couldn't add any more sensors because a limit was reached. 

I had this happen to me too.  I didn't even know it was a thing.  Some useful reading:

https://support.garmin.com/en-US/?faq=pb7Bxcm3x48cQpGy2LfR4A

https://support.garmin.com/en-US/?faq=RpX8SeCLBd2K8sggJk4L56#:~:text=Up%20to%2020%20sensors%20can,if%20this%20limit%20is%20reached).

If you have the Runn, bin the footpods as they add very little to a F7 for anything but treadmill use. They're certainly less accurate than GPS. Bin the speed sensors, they give you nothing useful on a GPS watch, and the Power will usually give you cadence for the bike. It's been years since I've seen a Tempe do anything useful, as far as I know they removed the ability to record constant temperature from these a long time ago, leaving it as a useful "I wonder what the temp is right now" type device.

I have a bunch of old redundant sensors too, but you have to move with the times and most are no longer needed. I'd love if the Tempe worked the way it used to on the F2 and the way it does on the GPSMap devices!

I think there's still an argument for a calibrated footpod on road and track for instantaneous speed, even though I use GPS for distance, but maybe I should try unpairing it from my F7x and leaving it paired to a F6 for a few runs to compare pace/distance...

Same goes for a calibrated speed sensor on the bike- it should nearly always give more accurate instantaneous speeds and total distance, especially in mixed environments, and especially since I didn't pay the Sapphire tax got get Multi-GNSS (like the watches released 4 months later at a quarter the price- argh!!)...

And I find my Edge temperature sensors to frequently over-estimate the ambient temperature when mounted in the usual place on/out-front of the handlebars in any sunlight, and the wrist Fenix temperature sensors are similarly always inaccurate due to position on the body and in the compact electronics.  So a paired Tempe to the Fenix for runs/rides/hikes and a Tempe CIQ data field on the Edge devices (still disappointed that they removed that functionality from the x20/x30 yet now are adding back to the 1040) seems to give much more accurate temperature data when looking back at performance in various weather conditions. 

The problem is that a calibrated traditional footpod is wrong at any speed other than the one you calibrate. This is incredibly easy to demonstrate using a treadmill and a Runn. They are horrible things. I agree they update pace quickly, but then if you're staring at your watch long enough for this to matter you're running wrong and the sensor isn't helping you

Yes, a speed sensor on a bike is technically more accurate and responsive. No, this isn't actually useful in real life, especially when a power meter is fitted. The effort of using one, heck even the weight of the sensor outweighs any benefit in my opinion. Maybe a bit dogmatic, I would use one on a track, for instance, but I wouldn't fit one to a road bike these days, and certainly not a mountain bike.

Agree Fenix internal temperature is wrong, perhaps they did put the Tempe recording back in, I've not tried for a while. It certainly was the case that you could choose either recording temperature or using a Tempe, I think around F3 or F5 sort of time. If they fixed it then I take it back, originally Tempe was a great sensor.

I wanted to add on to this in case anyone is searching for this problem with Garmin Approach CT10 sensors not connecting - as I had an issue with the Fenix 7 refusing to pair the final golf club sensor of my CT10 despite pairing all other 13 flawlessly. This was the correct answer to solve the issue! I had to delete an old HR sensor and as soon as I did that it accepted my 14th club sensor. Before it would just hang on the watch face saying "Club sensor detected. Pairing"