IoT dashboards and data pipelines for your sensors.
Sensors are only useful once their readings reach a screen someone can act on, and that needs a network server, a database and a web front end that a hardware company may not have. We have set up the first two behind our LoRaWAN temperature node, and we build web software alongside the electronics.
Just want monitoring deployed, not a custom build? See Paqett →
The problem
Data from a sensor fleet has to travel a long way: from the radio to a network server, into a database and then into something people can read. Each stage is another thing to build and keep running. A company that has a working device but no web engineers often finds the cloud half harder than the hardware. We would typically set up the pipeline and the dashboard as part of the same project as the device, so the data the hardware sends is the data the screens expect.
We would start from the question the screen has to answer, such as what to alert on and who sees it, and work back to the data the device must send. A dashboard is the last link in a longer chain, so we would check each link before drawing a chart: that the gateway forwards uplinks to the network server, that the server writes them to the database and that the stored readings match what the device measured.
Paqett is our own open-source IoT platform, and paqett.com offers white-label monitoring, with water hygiene first, for companies that would rather buy monitoring than build it. We would also agree who the dashboard is for. A screen for the engineers who maintain the devices needs signal strength, battery state and last-seen times, while a screen for customers needs a clear reading and a clear alert. Access and logins, how long old data is kept and how it is exported are decisions we would settle with you before building, since they are hard to add later.
What we'd build
What we would build behind your sensors
The one pipeline we have run sits behind our LoRaWAN node: uplinks land in ChirpStack and are written to a telemetry database, all on a server we host. The rows describe what we would set up for you.
| Layer | What we'd do | Detail |
|---|---|---|
| Network server | A LoRaWAN network server that receives the uplinks from your gateway or gateways. | We run ChirpStack, fed by an indoor gateway |
| Storage | A telemetry database that holds the readings so they can be queried and charted. | Ours is a telemetry database on a self-hosted server |
| Screens and alerts | A web dashboard and alerting built to your use case and designed with the device data in mind. | Web software is part of our end-to-end scope |
| Open platform | Paqett, our own open-source IoT platform, is another route. | Paqett also runs white-label monitoring, starting with water hygiene |
How working with us goes
- 01 Scope We agree what has to be built, where it lives and where the data goes.
- 02 Prototype Working hardware and firmware on your bench, tested against real conditions.
- 03 Pilot A small batch on real sites, with fixes folded back into the design.
- 04 Production Design for manufacture, a production run, and support once it is in the field.
Related
LoRaWAN sensor design ·IoT product design ·Environmental monitoring ·Asset and vehicle tracking · All sectors →
Need your sensor data on a screen?
Custom hardware, firmware and software, from first sketch to production.
Talk to us about your project alessio.grespi@gmail.comWant it deployed, ready to run?
Paqett, our own open-source IoT platform, also runs white-label monitoring. Ask whether it could carry your sensor data before you commission a new dashboard.
See Paqett →