Gateways

A gateway is the LoRaWAN radio bridge between your devices and the internet. Sensors send uplinks over the air; gateways receive them and forward to the network. This page covers registering, assigning, and managing gateways in ioX-Pulse.

note

Where to find it: Sidebar -> Settings -> Gateways, or Fleet -> Gateways tab for the active gateway view.

How gateways fit in

LoRaWAN devices don't connect to the internet directly. They broadcast over radio; nearby gateways pick up the signal and forward it. A given device's uplink can be received by multiple gateways simultaneously; the network deduplicates and routes the message.

In ioX-Pulse:

• Gateways are registered to your partner workspace.
• Optionally assigned to a sub-account (e.g., dedicated to one customer site).
• Forward uplinks for any device on the same LoRaWAN region, not just devices in their assigned sub-account.
• Reach back into devices via downlinks queued on the network.

You don't need a gateway per sub-account. Many partners have a small number of well-placed gateways serving many customers' devices.

Gateway states

State	Meaning
Inventory	Registered to your workspace but not yet deployed. Hasn't been provisioned on the LoRaWAN network. Doesn't consume an active-gateway license. Sends no data, so it isn't offered in dashboard widgets or workflows until it is assigned.
Assigned	Live. Provisioned on the network. Assigned to a sub-account. Consumes a license seat.
Archived	Decommissioned. Removed from the network. Frees the license seat.

States transition: Inventory -> Assigned (via Assign), Assigned -> Inventory (via Unassign), Assigned -> Archived (deprecated path; new deployments use Unassign + delete instead).

Registering a gateway

Gateways enter ioX-Pulse via Inventory.

1. Settings -> Gateways -> + Register Gateway.
2. Fill in:
   • Gateway EUI - 16 hex characters, from the device's label or the manufacturer's web portal.
   • Name - friendly identifier (e.g., "Roof gateway, North building"). 1-120 characters.
   • Frequency - LoRaWAN region: EU868, US915, AU915, AS923, IN865. Pick the region for your country / deployment. Your tier may restrict which regions are available.
   • Model (optional) - e.g., "Milesight UG65". Metadata only, doesn't affect networking.
   • Backhaul (optional) - how the gateway reaches the internet: Cellular, Ethernet, Wi-Fi, or Other. Metadata only; you can set or change it later from the gateway's Edit form.
3. Click Register.

The gateway is now in your Inventory, no active connection yet.

After registering, ioX-Pulse shows the ioX-Bridge settings to configure on the gateway hardware so it can reach the network. See Connecting your gateway to ioX-Bridge for the full walkthrough.

caution

Gateway EUIs are globally unique. If the EUI is already registered in ioX-Pulse (under your workspace or someone else's), or in another LoRaWAN tenant, registration fails. If you believe the conflict is wrong (you bought the gateway second-hand, for example), contact ioX-Connect support.

Permission required: Partner Admin.

Assigning a gateway to a sub-account

Assignment provisions the gateway on the LoRaWAN network and binds it to one sub-account.

1. Settings -> Gateways -> find the gateway in Inventory.
2. Click Assign.
3. Pick the destination sub-account. Only customer sub-accounts are valid targets, not Inventory or Archive.
4. Click Assign Gateway.

In the background, ioX-Pulse provisions the gateway on the network with the right frequency tags. Within a few seconds, the gateway can start serving traffic.

A gateway can serve devices from any sub-account, not just the one it's assigned to. Sub-account assignment is for licensing and visibility (who sees this gateway in their list, who's responsible for it), not for traffic restriction.

Making gateways available to claim

Instead of assigning a gateway yourself, you can let a customer claim one they physically hold by entering its Gateway EUI and serial number (both on the gateway label). It mirrors device claiming: the gateway stays in Inventory until claimed, then provisions on the network and becomes assigned to that customer.

To make a gateway claimable, open it and use Edit -> Available to claim. The toggle requires:

