Edited by EishiFUN
Customer would like to use the driver feedback notification option for their speeding rule. For the 10 beep option. The device will beep 10 times once the driver breaks the speed rule. If after the 10 beeps the driver is still breaking the speeding rule, will it beep 10 times again?
You need to be logged in to reply to this post and participate in the Geotab Community discussions.
Hey @aaspa-1524 ,
Thank you for asking your question in our community. This comes up fairly often with the driver feedback feature. Let me clarify how the beeping actually works.
The beep sequence fires once per exception event onset — it does not repeat.
When the speeding rule triggers, the device plays the 10 beeps once at the start of the violation. If the driver is still speeding after those 10 beeps complete, the device goes silent — it does not loop back and beep again while the same violation is ongoing. The 10 beeps is the total feedback for that exception event.
A second beep sequence would only occur if the exception event closes and reopens — meaning the driver briefly came back within the speed limit (ending the active exception) and then sped again (starting a new one).
This is a known limitation. Continuous or repeating beep behavior for sustained violations is something customers have requested, and it's on Geotab's radar as a future enhancement. It isn't currently available.
Workaround if you need more persistent alerting
If the goal is to keep reminding the driver throughout a sustained violation, one approach is to design the rule with a very short evaluation window so the exception closes and reopens more frequently. For example, instead of triggering once the vehicle is speeding, you can structure it so the exception fires in short bursts — though this does increase notification volume and has trade-offs for reporting.
One more thing worth knowing
There are actually two separate driver feedback systems in MyGeotab:
1. Rule-based driver feedback (configured under Rules > Notifications > Add Driver Feedback) — this is what you're describing. It relies on the server detecting the exception and sending a command to the device, so there's a small latency involved. If the device is offline or the data is delayed, the beep may be suppressed to avoid confusing the driver with a delayed alert.
2. Firmware-embedded thresholds (configured on the vehicle's Asset page under the Device & Settings tab) — this is evaluated directly on the device in real time without needing a server round-trip. It's more reliable in areas with poor coverage and can be more responsive for speed-based feedback. this option also gives you the option to start beeping at a certain speed and then stop once they come back down. So if you just want to make sure you beep when they go over 80 MPH it will just keep beeping at them until they slow down.
If reliability of the beep during live speeding events is a concern, it's worth checking whether the firmware-embedded option meets the customer's needs for their specific setup.
Hope that clears things up! Let us know if you have any other questions. We are here to help.
Have a great day!
Eishi FUN
Hey @aaspa-1524 ,
Thank you for asking your question in our community. This comes up fairly often with the driver feedback feature. Let me clarify how the beeping actually works.
The beep sequence fires once per exception event onset — it does not repeat.
When the speeding rule triggers, the device plays the 10 beeps once at the start of the violation. If the driver is still speeding after those 10 beeps complete, the device goes silent — it does not loop back and beep again while the same violation is ongoing. The 10 beeps is the total feedback for that exception event.
A second beep sequence would only occur if the exception event closes and reopens — meaning the driver briefly came back within the speed limit (ending the active exception) and then sped again (starting a new one).
This is a known limitation. Continuous or repeating beep behavior for sustained violations is something customers have requested, and it's on Geotab's radar as a future enhancement. It isn't currently available.
Workaround if you need more persistent alerting
If the goal is to keep reminding the driver throughout a sustained violation, one approach is to design the rule with a very short evaluation window so the exception closes and reopens more frequently. For example, instead of triggering once the vehicle is speeding, you can structure it so the exception fires in short bursts — though this does increase notification volume and has trade-offs for reporting.
One more thing worth knowing
There are actually two separate driver feedback systems in MyGeotab:
1. Rule-based driver feedback (configured under Rules > Notifications > Add Driver Feedback) — this is what you're describing. It relies on the server detecting the exception and sending a command to the device, so there's a small latency involved. If the device is offline or the data is delayed, the beep may be suppressed to avoid confusing the driver with a delayed alert.
2. Firmware-embedded thresholds (configured on the vehicle's Asset page under the Device & Settings tab) — this is evaluated directly on the device in real time without needing a server round-trip. It's more reliable in areas with poor coverage and can be more responsive for speed-based feedback. this option also gives you the option to start beeping at a certain speed and then stop once they come back down. So if you just want to make sure you beep when they go over 80 MPH it will just keep beeping at them until they slow down.
If reliability of the beep during live speeding events is a concern, it's worth checking whether the firmware-embedded option meets the customer's needs for their specific setup.
Hope that clears things up! Let us know if you have any other questions. We are here to help.
Have a great day!
Eishi FUN