Accessing Real-Time Device Status
This guide explains how you can monitor the real-time status of your Dronetag device, such as battery charge, LTE, and GNSS signal strengths, and other key metrics. You can retrieve this data using either the REST API or the real-time Socket.io API.
Key Differences from Other Telemetry Types
Unlike other telemetry data such as Telemetry-UA or Telemetry-Operator, which are sent frequently, telemetry related to the device’s system status (Telemetry-System) is generally sent at lower intervals—typically every 10 to 15 seconds or more.
Learn more about all telemetry types in the DUMP guide.
Monitoring Specific Device Using UAS ID
To retrieve the status of your Dronetag device in real-time, you must use the device’s UAS ID, which is equivalent to the serial number of the Dronetag device. Unlike other telemetry types that allow observation based on a geographical region (via bbox
), this endpoint does not support monitoring by geographical region. Instead, you’ll need to specify the UAS ID to access data for a particular device.
Authenticate Your API Requests
Ensure you have access to the necessary resources by authenticating your API requests. You can find more details on the authentication process in the authentication guide.
Identify the Device by UAS ID
Before making any requests, confirm the UAS ID (serial number) of the device you wish to observe. You can find the UAS ID on the physical Dronetag device or within your account settings in the Dronetag App, or other API responses.
Request Real-Time System Status Data
Option 1: Retrieve Data via REST API
To access the device's real-time status data through REST API, use the following endpoint:
Set the
uas_id
query parameter to the serial number of the Dronetag device, and define a time range using thefrom
parameter, or bothfrom
andto
.Option 2: Real-Time Updates via Socket.io API
Not available yetThis option is not yet available
For real-time updates, connect to the
telemetry_system
channel via Socket.io. This method delivers lower-latency updates compared to REST polling.