Gateway data not arriving

Work through the section that matches what you see.

The gateway stays Offline

No message from the gateway has been accepted.

1. Wait 30 seconds. The Firmcraft IoT Dashboard picks up new and changed gateways every 30 seconds. If you just added or edited the gateway, wait, then send data again.

2. Check the port and Authentication Method. They must match how the gateway connects:

   The gateway connects on	Set Authentication Method to	Port
   Plain MQTT	None (anonymous) or Username & Password	1883
   TLS with an IoT Dashboard certificate	Self-Signed Certificate	8883
   TLS to your own broker	Username & Password, with Enable TLS / SSL ticked	8883

   A gateway set for TLS that receives plain messages, or the other way round, rejects them all as coming from the wrong broker.

3. Check the broker. The IoT Dashboard connects to the broker in Broker / Server IP or URL. If it's your own broker, check that it's reachable from the internet and that the username and password allow subscribing to the topic.

4. Check the topic. Compare the topic the gateway publishes on with the Topic Path:

   • A {device} segment matches any single level, such as GW-1/{device}/telemetry matching GW-1/meter-5/telemetry.
   • Upper and lower case don't matter.

5. For TLS to your own broker, check that its CA certificate is pasted into CA Certificate (PEM). See Secure connection.

The gateway is Online, but a child device shows nothing

Messages arrive, but none are matched to this child. The child's card on the gateway page says why.

• The Device ID doesn't match. It must be exactly the ID the gateway sends (upper and lower case don't matter). Meter 7 and Meter7 are different.
• The Identifier Field is wrong. It must name the field that holds the child's ID. Paste a fresh sample in the gateway's edit form and check Device identification.
• The child isn't in step 5. Readings for children that aren't configured are ignored. Add it in the gateway's edit form.
• The mapping wasn't saved. Open the gateway's edit form and check that the mappings are still there.

A metric is empty on a child

The card says No value in the latest reading for …. The metric's JSON Path doesn't reach a value in the message, or its transform gives nothing. Paste a fresh sample and use Test Mapping to find which one.

LoRaWAN

The gateway stays Offline.

• Check the Application ID, and for The Things Stack the Tenant. The topic the IoT Dashboard subscribes to is shown under the fields in step 2; compare it with your network server's MQTT integration.
• For The Things Stack, the username must be <application-id>@<tenant> and the password an API key allowed to read application traffic.
• For ChirpStack, check that its MQTT broker accepts connections from the internet.

A sensor shows nothing.

• ChirpStack: the child's Device ID must be the sensor's DevEUI, such as A84041000181C4A1.
• The Things Stack: the child's Device ID must be the end device ID, not the DevEUI.

Only rssi, snr and bytes arrive, no readings. Your network server has no payload decoder for this sensor. Add one on the network server, or read the values from bytes.

Sparkplug B

The gateway stays Offline.

• The Group ID and Edge Node ID must match the edge node exactly. Subscribe to spBv1.0/# on the broker with an MQTT tool and compare the topics.
• Messages from edge nodes that aren't registered as a gateway are ignored.

A device shows nothing. The child's Device ID must be the last part of the device's topic, such as Meter7 in spBv1.0/Plant1/DDATA/Line3/Meter7.

Some metrics never appear. The edge node sends them by alias, and the IoT Dashboard hasn't seen the BIRTH message that names them yet. Trigger a rebirth on the edge node, or restart it.

Still stuck?

Click Get Assistance at the bottom of the dashboard's sidebar. Include the Gateway ID, one sample message, and what you see.