Device control
Connect IoT devices with remote commands, event capture, and self-describing config.
Raytio Device control connects IoT devices in the field to the platform: remote command dispatch, real-time event capture, configuration delivery, and a configurable slot-and-product model that adapts to different device types without code changes. Usage events flow through to billing, so a device interaction becomes a metered charge.
Capabilities
The model has four entities: devices, slots, commands and events.
- A device has many slots, each holding one catalogue product.
- Commands flow from the cloud to the device.
- Events flow from the device to the cloud.
Slots adapt to vending rows, service bays, or session-based devices without code changes.
Correlation IDs track commands through pending, sent, acknowledged, completed and failed.
A halt, set, release pattern reserves a slot, dispenses and captures payment, then releases the slot. The sequence has defined failure handling.
Operational events for health and faults; usage events forwarded to billing for metered charging.
A structured topic convention means a device only receives its own commands and publishes on its own topics.
Firmware requests authoritative config by section at startup; an audit pair inspects what a device actually applied.
Notable details
Devices connect over TLS with certificates restricting publish and subscribe to their own topic path.
Management uses the REST API; firmware reads config only over messaging, read-only.
Part of Operate · Read the documentation →
Verified customers, protected data, and agents you can hold to account.