Skip to main content

Improving Unauthorized Device removal Alert in MyGeotab

bbnk-1329
Original Poster

I have a customer (1000+ vehicles) questioning the validity of the Unauthorized Device Removal rule. The reason being, when they look into Geotab the device is almost always working and reporting location. We know as resellers, this rule really is just a device lost voltage alert but are wondering if they can get the alert instead if the device loses power for more than 5 minutes in hopes this will cut down on the noise.

 

I dont want to do a device report becuase that looks at Cell Communication/GPS downloading data. They specifically want a report that shows if the device is down for more than 5 minutes with no power to it.

 

I took the logic from the default rule and applied a duration to it. I am just wondering if anyone knows if this will work:

 

Duration of Active Fault "Telematics device fault: Telematics device is unplugged" > 5m 

 

I checked the exceptions today and it didn't trigger anything for the past 7 days and I dont really know a better way to verify if that is valid or not.

Join the conversation

You need to be logged in to reply to this post and participate in the Geotab Community discussions.

Top Answers

@bbnk-1329​ I think the issue you're running into is that the Fault for being unplugged is just an instant trigger so it doesn't have a duration. If you want to add a duration you'll want to use the Device Power Change measurement instead. I think the rule below should work for what you're looking for.

DurationLongerThan[time=5m]( IsValueLessThan[value=1]( FilterStatusDataByDiagnostic[diagnostic=DiagnosticDevicePowerChangeId] ) )

 

5 Replies

@bbnk-1329​ I think the issue you're running into is that the Fault for being unplugged is just an instant trigger so it doesn't have a duration. If you want to add a duration you'll want to use the Device Power Change measurement instead. I think the rule below should work for what you're looking for.

DurationLongerThan[time=5m]( IsValueLessThan[value=1]( FilterStatusDataByDiagnostic[diagnostic=DiagnosticDevicePowerChangeId] ) )

 

bbnk-1329
Original Poster

Thanks Tony. This is very helpful! hopefully meet you at Connect!

 

Hi @bbnk-1329​ 

 

In addition to what tony says, you could also use the low battery rule, so you can rule out that the equipment was disconnected and that the alert is triggered because the vehicle's battery is supplying less than the base voltage for the GO to operate, which I believe is 9 volts, that will certainly help to improve the accuracy of the rule and avoid false positives.

bbnk-1329
Original Poster

@TonyFC-1053​ do you have any recommendations for tracking this in real time? I had a customer where the driver removed the device on purpose to not be tracked, Is there a rule that looks at lets say no communication > 1 hour it will flag an exception?

@bbnk-1329​ There isn't really a way of doing it by rules, as far as I know. For notifying people about assets that aren't reporting, we usually use a modified Watchdog Report that's set up to only send if the last communication date is > 24 hours from the run date. It does get pretty messy for large fleets and fleets that use kill switches or battery isolators, unfortunately. Otherwise the options are pretty limited for unplug notifications.

Still have questions?