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

Sensors keep turning off

badbri
over 4 years ago

This began with the latest FW version 5.0 and I (and others) have commented on it other threads but this problem has persisted for me.

My ANT+/BT sensors continue to turn "off" on their own from day to day on my watch.  I'll turn them all on before starting an activity, then the next time I go to do another activity I noticed that my HR and footpod are not connecting and sure enough in the settings they have been turned "off" again.  

Only my Varia Radar for my bike and my Garmin Tempe stay "on" in settings...everything else including HRMs, footpods, power meters, speed/cadence etc get their status to "off" somehow between activities.

Anyone else seeing this?

  • 0 over 4 years ago in reply to badbri
    badbri said:
    When you access the Sensors menu and scroll down do your sensors all show as "searching..."?

    Yes, as the options is "Searching..." or "Off". Would be better if they would be "On" and "Off". If you wear the HR strap, it won't connect, it's not really searching, you need to select "Connect" and then it's really searching and it changes to "Connected".

  • 0 over 4 years ago

    so this is a bit of an off topic follow up question: i actually turn off all sensors manually (for example after indoor biking) because i feared it would impact battery life - is it not a problem to leave it at "searching" all the time?

  • 0 over 4 years ago in reply to DanielM

    According to some other posters above, it doesn't really impact battery life.

    My problem persists by the way.  There are certain sensors that I now ALWAYS have to turn "on" as they somehow turn themselves "off" after the activity is done.

  • 0 over 4 years ago in reply to DanielM

    The battery will be negligible (probably close to zero), and would not be an issue at all unless you are in an activity that can use those sensors.   

  • 0 over 4 years ago in reply to ekutter-dnu

    thanks for your answers!

  • 0 over 4 years ago in reply to badbri

    What sensors are you having this issue with?  It's been completely fixed for me for months.

  • 0 over 4 years ago in reply to ekutter-dnu

    There's a speed/cadence sensor that always always always I have to turn on.  My other sensors seem to do okay but I just checked now and there was a HR sensor and my Tempe had been turned off.  The Tempe was odd as I just used that one yesterday and it connected.

  • 0 over 4 years ago in reply to badbri

    Do you have any CIQ device apps you use regularly (full apps vs data fields vs widgtes)?  My original issues, and what was fixed, was with a CIQ widget that would play with Sensor states.  Seems like I've seen it with a full app as well, but has never been fully reproducible like with the widget.  Do you do any of your own CIQ development or just stuff from the store?

    probably stupid question, but I assume you are on the latest FW?

  • 0 over 4 years ago in reply to ekutter-dnu

    Yeah good questions.  Latest FW (well except for the 6.2 which hasn't gotten to me yet) and I only use CIQ datafields but I do use one in cycling, so maybe that is somehow the culprit.  Seems odd that a datafield could have that kind of power over a sensor state though.

    I also use the CIQ "battery" widget as well.  Again, can't imagine how that might have an impact.

  • 0 over 4 years ago in reply to badbri

    I'd be shocked if data fields could cause this as sensor management should be handled by the system.  But maybe there is a bug with that.  I'll try creating a data field that changes sensor settings.  Not sure it's even possible.

    The battery widget might.  The way sensors worked before the latest versions of CIQ was you call a function call setEnabledSensors(), passing in a list of sensors you wanted enabled. (that still works, they've just added a new interface that gives a bit more control as well).  All other sensors would be disabled.  My understanding of the problem that started this whole thread was that the sensors weren't properly being restored after exiting the widget.