Hi We currently consume via API only your HEARTBEAT data element for all our GO09 devices without backup battery to monitor possible PID disconnections or loss of communications. Looking at the data, we basically receive 2 states CONNECTED/DISCONNECTED. Can you please confirm how long does GEOTAB's cloud infrastructure logic behind the HEARTBEAT data element waits before sending a DISCONNECTED state status message? I am aware of the information you have in your documentation about "Heartbeat Frequency". That one I understand it. But what I would like to know is ALL the conditions, times and logic your system follows before sending a DISCONNECTED message via API for a specific PID. Thanks.

How long does GEOTAB's cloud infrastructure logic behind the HEARTBEAT data element waits before sending a DISCONNECTED status message via API for GO09 devices without backup battery?

page-user page-user-parmend3-parmend3-8148 template-account-profile page-status-200 theme-harmony user-guest

Company

Title

Hi We currently consume via API only your HEARTBEAT data element for all our GO09 devices without backup battery to monitor possible PID disconnections or loss of communications. Looking at the data, we basically receive 2 states CONNECTED/DISCONNECTED. Can you please confirm how long does GEOTAB's cloud infrastructure logic behind the HEARTBEAT data element waits before sending a DISCONNECTED state status message? I am aware of the information you have in your documentation about "Heartbeat Frequency". That one I understand it. But what I would like to know is ALL the conditions, times and logic your system follows before sending a DISCONNECTED message via API for a specific PID. Thanks.

Senaste aktivitet

How long does GEOTAB's cloud infrastructure logic behind the HEARTBEAT data element waits before sending a DISCONNECTED status message via API for GO09 devices without backup battery?