Device Console
A developer console at the bottom of the sensor page. It shows every request your device sends, including refused ones and the reason, and has tools to decode payloads, check the link and send commands.
Opening the console
`. Drag the top edge to resize. Full screen on phones. The console keeps the last 48 hours, up to 2,000 lines per sensor. The help button in the console shows short help with examples for the open tab.
Every request as it arrives
New lines appear at the bottom. Use the checkboxes to show accepted, rejected, duplicate or command lines, and grep to filter by any text such as 401, fport 2 or TEMPERATURE. Click a line to see everything about it.
| Connection | A line shows |
|---|---|
| HTTP | Status, measurement type and value, signature check, device clock offset. For an invalid signature it shows the exact string the server expected you to sign. |
| LoRaWAN | fPort, frame counter, payload bytes, decoded values, RSSI, SNR and gateways. For a rejected uplink the reason, for example a missing fPort layout. |
| Commands | Each step: queued, delivered, acknowledged, declined with reason, cancelled. |
Test a LoRaWAN payload
Paste a payload and pick an fPort. The server decodes it exactly like a real uplink and shows which bytes become which value, with raw value and formula. Accepts hex (09 15 18 9C), Base64 as TTN and ChirpStack show it (CRUYnAMs) and decimal bytes ([9, 21, 24, 156]). Nothing is stored.
The same decoder sits in Sensor Settings next to your fPort layouts. There it decodes against the layout you are editing, before you save it.
How well the device reaches HydroNode
Pick a window of 6, 24 or 48 hours. LoRaWAN sensors see the Link tab, HTTP sensors the Timing tab.
| Value | What it tells you |
|---|---|
| RSSI, SNR | Radio strength, last, min and max. Above −110 dBm is comfortable, below −120 dBm the link is marginal. |
| Frames | The last 100 frames as a grid: received, rejected or lost. Loss is counted from gaps in the frame counter. Above 5 %, move the antenna or add a gateway. |
| Device clock | HTTP only. How far the device clock is off and how fast it drifts. Requests more than 2 minutes off are refused, so the tab shows when that limit will be reached. |
| Interval | Expected and typical gap between readings, the last gap, a countdown to the next expected reading, and a chart of how punctual arrivals are. |
Send commands from a prompt
Available for devices that support commands. A command is queued and picked up with the device’s next request; the device answers with acknowledged or declined.
pump:uint32 1500 name, type, value fan:bool true run Water 4s send a saved template cancel last take back what is still queued
Types: bool, int32, uint32, int64, uint64, string. Tab completes names, ↑ recalls earlier commands, help lists everything.
From values to bytes
LoRaWAN only. Pick an fPort, type real values such as 23.25 °C, and get the bytes your firmware must send, in hex or as a ready call for LMIC or RadioLib. Verify on server decodes the bytes back and compares them. Values outside a channel’s range are clamped and marked.