LoRaWAN sensors and gateways

LoRaWAN is built in: sensors are things in the same registry as your other devices, secured, monitored and used in the same rules.

1. 1Add the sensorDevEUI + AppKey (+ JoinEUI)
2. 2Register the gatewaythen point its packet forwarder at your workspace
3. 3Sensor joinsover the air (OTAA)
4. 4Uplinks become telemetrydecoded fields, RSSI, SNR
5. 5Downlinks are commandswith fPort and acknowledgement

#1. Add a sensor

Get started → LoRa device. Enter the DevEUI and AppKey printed on the sensor or its datasheet (and the JoinEUI/AppEUI if it has one). IoT Core registers it on the LoRa network for you; there is no second screen to fill in. Deleting the thing removes it from the network too.

#2. Register and point the gateway

Register each gateway with its gateway ID (from the gateway's label or admin page) using POST /v1/lora/gateways, or ask us to add it. Then set the gateway's packet forwarder to the LoRa server address and port in your workspace details. The gateway shows online once it starts sending.

#3. Uplinks

Each uplink becomes telemetry on the sensor: the decoded fields (from the device profile's codec) plus rssi, snr, the frame counter and which gateways heard it. The twin's reported state is updated with the latest decoded values.

#4. Downlinks

Send a command with fPort and the payload as data_hex (or data_b64, or a JSON object if the codec encodes it):

{ "fPort": 10, "data_hex": "0164" }

The command is queued for the sensor's next receive window and marked acked or failed when the network confirms it.

#Troubleshooting

• Never joins: wrong AppKey or JoinEUI, the wrong region, or no gateway in range. The Event log shows join attempts it heard.
• Uplink for an unknown DevEUI: logged as lora_unknown_device, never dropped silently. Add the sensor, or fix the DevEUI.
• Gateway offline: an issue opens on the support page and closes by itself when the gateway is back.