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 sensitivity on 530

Initial ride with an Edge 530 (KEdge combo mount with Niterider light) and the incident detection went off at literally every stop light, road crossing or any time I came to a stop regardless of slowing rate. Only time it didn't go off was for a panic stop. Anyone have similar before I reach out to support? It can't be this sensitive and be correct.

520 Plus on same bike with the light has never gone off at a stop; in 2 odd years with the 520 I think the detector has gone off maybe 3 times.

0 Tisztul_A_Visztula over 2 years ago in reply to Penguin

I dont dare to switch it off in spite of having the same oversensitivity. Any fast braking means an incident detection for my Edge 530, and I am not speaking about panic braking, just normal, solid ones.

Last time I reached a top of a hill with my recumbent, my speed was very slow and before really accelerating I decided to stop. So even if my braking to stop was relatively sudden, my speed at the time of braking was like 15 km/h.

0 ewarnerusa over 1 year ago

My 530 now gives me a false detection of an incident on nearly every mountain bike ride. Usually after a sudden braking or jarring point in the ride along with large deceleration. I can see how these changes in movement could make the device suspect an incident, but it's like it is too quick to trigger an incident detection alert rather than acknowledging that I'm still riding after it occurred. Then I have to stop and go through the task of cancelling the alert, plus it logs it on the GC phone app in such a way that the incident won't go away from notifications without a force close. I feel like the algorithm was changed after last FW update, I recall occasional false alerts before but not on practically every mountain bike ride like it is now.