Use cases

If a device can publish JSON over MQTT, IoTAPS can store its history and show it live. Below are common setups and the message each device would send.

Buildings

Climate, air quality, and occupancy per room. Facilities staff get a live view; engineers get the history to tune HVAC schedules.

  • One project per site, one device per sensor or gateway
  • Viewer role for facility managers
  • 30 days of history for comfort and energy analysis
v1/…/room-301/telemetry
{
  "schema_version": 1,
  "message_id": "b2-f3-room-301-000912",
  "metrics": {
    "temperature_c": 22.8,
    "co2_ppm": 684,
    "occupancy": 7
  },
  "attributes": { "room": "301" }
}

Agriculture and greenhouses

Soil moisture, light, and air temperature across beds. Battery nodes can send small, infrequent messages and still leave a complete record.

  • Pump and valve state as booleans next to readings
  • Device time and receive time kept for flaky links
  • Store-and-forward resends are deduplicated
v1/…/gh2-bed4/telemetry
{
  "schema_version": 1,
  "message_id": "gh2-bed4-41ac90",
  "sent_at": "2026-10-05T06:00:00Z",
  "metrics": {
    "soil_moisture_pct": 38.6,
    "lux": 5400,
    "irrigation_on": false
  }
}

Energy metering

Sub-meters, inverters, and batteries. Server-side aggregates turn readings every few seconds into daily and weekly charts without moving raw data to the browser.

  • Min, average, and max per time bucket
  • Up to 64 metrics per message for multi-channel meters
  • Daily usage counters per organization
v1/…/meter-7731/telemetry
{
  "schema_version": 1,
  "message_id": "meter-7731-1759640400",
  "sequence": 88412,
  "metrics": {
    "energy_kwh": 15872.4,
    "power_w": 3120,
    "voltage_v": 231.6
  }
}

Cold chain

A complete temperature record for freezers, reefers, and pallets. Gateways that buffer while offline can resend everything without creating duplicates.

  • Both device time and receive time on every point
  • Door and power state as booleans
  • Excursion alerts are being built, not available yet
v1/…/reefer-18/telemetry
{
  "schema_version": 1,
  "message_id": "reefer-18-0042331",
  "sent_at": "2026-10-05T03:12:44Z",
  "metrics": {
    "temp_c": -18.4,
    "door_open": false,
    "battery_pct": 81
  }
}

Industrial equipment

Vibration, runtime, and run state for machines on the floor, sent from a gateway or directly from the controller.

  • A gateway publishes as its own device identity
  • Firmware and asset data in attributes
  • Every credential change is in the audit log
v1/…/press-04/telemetry
{
  "schema_version": 1,
  "message_id": "press-04-7f3a19c2",
  "metrics": {
    "vibration_rms": 0.42,
    "runtime_h": 18233.5,
    "running": true
  },
  "attributes": { "firmware": "4.2.1" }
}

Environmental sensing

Air quality and weather from distributed stations, with read-only access for partners through the Viewer role.

  • Malformed sensor values are rejected with a reason
  • Live view per station
  • REST API for research and reporting pipelines
v1/…/aq-station-12/telemetry
{
  "schema_version": 1,
  "message_id": "aq-station-12-5521",
  "metrics": {
    "pm2_5_ugm3": 8.4,
    "humidity_pct": 64.1,
    "wind_ms": 3.7
  }
}

System integrators

Separate client spaces, delegated administration, and white-labelling are on the roadmap but not built. If you deliver IoT projects for clients, we would like to work out the design with you. Get in touch.

Have a setup that is not listed?

Tell us what the devices measure and how often they report.