• A serial number on the record. Claiming matches on Gateway EUI and the exact serial (case-sensitive), so a gateway with no serial can't be offered.
• A non-cellular gateway. A cellular gateway carries a managed data plan billed to you, and that plan would follow the gateway onto whoever claims it, so cellular gateways can never be made claimable. The toggle is disabled with the reason shown when the gateway is cellular, already assigned, or missing a serial.

note

This is tier-gated. A customer can only claim when Sub-account gateway claiming is enabled on their sub-account tier, and each tier can cap how many gateways a sub-account may claim with the Per-sub gateway limit (see Tier features and quotas). For what the customer sees, see Claiming a device or gateway.

Unassigning a gateway

Move a gateway back to Inventory without deleting it. Useful for swapping gateways between sites or temporarily decommissioning.

1. Gateway detail page -> three-dot menu -> Unassign.
2. Confirm.

The gateway is removed from the network and returns to Inventory. It stops forwarding traffic for any sub-account. You can re-assign it later, to the same or a different sub-account.

What else happens:

• The gateway's data is permanently deleted: its stats, activity history, power readings, and any GPS-reported position. A location you set by hand on the Location tab is kept. This cannot be undone.
• Workflows the customer created for this gateway are disabled, with an audit entry.
• Dashboard widgets and workflows that referenced the gateway keep their settings and show it as Gateway not available or Unavailable until it is assigned again; see When a device is not available.
• If your plan limits how many gateways you can hold in inventory, the move is refused when it would go over that limit.

The gateway list

Settings -> Gateways shows every gateway in your workspace, grouped by state. The Fleet -> Gateways tab shows only assigned (live) gateways.

Columns:

• Gateway EUI - the unique identifier.
• Name - friendly name.
• Serial - the gateway's serial number (from the label). Blank if not recorded.
• Model - optional metadata tag.
• Backhaul - how the gateway reaches the internet (Cellular, Ethernet, Wi-Fi, or Other), if set. Each type shows as its own color-coded chip so you can tell them apart at a glance.
• Frequency - LoRaWAN region.
• Sub-account - which sub-account it's assigned to (blank for Inventory).
• Status - Inventory / Assigned / Archived.
• Health - Online / Offline / blank (see below).
• Last seen - when the gateway last reported in.

On the Fleet -> Gateways tab the list is sorted online gateways first, then by most recently seen, so the freshest live gateways sit at the top, matching the Device List. That tab also has a Sub-account quick filter (with a No sub-account option for gateways kept at the partner level) alongside the Site and Network filters, and its own Columns button: by default it shows GatewayEUI, Serial, Name, Health, and Last seen, and each user can show, hide, and reorder the rest to taste, saved to their profile. See Choosing your columns. Its search, filters, and page are remembered while users move around the app, exactly like the Device List; see Your search and filters stay put.

Filters:

• Status (Inventory / Assigned / All).
• Sub-account (filter by which customer the gateway serves).
• Backhaul (filter by Cellular, Ethernet, Wi-Fi, or Other).
• Search by EUI, name, serial number, model, or frequency.

Map view - switch from the list to a map showing each gateway's location with a health-colored pin.

Exporting the gateway list to CSV

The Export button on the Gateways page downloads everything you can see in the current table (search and filters applied) as a CSV file.

The file includes each gateway's EUI, name, model, backhaul, serial number, frequency, status, sub-account, description, last-seen, and registered timestamps. It is named pulse-gateways-YYYY-MM-DD.csv. Every export is audit logged.

Permission required: Partner Admin.

Health indicators

Once a gateway is assigned, ioX-Pulse tracks whether it's actively communicating with the network.

Chip	Meaning
Online	The gateway has sent network status messages within the last 30 minutes.
Offline	The gateway hasn't reported in for more than 30 minutes. Either it's powered off, lost connectivity, or has a hardware issue.
(blank)	Status is "Inventory" or "Archived". Health doesn't apply.

Gateways report stats every 30 seconds when healthy. A gateway that's been silent for 30+ minutes (60+ missed reports) is flagged offline.

