Devices
A device represents a registered IoT endpoint — a physical sensor, gateway, actuator, or any hardware that connects to IOTMER via MQTT.
Device lifecycle
Template (optional)
│
▼
Create Device ──► Auto-generated MQTT credentials
│
▼
Device connects via MQTT
│
├──► State updated (last reported payload)
├──► ACLs enforce topic permissions
└──► Firmware rollout (if applicable)
Key concepts
- Credentials — each device gets a unique MQTT username and password at creation. These can be reset.
- Custom fields — typed metadata (string, number, boolean, JSON) attached to a device. Useful for serial numbers, hardware versions, location, etc.
- MQTT ACLs — per-device rules controlling which topics the device can publish to or subscribe from
- State — the last payload reported by the device, stored and queryable
- Device templates — blueprint for a model (capabilities, JSON defaults, optional auto
device_keypattern, default MQTT ACLs) before you create devices. See Device Templates. - Firmware & Rollouts — distribute firmware updates across your fleet. See Firmware and Rollouts.