MQTT
Connect devices to the embedded MQTT broker, inspect published messages and topics, and test plain or TLS-enabled MQTT connections where available.
Common tests: connect, publish, subscribe and inspect message payloads.
MQTT testing guide →HTTP
Send device telemetry through the HTTP ingest endpoint and inspect received request payloads and configured responses.
Common tests: endpoint configuration, request bodies, headers and secure HTTPS paths.
HTTP testing guide →TCP
Inspect raw TCP streams with configurable frame boundaries. Device connection modes include token-based authentication and supported protocol-identifier workflows.
Common tests: framing, binary payloads, replies and TLS handshake details.
TCP testing guide →UDP
Receive device datagrams as individual frames and review their payloads in the device workspace.
Common tests: compact telemetry, datagram formatting and device identification.
UDP testing guide →Security and additional integrations
TLS is available on supported endpoints. CoAP/DTLS can be enabled by an administrator as an integration. Supported protocols, ports and options vary by plan and server configuration; confirm the current connection details in your workspace.
Protocol testing, step by step
- 1Choose the transport
Check that the transport is enabled for your plan and device configuration.
- 2Configure identity and framing
Use the assigned credentials or a supported protocol definition for devices with fixed protocols.
- 3Send traffic and inspect it
Review payloads, frame boundaries and acknowledgements in the live workspace.