To get notified when a gateway goes quiet, use a gateway-scoped workflow: it checks a threshold you choose (independent of this fixed 30-minute chip) and emails, texts, or webhooks once per incident. See Rules and Alerts and the shared builder reference, Gateway workflows.

Power source

Gateways that report their power source show a power chip in the detail page header: Line power, or On battery when the gateway has lost line power and is running on its backup battery. Alongside the chip:

• The Overview tab shows a Power row with the backup battery percentage (shown on line power too, so you can spot a battery that isn't holding charge) and, while on battery, how long the gateway has been on it.
• The Stats tab shows a Power card with the backup battery's charge.
• The gateway list marks gateways currently On battery so a site-wide outage is visible at a glance.
• Every line/battery transition is recorded on the Activity tab, so "when did this site lose power" is a lookup.

Which gateways report power depends on the hardware: RF gateways report line/battery state and backup battery health automatically; LoRaWAN gateways generally do not report power, and show no power chip. The platform treats an absent report as "unknown" rather than assuming line power.

To get alerted the moment a gateway switches to battery (with an optional hold to ride out brief blips), use a gateway-scoped workflow with the Gateway on battery power condition; power transitions are evaluated the moment they are reported, not on the next sweep. See Gateway workflows.

Gateway detail page

Click any gateway to open its detail page. Five tabs. A gateway in inventory or archived shows only Overview and Location, with a notice; the other tabs come back once it is assigned.

Overview

Quick reference: EUI, name, model, frequency, status, sub-account, last-seen and last-stats timestamps, and (for gateways that report it) the power source with backup battery charge. Embedded read-only map showing the gateway's position. For cellular gateways, a Data plan card shows the plan status and lets you manage it (see Data plans).

Location

Editable map. Drag the pin to set the gateway's location, or rely on GPS-reported location if the gateway hardware sends one. You can also set the position without knowing the coordinates: use the Search for an address box to type the install address, pick the match, and the pin and coordinates fill in. See Setting a location by address for the full how-to (it works the same on devices and gateways).

Location source:

• Manual - you set it via the map. Sticky, won't be overwritten by automatic updates.
• GPS - the gateway hardware reports its position automatically. Updates whenever the gateway moves.

Setting a manual location is the recommended pattern for fixed installations (roof-mounted, indoor). GPS source is useful for mobile gateways.

Devices

The devices currently reporting through this gateway: every device whose most recent reading was relayed by it, with health chips, last-seen times, and a search box. The tab label carries the count. Works for LoRaWAN and Monnit gateways alike; for LoRaWAN, a reading heard by several gateways counts toward the strongest receiver.

The list follows the traffic: when a device starts reporting through a different gateway, it moves to that gateway's list on its next reading. Devices that connect directly over cellular never appear here, since no gateway is involved. Users scoped to a single account see only their own devices.

Useful for answering "what breaks if I unplug this gateway" before a move, and for confirming a new gateway has picked up the devices you expected. The same association is available per device as the optional Last gateway column on the device list.

Stats

Time-series charts of the gateway's operational metrics over the last 24 hours, 7 days, or 30 days:

• RX / TX packet counts - traffic volume.
• CPU load - whether the gateway is overworked.
• Memory usage - %.
• Temperature - useful for outdoor deployments in heat.
• Power (gateways that report it) - current source and backup battery charge; see Power source.

If a gateway's stats show high CPU or temperature consistently, that's a flag to inspect the deployment.

Activity

Audit log of gateway mutations (register, assign, edit, unassign, delete) and power transitions (line power lost or restored), plus a runtime summary (uplinks forwarded in the last 24h, total RX/TX, last seen).

Useful for diagnosing "why did this gateway stop working three days ago" type questions.

Editing a gateway

Open the gateway detail page -> Edit button.

Editable:

• Name - friendly label.
• Model - metadata tag.
• Backhaul - how the gateway reaches the internet (Cellular, Ethernet, Wi-Fi, or Other). Metadata only.
• Serial number - from the gateway label. Required before the gateway can be made available to claim.
• Available to claim - offer this gateway up for a customer to claim by EUI and serial. Non-cellular gateways only. See Making gateways available to claim.
• Frequency - LoRaWAN region. Changing this re-tags the gateway on the network and may briefly disrupt traffic.
• Location - via the Location tab.

Permission required: Partner Admin.

Removing a gateway

Removing a gateway:

1. Detaches it from the LoRaWAN network (it stops forwarding traffic).
2. Soft-deletes the row in ioX-Pulse (the record stays in the database for audit but is hidden from the UI).
3. Devices that were uplinking through it are unaffected; their uplinks will route through other gateways in range, if any.

How:

1. Gateway detail page -> three-dot menu -> Delete.
2. Confirm.

Permission required: Partner Admin.

If a gateway was the only one in range of certain devices, those devices will appear offline until you deploy a replacement gateway or move them within range of another one.

Data plans

ioX-managed cellular gateways ship with a SIM and carry a cellular data plan, billed monthly or annually alongside your subscription. Gateways on your own SIM, and gateways that are not cellular, are never billed for a data plan.

You manage a gateway's data plan from its detail page, on the Overview tab, in the Data plan card.

What the card shows

• ioX-managed cellular - the gateway carries an ioX data plan. When it is active the card shows Active, and the amount appears on your Billing page with the rest of your subscription.
• Your own SIM - the gateway is bring-your-own and is never billed.
• Not cellular - the gateway does not use a cellular connection, so there is no data plan.
• Not classified - we have not yet determined how this gateway connects. If it is on your own SIM or is not cellular, mark it (see below) so it is never billed.

You can always assign and use an ioX-managed cellular gateway, including while your account is on a free trial - the hardware works straight away. The data plan itself only starts once your subscription is active, so during a trial the card shows that the plan starts when your subscription becomes active. Nothing is charged for the data plan until then, and it begins automatically after you move onto a paid plan.

Marking a gateway as your own SIM

If a gateway uses your own SIM, or is not cellular, mark it so it is never billed:

1. Open the gateway, Overview tab, Data plan card.
2. Choose My own SIM (BYO) or Not cellular.

Gateways that ioX issued are classified by ioX and cannot be changed here - their data plan is part of the hardware you bought from us.

Permission required: Partner Admin.

Stopping a data plan

When you retire an ioX cellular gateway, you can stop its data plan:

1. Open the gateway, Overview tab, Data plan card.
2. Select Decommission, then confirm.

The change takes effect at your next renewal - the gateway keeps its data plan until then, and there is no refund for the rest of the current period. The card shows the date it stops. You can select Cancel decommission any time before that date to keep the plan.

Permission required: Partner Admin.

Frequently asked

Can I have multiple gateways at the same location?

Yes, and you should for redundancy in critical deployments. The network deduplicates uplinks received by multiple gateways. The trade-off is license cost: each assigned gateway consumes a seat.

A device is offline but the gateway is online. What's wrong?

The gateway is reachable from the network's perspective (it sends stats), but the device is either (a) out of radio range, (b) misconfigured (wrong frequency, wrong join keys), or (c) actually broken. Check the device's Events tab for the last received uplink and decode status.

Can a sub-account see gateways assigned to other sub-accounts?

No. Sub-account members only see gateways assigned to their sub-account, plus Inventory gateways (which any partner-tier user can see for diagnostic purposes).

Can I move a gateway between sub-accounts without going through Inventory?

Not in a single action today. Unassign it (returns to Inventory), then re-assign to the new sub-account. Direct reassignment is on the roadmap.

Why isn't location showing up automatically for a new gateway?

Not every gateway model reports GPS. If yours doesn't, set the location manually via the Location tab. Once set manually, it stays sticky.

Do gateways count separately from devices in my tier?

Yes. Your tier has separate quotas for active devices and active gateways. Check Settings -> Plan for current usage.