See Your Devices and Health

For most ActionStreamer customers that have a device in-hand, the first useful step is seeing which devices are online and what they are reporting.

ActionStreamer ships device software that runs on each camera and keeps the portal updated. Once that software is installed and the device is connected, you can use the API to check the fleet and inspect current health.

This post shows the two most useful views:

• The device list

• The current health list

If you are using the Python SDK, the wrapper handles request signing for you once you provide your access key and secret key. If you are calling the API directly, use the same HMAC SHA256 signing flow from the previous post.

What You Need

• An authenticated session or a signed API request

• One or more connected devices

• Access to the device fleet

What The Device Software Does

The software package installed on each device handles the connection to the platform and keeps the device reporting in.

For portal users, that means you do not need to build your own device agent code just to see the basics. The API already exposes the device inventory and the latest health data.

Step 1: Get The Device List

Use GET /v1/device/list to see the devices you can access.

Example request:

 GET /v1/device/list HTTP/1.1
Authorization: <your-session-or-signed-request>

The response is an array of device records. Each item includes fields such as:

• key

• deviceName

• serialNumber

Use this endpoint when you need to find a device ID, confirm the camera name, or build a simple fleet inventory view.

Step 2: Get The Current Health List

Use GET /v1/device/list/health to see the latest health summary for the devices you can access.

Example request:

GET /v1/device/list/health HTTP/1.1
Authorization: <your-session-or-signed-request>

You can also add ?status=online to focus only on online devices:

GET /v1/device/list/health?status=online HTTP/1.1
Authorization: <your-session-or-signed-request>

The response is an array of current health rows. Each row includes fields such as:

• key

• deviceName

• serialNumber

• batteryStatus

• batteryPercent

• batteryVoltage

• cpuTemp

• gpuTemp

• cpuPercent

• accessPointName

• networkAlias

• frequency

• linkQuality

• signalStrength_dBm

• transferBitrate_Mbps

• deviceStatus

• cameraStatus

• cameraActivity

• tunnelStatus

• softwareVersion

• lastHeardFromDate

• lastVideoClipDate

• softwareDeployDate

This is the view most device owners want first, because it tells them which devices are online and how they are behaving right now.

How The Python SDK Fits In

If you are using the Python SDK, you do not need to sign these requests by hand.

The SDK takes the access key and secret key in its config object, then handles signing in the wrapped calls. The device and health workflow is the same either way. The only difference is whether you build the HTTP request yourself or let the wrapper do it.

Common Mistakes

• Looking only at the device list when you also need live health

• Ignoring the status=online filter when you only want active devices

• Treating the health list as historical data

• Using the wrong device ID when you move on to a single-device query

• Assuming the device software package changes the API contract

Why This Matters

This is the most practical starting point for device owners.

It gives you a quick answer to the two questions that usually matter first:

• Which devices do I have?

• What is each device doing right now?

What Comes Next

The next post will go deeper into device health so you can query a single device’s current health record and start building more specific monitoring views.