Recommended configuration for a Car-Sharing solution

Hi Teltonika Support Team,

I am currently configuring a Teltonika device for a car-sharing platform.

Our main requirements are:

  1. Instant remote response: Users need to unlock the vehicle instantly from our mobile app via server commands (TCP / MQTT only, no SMS).

  2. Power management: The device must minimize power consumption when the vehicle is parked to prevent draining the vehicle’s battery.

Based on your experience and best practices, what is the recommended configuration for a car-sharing use case without SMS?

Specifically:

  • Which Sleep Mode should we use (GPS Sleep or another) to ensure the server socket remains active while still saving power?

  • What are the optimal connection maintenance settings (Ping Timeout, heartbeat frequency, data sockets) to keep the TCP/MQTT socket continuously open without unnecessary power drain?

Thank you in advance for your technical guidance and recommendations.

Best regards,

Dear Robert,

Good day!

Thank you for contacting us.

For a car-sharing solution requiring instant TCP/MQTT commands, the device needs to keep the cellular connection active to receive server commands at any time.

We recommend using GPS Sleep mode, as it reduces power consumption by disabling GPS while maintaining communication with the server. Deeper sleep modes may disconnect the cellular connection and delay remote command execution.

For TCP/MQTT connection maintenance, the default settings can be used as a starting point. The Ping Timeout and heartbeat intervals should be adjusted based on your server and network requirements to maintain the connection without unnecessary data usage.

Please note that there is always a balance between power saving and instant response. Keeping the connection active will consume more power compared to deeper sleep modes.

Kind regards,
Amalnath