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

Light network formed when accessing widgets

Hi,

I use RTL510 and Bontrager ION RT front light and everytime

1) I hit start button, it forms light network.

2) I access widget glances it forms light network.

I have my bike in the apartment so you understand how this is annoying.

Anyone else experiencing this? (I don't turn off the lights using the button on the lights, I have set it up so that It turns off automatically after I save the activity).

Thanks.

BTW: where should I report this bug? I didn't find any useful information. (using official firmware so probably emailing beta program email is not the right place)

  • In widgets section, my watch connects to my Tempe sensor too. For me, that's good but for other use cases such as yours, it may be irritating.

  • Not sure if it is a bug, but I understand your annoyance.

    I think there was a change of software structure between Fenix 6 and Fenix 7. Now there are no widgets anymore in Fenix 7, also you see in IQ store. It is all now activity profiles, you find widgets from IQ store in the activity profile.

    I guess once you go to widgets, it is like starting an activity and it is looking for ANT devices nearby.

    When I have a HR sensor near by that I just removed or I still have on while using an EDGE and I go to widgets, it connects to the HR sensor and deactivates OHR.

    I never had that in the Fenix 6. But as said, I fear this is actually per design rather than a bug.

    Hopefully there is a solution still.

    Best regards, 
    J

  • Well, no. I work in Software Quality Engineering, and "per design" is still a bug if it causes unexpected and wrong behavior. There can be a simple fix in code either to not to connect certain sensors until I start an activity (bike lights, power meter, others?) or even an option for each connected device to choose when to connect it.

    Thanks both for confirmation that this is not something just I'm experiencing.

  • think there was a change of software structure between Fenix 6 and Fenix 7

    Definitely noticed the change on the f7 from day one.  No other watch I've owned (Instinct 1/2, FR945, f6) have located sensors in the Widget/Glance view (or at least alerted me).  Every time I view my glances in my family room, my Tempe and UT800/RTL515 connect.  Seems to be no good reason.  Annoying.

  • Fine that you work in SW QE. You should not buy a Garmin then, that is not their strength;-)

    The F7/E2 are CIQ 5 devices. Those behave like pilzj described it. It is one of the main changes from CIQ 4 to 5. As it is now, it is expected behavior because the watches start to scan for Sensors as soon as they get themselves ready to start an app (pushing the start button) or even when an app is running (looking at a widget wich is now part of an app). 

    i understand why it is annoying, but I would also say that in the case of Tempe and HRMs it’s quite useful. 

  • in the case of Tempe and HRMs it’s quite useful

    I can see how this might be useful if one is accessing the Temperature glance and to a lesser extent the HR glance.  But if neither is in the glance list, it is just an additional alert for no purpose.

  • Yes, experiencing the same issue, reported it to the Garmin Outdoor Quality Team ([email protected]) as I'm running 8.16.

    I think you can report bugs you find to the same bunch even if you are running an official firmware.

  • Updated:

    - We now have a Public Beta Software program. For those interested, see here: Beta Software Program.

  • I find that my Fenix 7 turns on the See Sense Icon2 taillight I have on my bike. If I am going for a run, it is no use to me and in fact if I leave through the front door I don't see that the light is on in the garage, and so the charge in the light runs down. Today, I went to turn it on to go for a bike ride, and found that it would not turn on, because it was completely discharged.

    This feature is a bug. Please remedy the situation.

    I am now going to charge my Icon2 taillight.