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

Incident Detection too sensitive

Just used my new 520 Plus for the first time today. Sadly I've had to disable the incident detection feature; it's a good idea in theory but it's just way too sensitive. Twice coming home it triggered after I went over a bump just before stopping at a junction. A third time it triggered and I didn't notice for a while so my poor wife got a message to say I'd been in an incident, which gave her kittens.

Garmin, I think you need to allow for different sensitivity levels. It only really wants to go off if I've been involved in a big crash, not a minor bump. If it triggers and I carry on cycling then surely it should be bright enough to realise that there hasn't, in fact, been an incident.
  • My incident detection is also on. But hasn't gone off once. I am a MTB rider. So expected false reports. But have non.
    if it's so sensitive... should I be worried that mine isn't working.
    is there a way to test this?
  • Mine went off prematurely yesterday for the first time. It happened after an abrupt stop, I had to get across the highway and couldnt read what it was saying due to bright sunlight so my wife received the message.
  • Former Member
    0 Former Member over 5 years ago

    Same here. I got a false incident alarm while ice skating. My emergency contact called me right away, which I fortunately heard - not always the case while doing an activity. If I missed him calling, he would have started an unnecessary, elaborate  rescue operation. It was dark, in a snow storm and we were in the middle of a lake, far from civilization (completely fine though, even having fun). I would have really hated to see a rescue team wasting resources on trying to locate and “save” us, especially in these conditions.

    Rubbish function.

  • Same here - had to disable it because it goes off on every bike ride.  Maybe a sensitivity setting would help?