Skip to main content

Is it possible to create a notification when a GO device loses communication?

RReye-10434
Original Poster

Hi everyone,

I'm trying to find a way to receive an alert whenever a GO device stops communicating with MyGeotab.

I'm not looking for an exception rule based on engine diagnostics or GPS data. Instead, I would like to know if there is a way to configure a notification, rule, or any other native feature that alerts us when a GO device loses communication with the database for a defined period of time (for example, 15 or 30 minutes).

I couldn't find an option for this in the Exception Rules.

Is this possible using native MyGeotab functionality, or would it require an Add-In, API, or another solution?

Thank you in advance!

Join the conversation

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

8 Replies

Hello,
In the assets section, there is a subsection that displays the total number of assets that are not communicating.
As for creating a notification or alert to detect when a GO device stops communicating, I am not sure if that is possible.

EishiFUN
Community Administrator

Hello @RReye-10434 ,

Thank you for asking your question in our community. My best suggestion is to use this free report from our marketplace: Watchdog by the minute .

Since there is no internal battery in the GO9 we cant get an exact message when a go device loses communication and if it was a connectivity issue the battery would not help here anyway. The report I shared is the best way to track potential issues with GO device connection that should be able to alert you to them pretty quickly. If you have any questions feel free to reach out we are here to help.

Have a good one!
Eishi FUN

I know the new Go10 has an internal battery and there's and IOX battery that can keep a Go device running even after being disconnected but otherwise there's no way an unpowered Go device can give you an exception that it has been unplugged.

RReye-10434
Original Poster

@HLui-1390 Thank you for your response. There is actually a way to achieve this by using a specific condition in a rule. I will share the configuration I'm using so you can review it.
However, I'd like to clarify that while this condition allows me to detect when the GO device has been unplugged, it does not detect when the device loses cellular signal or communication with the server. That is the part I'm still trying to solve. The condition is "Fault[diagnostic=DiagnosticDeviceHasBeenUnpluggedId]" I have named the rule 'battery disconnection'

@RReye-10434 Hi thanks for the comment, just like the device has been unplugged rule creates an exception after the device is reconnected any fault diagnostic will only work once the device is replugged in and powered up again.

RReye-10434
Original Poster

@HLui-1390 Thanks for the clarification. What I'm referring to is the power connection/disconnection, either for the vehicle battery or for the GO device itself. My goal is to detect when the device loses its power source and when power is restored, regardless of whether it's caused by the battery being disconnected or the device being unplugged. I understand that the exception is only generated once the device powers up again, but I'm specifically looking for diagnostics or events related to the loss and restoration of power.
For the reconnection, the condition would be the following "Fault[diagnostic=DiagnosticDeviceRestartedBecauseAllPowerWasRemovedId]"

Hi @RReye-10434
If you're looking to add duration to a rule for when a device loses power then you should use the Engine Measurement "Device power change (1. Powered)" for the condition. That will allow you to add a duration to the rule and the exception report will include the duration that the device lost power.
This is an example for a rule that will only trigger if the device has lost power for more than 10 minutes:


Still have questions?