LORAWAN / APPLICATION ENGINEERING
From radio packet
to useful context.
We design the software around your LoRaWAN network: device onboarding, provider integration, normalized events and the workflows that follow.
Commission with intent.
Match region, device profile, firmware and payload format. Record who owns the device and where it belongs before accepting measurements.
Preserve the evidence.
Keep provider event identity, original bytes and receive time. Normalize the envelope without silently inventing units or sensor meaning.
Make action accountable.
Separate a rule becoming active from someone being notified. Track delivery, acknowledgement and recovery as different events.
Two provider paths.
One integration boundary.
ChirpStack
Ghost Signal maps ChirpStack v4 JSON application uplinks into its versioned envelope. Your deployment provides authenticated transport and durable storage.
Read the mapping ↗The Things Stack
The v3 uplink adapter maps event identity, device EUI, receive time and application payload. Strict validation keeps unsupported input explicit.
Read the mapping ↗DESIGN BEFORE DEPLOYMENT
Questions that
change the architecture.
- Who operates the network server and owns its credentials?
- Which region, device class and firmware are in use?
- How long may data be delayed before it becomes stale?
- What happens when a gateway or internet link goes offline?
- Who receives an alarm, and who owns its resolution?
- How will commissioning and field acceptance be proved?
BRING THE HARD PART
What needs to
work together?
A device. A database. A workflow nobody wants to touch.
Let’s map a practical way forward.