A LoRaWAN sensor network was the answer to gathering readings from a large site without pulling cable to every sensor. These five posts run from cutting an enclosure for the node to data that never showed up on the server.

The assembled LoRa sensor node enclosure

All five start the same way. The checker reports zero, the gateway stays quiet, the server answers OK every time. The pass signal came first and the problem came after it.

Standing the node up

What has to work before anything goes on the air: a box for three boards, and a gateway that understands what the box is saying.

Adding sensors, adding devices

The two problems that arrive once the radio works: the real sensors are on site, and someone asks how many devices will fit.

The last stretch to the server

After the whole thing started running alone inside the gateway. The radio worked, the sensors worked, and half the data disappeared.

What the LoRaWAN sensor network series comes down to

One thing repeats across all five parts. An automated check, a silent radio, and an OK response all look like the absence of a problem, and none of them is evidence.

  • A checker reporting zero is not the same as a part you can assemble
  • The failures that leave no log are the expensive ones - silence does not record its cause
  • Vendor documents contradict themselves, and the simulator built to stand in for hardware becomes the tool that proves it
  • An OK on every send does not mean anything was stored, and rules built on partial logs were wrong three times

A pass signal is not evidence. The cause only appeared after the full record was compared line by line.

Contact