Register, Assign, and Monitor LoRaWAN Devices
LoRaWAN device management is the work of registering devices, provisioning them onto the network, assigning them to the right customer or site, and keeping track of their health once they are in the field. ioX-Pulse handles all four from one place, for devices from any manufacturer.
Most of that work happens once per device, in the first ten minutes of its life, and then never again. The rest of the time what you need is a list that tells you which units have gone quiet, which are running low on battery, and which are reporting from a weak signal position before that turns into a support call.
Key specifications:
- Import 1,000 devices from one spreadsheet, with every row checked before anything commits
- Let customers bring their own devices online using two numbers printed on the label
- See battery, signal, and last-heard-from on every device, with nothing to configure per device
- Works with sensors and gateways from any LoRaWAN hardware manufacturer
- Devices sitting in inventory cost you nothing until they are assigned
- Know a device has gone quiet within 30 minutes, or set your own threshold
Trusted by customers across multiple industries
The part nobody quotes for
Fleets Get Harder to Watch, Not Harder to Deploy
Registering one device takes a minute. Registering four hundred takes a week, unless you can do it in a single file. But deployment is the part everyone plans for. The part that catches people out is what happens next, because the job changes completely. You stop deploying and you start noticing.
Noticing the unit that has not reported since Thursday. Noticing the three running at eight percent battery. Noticing the site where every device sits at the edge of coverage, so one bad week of weather takes them all offline at once. Most platforms hand you a device list. Fewer hand you a device list that tells you which forty of your four hundred devices need you this week.
Status, battery and last seen are columns you can sort and filter the whole fleet by.
Know Which Devices Need You This Week
Once devices are in the field, one screen matters more than the rest: the list that tells you what changed. It sorts live devices first, updates as readings arrive, and filters down to whatever you are chasing, whether that is one customer, one site, or every device that has gone quiet.
Every device carries a Signal Quality score between 0 and 100, which combines the two radio measurements into one number anyone can read. Sort by it and your weakest-connected devices rise to the top. That is your site visit list, and you get it without configuring anything.
What the fleet list tells you at a glance
- Which devices have gone quiet, based on a 30-minute threshold you can change per device
- Which have an alert nobody has acknowledged yet
- Which are transmitting too often, usually a misconfiguration worth catching early
- Which are sending data that does not match their profile, usually the wrong profile assigned
- Which have a compliance document expiring in the next 30 days
- Which are sitting on a weak signal, before that becomes a support call
Works With the Devices You Already Own
You do not have to replace a working deployment to get better management of it. ioX-Pulse takes devices from any manufacturer: sensors from the major vendors are already in the profile library with tested decoders, and anything missing can be added. All you need from the manufacturer is the two identifiers every LoRaWAN device ships with.
Five regional frequency plans are supported, and LoRaWAN is not the only way in. Cellular NB-IoT and LTE-M devices register alongside it, and Blues Notecard devices connect through your own Notehub project.