No Telemetry

Symptoms

• Device shows DISCONNECTED (no telemetry in 15 seconds)
• Adapter status ERROR or NOT_IMPLEMENTED
• UNS Explorer empty for expected tags
• Operations Center connectivity KPI low

Checklist

1. Adapter orchestrator — docker compose logs adapter-orchestrator; device should show RUNNING for live in-process adapters
2. Connection config — host, port, MQTT URL, or OPC endpointUrl matches the field device
3. Tags — at least one active tag with valid address for the adapter type
4. Inactive tags — if a tag was deactivated, it will not appear in UNS or live views and will not receive new history; reactivate on the device Tags tab or check includeInactive in API lists
5. NATS — telemetry-worker and api healthy; seeded SIMULATOR should work without external network
6. NOT_IMPLEMENTED — Modbus TCP and some types need external iot/ adapters or a different adapter choice — see Adapters
7. Browser vs API — if console UI fails but health OK, check NEXT_PUBLIC_API_URL and rebuild frontend (Deploy troubleshooting)

SIMULATOR sanity check

Open the demo plant device in Devices — SIMULATOR should stream within seconds after stack start.

Related

• Data quality
• Plants, machines, and devices
• Adapter contract