Ways to connect
Equipment that can run Arduino code, talk through a cellular modem, or make a web request can report to MaxwellTrack. Pick the path that matches yours.
| You have | Use | Guide |
|---|---|---|
| A board on WiFi: ESP32, ESP8266, Pico W, UNO R4 WiFi and others | The device library | WiFi |
| Any supported board with a 2G or 4G modem | The device library with the modem | Cellular |
| Meters or drives on RS-485 beside a board, with rules that must keep working offline | The device library's local rules and Modbus | Local rules and equipment |
| Industrial equipment on Modbus, OPC UA or CAN, or a site that must keep working without internet | A MaxwellTrack site gateway | Site gateways |
| Another gateway, controller bridge, computer, phone app or script | The device report API | Device report API |
| Another system that should start an automation, such as a form or a payment | An automation webhook | Automation webhooks |
| Vehicles | Trackers fitted and set up by MaxwellTrack | Fleet tracking |
What every connection needs
- A device in your account, created from a template.
- Its Device ID and access token, from the device's Settings tab.
- A datastream on the template for every key the device writes. Readings for other keys are ignored.
Supported boards
ESP32 (including S2, S3 and C3), ESP8266, STM32, Raspberry Pi Pico and Pico 2 (with or without WiFi), Arduino UNO R4 (WiFi and Minima) and Nano R4, Arduino Zero, MKR, MKR WiFi 1010 and Nano 33 IoT, Arduino Mega, Uno and Nano. Boards with WiFi connect over WiFi or a cellular modem, the ESP8266 over WiFi only, and every other board through a cellular modem. The full table, with how each board is updated, is in Supported boards.
Decide how often to send
Each value a device sends is metered as one reading, so send on a timer or when a value changes rather than on every pass of a loop. See Billing.
Something unclear or out of date on this page? Tell support.
