Selecting a GPS tracking platform requires confirming two things: that it can correctly interpret device data and that device actions can be integrated with other processes. This ALTAGAMA GPS update expands compatibility with GV355CEU and GT06 GPS trackers, adds device commands through the API, and improves Help, renewals, application access, and WhatsApp support.
These improvements are useful to both a customer connecting a first tracker and an integrator managing hundreds of devices. The following sections explain which information can be used, what can be automated, and how the changes apply to real operations.
Support for GV355CEU-Compatible GPS Trackers
ALTAGAMA GPS added compatibility with devices that communicate through the GV355CEU protocol. A compatible tracker can identify itself, send reports to the platform, and turn them into positions and states that users can review on the map, in history, and through alerts.
The integration recognizes location data such as latitude, longitude, speed, heading, altitude, and report time. It can also interpret operational information sent by the model, including battery level, mileage, status, sensor activity, and compatible emergency events.
When a fleet installs this type of tracker in new vehicles, an administrator can add them to ALTAGAMA GPS without changing the normal monitoring workflow. After each device is configured according to its manual, positions can support tracking, route history, and alert rules.
How States and Sensors Add Operational Context
A coordinate shows where an asset is, but states explain what was happening. When reported by the tracker, ALTAGAMA GPS can connect the position with an input turning on or off, battery level, accumulated mileage, or an emergency event.
This creates more useful context. A security company can confirm where a panic event occurred, a logistics operation can review whether an input associated with ignition was active, and a technician can detect a low battery before the tracker stops reporting.
Exact availability depends on the model, its configuration, and the fields it actually transmits. Protocol compatibility does not add physical sensors to a tracker; it makes it possible to use the data that a compatible device is already able to send.
More Telemetry for Devices Using the GT06 Protocol
We also expanded the GT06 protocol with support for message type 0xA2. This message can carry a more complete combination of position, network information, power, battery level, signal, mileage, status, and device inputs or outputs.
For users, the benefit is a more accurate representation of trackers that use this variant. Instead of discarding an unrecognized message, ALTAGAMA GPS can process it, acknowledge the tracker, and convert compatible fields into operational information.
In a vehicle, for example, the report can help determine whether the ignition input was active, how much mileage the device communicated, and its power condition at that position. This improves diagnostics and reduces gaps in history when a model uses this packet type.
GPRS or SMS Commands Through the ALTAGAMA GPS API
The ALTAGAMA GPS API can now request a command for a device through the public endpoint POST /api/devices/{deviceId}/sendCommand. An integrator identifies the device, provides the command in the request body, and chooses the tracker's data connection or, when available, SMS delivery.
This function supports tasks that previously required opening the interface and acting manually. An external system can apply an approved configuration, request a remote action, or coordinate device administration from its own workflow.
The API accepts the command as a string and supports Text, Hex, and Base64 formats to represent instructions according to protocol requirements. The response indicates whether the request was accepted and returns usage information associated with the call, helping an integration track execution.
Commands should come from the manufacturer or validated documentation for the model. An incorrect instruction can change configuration or interrupt tracker communication. Test with a controlled device first, log the action, and verify the response before deploying it to a fleet.
Real-World API Automation
- Device onboarding: apply connection parameters after installing a compatible tracker.
- Maintenance: request a diagnostic action within an authorized technical workflow.
- Bulk operations: coordinate approved changes without opening every device individually.
- Business integration: connect tracker management with a proprietary application.
- Alternative delivery: use SMS when supported by the model, account, country, and available balance.
A Reorganized Help Center for Learning ALTAGAMA GPS
We rewrote and reorganized the documentation so new users can progress from basic concepts to specialized functions. The Help Center brings together guides for maps, devices, alerts, reports, statistics, settings, subscriptions, and developer tools.
The new structure makes it easier to find an answer by topic and continue through related articles. Instead of relying on a general explanation, users can open the function they are working with, review its steps, and return to the application with a more precise reference.
For someone who has just purchased a tracker, the natural path can begin with device setup, continue with checking the first position, and finish with alert configuration. Engineers can use the API and command sections as context before designing an integration.
Advance Notice for Recurring Renewals
Accounts with an applicable recurring subscription receive a notice approximately one day before the next charge. The reminder provides visibility into the planned renewal so the responsible person can review the payment method and service continuity in advance.
This notification reduces administrative surprises and helps prevent interruptions related to a payment that requires attention. A business can forward the notice to the appropriate team, confirm that the payment method remains valid, and address an issue before the renewal date.
The reminder does not replace subscription management or guarantee payment approval. Its purpose is advance visibility; conditions depend on the plan, payment method, and account configuration.
More Direct Access Between the Public Website and the Application
We created a clearer distinction between the ALTAGAMA GPS informational website and the authenticated application. Visitors looking for commercial information, features, or pricing remain on the public website, while login and tracking tools lead to the working environment.
This organization makes navigation clearer for visitors and registered users. A new customer can learn about ALTAGAMA GPS without confusing informational content with operational controls, while an existing user can reach the map and device management more directly.
We also improved continuity when moving toward authenticated access. The practical result is a more coherent login flow with fewer unnecessary steps when opening a protected function.
Smoother Reconnection for WhatsApp Support
We strengthened the restoration of WhatsApp support conversations. When a session must be re-established, the flow can retain relevant messages and continue with the appropriate team without automatically repeating greetings or steps already completed.
For customers, this reduces the frustration of explaining the case again after a disconnection. When a question about tracker configuration or communication requires several exchanges, the agent can recover context more effectively and focus on resolving the issue.
Identity validation may still be required before account or device information is shared. This verification protects the user while allowing a more continuous conversation.
Security and Stability for Device Management
Alongside the visible functions, we completed security and stability maintenance across shared platform components. This work helps reduce errors, preserve compatibility, and sustain reliable operation as functions and connected-device volume grow.
We describe this work in general terms because it does not change how a customer configures a tracker. Its benefit is broad: more stable access, consistent message processing, and a stronger foundation for the map, API, and notifications.
Related ALTAGAMA GPS Features
To start connecting a device, read Setting Up a New Tracker and the Commands guide. They explain the general flow for identifying a device, reviewing its documentation, and working with compatible instructions.
Developers can review Enable the API before implementing authentication and requests. For service-continuity conditions, see Subscription Plans.
Technical Summary for Users and Integrators
- GV355CEU support includes position, speed, heading, altitude, battery, mileage, status, sensor, and compatible events.
- GT06 accepts message
0xA2and processes the telemetry fields included by the device. - Device commands use
POST /api/devices/{deviceId}/sendCommand. - The body supports a command in
Text,Hex, orBase64format with an optional SMS selection. - Execution is subject to authentication, permissions, usage limits, connectivity, and device compatibility.
- Renewal notices apply only to supported recurring subscriptions.
- Documentation and application access are organized by function and user type.
Before integrating a model or automating a command, confirm the exact protocol, manufacturer documentation, tracker configuration, and capabilities enabled for the account. ALTAGAMA GPS processes what a device transmits, but data availability depends on the hardware and installation.
Explore ALTAGAMA GPS plans and features to evaluate the tracking, API, and support capabilities appropriate for your project.