Data isn't arriving or a rule doesn't fire

#The device is online but there's no telemetry

• Wrong topic: telemetry must go to tic/things/<name>/telemetry, where <name> is the device's own name. Check Messages on the device for what actually arrived.
• Denied publish: the policy doesn't allow the topic. The Timeline shows the denial.
• No numeric fields: only numbers become metrics. "temperature": "-19.4" (a string) is stored in the message but not charted; send -19.4.

#A label or sensor behind a gateway doesn't update

• The gateway's message must name the child in esl_id (or device, tin, device_id, child) exactly as the thing is named.
• The child must have the gateway as its parent.
• If the gateway is offline, all its children show offline too. Fix the gateway first.

#A LoRa sensor doesn't update

See LoRaWAN sensors and gateways: check the region, keys and gateway, and look for lora_unknown_device in the Event log.

#A rule doesn't fire

1. Paste the exact topic and payload from the device's Messages tab into the rule's test bench. If it doesn't match, the FROM topic or WHERE clause is wrong (remember + is one level only).
2. If it matches but the action fails, the rule's failed count goes up and the message is in its dead letters with the error, for example an HTTP 401 from your webhook. Fix the cause, then replay.
3. Twin updates don't go to rules. Use telemetry or events for anything a rule should react to.

#Commands stay queued

The device isn't connected, or isn't subscribed to its command topic. Commands are delivered when it reconnects, until they expire. For a child device, its gateway must be online and acknowledge with the command_id.