Connect Devices & Cameras

A Device is the thing that reports — CAN loggers, vision cameras, anything that can POST to the device contract. What each kind is and how it is provisioned: Devices & Media.

List devices — GET /api/v1/devices

curl "https://trydozer.com/api/v1/devices?status=transmitting" \
  -H "Authorization: Bearer $DASH_API_KEY" \
  -H "Project-ID: pr_northpit"

Which devices have stopped reporting?

data_query {
  "collection": "devices",
  "where": {
    "status": "transmitting"
  }
}

{
  "object": "list",
  "data": [
    {
      "object": "device",
      "id": "obj_123",
      "device_id": "canedge-ht14",
      "name": "CANedge2 — HT-14",
      "status": "transmitting",
      "status_color": "status color",
      "status_reported_at": "2026-07-25T12:00:00.000Z",
      "state": "state",
      "observation": "observation",
      "timeline_changes": "timeline changes",
      "metrics": {},
      "created_at": "2026-07-25T12:00:00.000Z",
      "updated_at": "2026-07-25T12:00:00.000Z"
    }
  ],
  "has_more": false,
  "next_cursor": null
}

You do not need hardware to evaluate Dozer. The telemetry-onboarding skill simulates camera feeds so the whole pipeline — device → telemetry → dashboard → playlist — runs against realistic data. That is what this checklist step means by "simulate your cameras", and it is why the completion predicate tests whether the project has a camera-like device at all rather than one exact device_type string.

What a camera frame becomes: Vision AI.

Next: Create a Dashboard.