Check device connectivity

Use Check connectivity on a device to copy credentials and example commands for that device.

Open the dialog

1. Go to Devices.
2. Open a device (Device Details).
3. Click Check connectivity.

You can also open it right after Create device from the success screen.

Tabs

Tab	When to use
HTTP	REST telemetry with device token in the URL; includes Send test
MQTT	Broker host, topics, and sample mosquitto_pub
WebSocket	Device WebSocket auth + telemetry messages
CoAP	UDP POST of the same JSON reading. The device token is in the path
AMQP	Publish to the autoconnecto topic exchange. The device token is the routing key
Gateway	Only for gateway devices — relay payload with childDeviceId
LoRa / webhook	DevEUI editor + link to Integrations (webhook URL and secret)

HTTP, MQTT, WebSocket, CoAP, and AMQP do not require device attributes — only the device token.

MQTT

The copied command uses mqtt.autoconnecto.in port 8883 with TLS. The username is the device token. The payload is JSON. After Rotate, the previous token is refused when it tries to connect.

MQTT over WebSocket uses the same host, port 8084, path /mqtt. The ESP32 library defaults to that port. Port 443 path /mqtt on the app or the API is not the broker.

Do not use app.autoconnecto.in or api.autoconnecto.in as the broker. Port 8883 on the API host is not the broker.

The broker also accepts plain MQTT on port 1883. The command in the app uses 8883.

A top-level numeric ts in the JSON is the time of that reading. It is not stored as a key.

Purpose	Topic
Telemetry	devices/<device-token>/telemetry
Telemetry, older prefix	v1/devices/<device-token>/telemetry
Client attributes	devices/<device-token>/attributes/client
Shared attributes	devices/<device-token>/attributes/shared
Shared attribute request	devices/<device-token>/attributes/shared/request
Shared attribute response	devices/<device-token>/attributes/shared/response
Command request	devices/<device-token>/rpc/request/<request-id>
Command reply	devices/<device-token>/rpc/response/<request-id>

A command reply on v1/devices/<device-token>/rpc/response/<request-id> is also read. A reply on v1/devices/me/... is not, because that topic does not carry the device token.

CoAP

The platform listens on UDP port 5683.

POST JSON to:

The public service does not publish a CoAP hostname. Use HTTP or MQTT for a device on the internet. A private broker that has CoAP enabled accepts:

coap://<broker>:5683/devices/<device-token>/telemetry

The body is the same object you would publish on MQTT, for example { "temperature": 21.5 }. A success response is CoAP 2.04. An unknown device token is 4.01.

This CoAP port is not encrypted. The device token is visible on the network. Use MQTT on the TLS port when the device can.

AMQP

The public service does not publish an AMQP hostname. Use HTTP or MQTT for a device on the internet. A private install consumes a topic exchange named autoconnecto.

Field	Value
Broker port	5672
Exchange	autoconnecto (topic, durable)
Routing key	devices.<device-token>.telemetry
Body	The same JSON object as MQTT

The broker username and password are the plant AMQP account. They are not the device token. Set them before the broker port is open to the internet. The default password in the server install is only for a private network.

A reading published this way is stored the same way as MQTT. Profile alarm rules still run. A rule engine on the profile still runs. A rule-engine drop, or a plan limit, is why a reading is not stored.

LoRa and external webhooks

LoRa networks (ChirpStack, TTN) send DevEUI, not your device token:

1. Enter DevEUI on create (optional card) or on the LoRa / webhook tab → Save.
2. Open Integrations in the sidebar, create or open a LoRaWAN / ChirpStack / TTN integration, copy the webhook URL and generate a webhook secret.
3. Configure the HTTP integration on ChirpStack or TTN with that URL and header.

Generic webhooks (custom cloud, scripts) use a Generic HTTP integration URL. New devices are registered automatically by device ID — no manual attribute required unless you use a custom external id.

For payload mapping (rename/scale/derive keys for any adapter), stay in Integrations (Integration Hub). Copy the per-integration webhook URL or set the integration as default for its type.

Integration webhook settings

Integrations (sidebar)

• ChirpStack and TTN endpoint URLs (include your tenant id)
• Generic HTTP webhook URL
• Generate / rotate webhook secret

Developer reference

• Device connectivity (developer)
• Device SDK