IONA Option Cards: Integrated LoRaWAN Gateway and 4G LTE
IONA's option cards add a LoRaWAN gateway with network server and a 4G LTE modem inside the Niagara 4 controller, removing separate gateways and routers.
Most Niagara controllers need extra boxes to reach wireless sensors or a mobile network. IONA builds both into the controller. This guide explains each option card, how it is configured, what it replaces, and how to decide whether a project needs it.
The IONA option cards
| Option | What it adds | Typical use |
|---|---|---|
| LoRaWAN gateway and network server | A LoRaWAN radio gateway plus the network server software, running inside IONA | Wireless battery sensors for IAQ, temperature, occupancy, energy and leak detection |
| 4G LTE modem (Quectel EG25-G, Cat 4) | Cellular data connection | Remote access, alarm delivery and cloud data where there is no dependable wired network |
| External antennas | A two-pack of magnetic-mount antennas for cellular and LoRaWAN | Panels in metal enclosures or basements where internal antennas would struggle |
Options are fitted to order, so specify them when you buy the controller. The IONA external antennas are sold separately. The IONA-I variant, built on an Intel Elkhart Lake dual-core processor, is the model designed around the integrated LoRaWAN gateway and network server.
The LoRaWAN option
What it does
LoRaWAN is a long-range, low-power wireless network for battery sensors (see What is LoRaWAN?). A LoRaWAN system normally needs three things: a gateway to receive radio packets, a network server to authenticate devices, remove duplicates and manage the network, and an application layer to decode payloads into values.
With the LoRaWAN option, IONA provides all three in one box. Sensor uplinks arrive at the radio, are handled by the on-board network server, and are decoded into standard Niagara points in the station. No cloud network server, no separate gateway on the wall, and no MQTT bridge to set up.
What it replaces
A typical JACE-based design for the same job would need:
- a separate LoRaWAN gateway, such as a Milesight UG65 indoor gateway or UG67 outdoor gateway
- a network server, either on the gateway or in the cloud
- an integration from the network server into Niagara through a driver or MQTT
- power, mounting, network and IT approval for the gateway
The integrated option removes the hardware, the integration layer, and one more device to secure and maintain.
What you can connect
Any LoRaWAN Class A or Class C device using the EU868 band and a supported payload decoder, for example:
- indoor air quality sensors (temperature, humidity, CO2, TVOC, PM2.5)
- temperature and humidity sensors for rooms, fridges and plant
- occupancy, desk and people-counting sensors
- smart current transformers, pulse counters and meter readers
- water leak, door contact and level sensors
- radiator thermostats and LoRaWAN I/O controllers
See LoRaWAN indoor air quality and CO2 sensors and people counting and occupancy sensors for device choices.
Range and planning
A single gateway typically covers several floors of a conventional office building, but range depends heavily on construction. Concrete cores, foil-backed insulation and plant rooms all reduce it. Mount the controller's antenna high and outside metal enclosures where possible; use the external antenna kit where the panel sits in a steel cabinet or basement. Our LoRaWAN range and planning guide explains how to survey a building and when a second gateway is needed.
Configuring LoRaWAN devices on IONA
The workflow is:
- Register each device on the IONA network server with its DevEUI, AppEUI/JoinEUI and AppKey (supplied with the sensor).
- Power the sensor so it joins the network (over-the-air activation).
- Select or add the payload decoder for the device type.
- Add the decoded values to the station as points.
- Add alarms, histories and logic as normal.
Because the data arrives as ordinary Niagara points, LoRaWAN sensors can drive control directly: CO2 sensors controlling ventilation, occupancy sensors setting back heating, leak sensors closing a valve.
The 4G LTE option
What it does
The cellular option fits a Quectel EG25-G LTE Cat 4 modem inside the controller, giving IONA its own mobile data connection with a standard SIM.
When to use it
- No building network: pumping stations, car parks, temporary buildings, remote plant
- IT restrictions: sites where corporate IT will not carry BMS traffic or allow inbound remote access
- Resilience: a backup path for alarms and remote access if the wired network fails
- Fast deployment: getting a site online on day one, before the permanent network is ready
Security considerations
A controller on a public mobile network must be secured properly:
- use a private APN or VPN rather than a public IP address where possible
- keep FoxS and HTTPS only, and disable unused services
- use strong unique credentials and, ideally, two-factor authentication
- keep the Niagara version and modules current
- monitor data usage so a misconfigured history export does not run up a bill
Data SIMs and cellular accessories are available from our cellular connectivity range.
Choosing options for a project
| Project need | Recommended option |
|---|---|
| Add room-level sensing without cabling | LoRaWAN |
| Retrofit an occupied or listed building | LoRaWAN |
| Remote site with no network | 4G LTE |
| IT will not allow BMS on the corporate LAN | 4G LTE |
| Plant room in a steel panel or basement | External antennas with either option |
| Large site with many gateways already installed | Neither; integrate the existing network server instead |
Both options can be fitted to the same controller, and both work alongside the 24 onboard I/O points and the eBMS/IO expansion bus (see IONA I/O and expansion).
How many LoRaWAN sensors can IONA handle?
LoRaWAN capacity is limited by airtime more than by the number of devices. Battery sensors typically send a few bytes every 5 to 15 minutes, so a single gateway can serve hundreds of them comfortably in a typical building. Capacity is used up faster when:
- sensors report very frequently (every minute or less)
- sensors are far from the gateway and fall back to high spreading factors, which keep each packet on air for longer
- many devices send at the same moment, for example after a power cut when they all rejoin
Keep report intervals sensible for what is being measured (temperature changes slowly; a leak sensor only needs to report on change plus a heartbeat), and let adaptive data rate (ADR) move nearby sensors to faster data rates. If a building needs more coverage or capacity, add a second gateway rather than turning sensor intervals down.
Remember that each decoded value brought into the station uses a point of the IONA licence. A sensor reporting temperature, humidity, CO2 and battery level uses four points if you bring in all four values.
LoRaWAN security on IONA
LoRaWAN is encrypted by design. Each device has a unique AppKey from which two session keys are derived when it joins: one protects the integrity of the network layer and one encrypts the application payload with AES-128. Nobody listening to the radio can read or forge sensor data without those keys.
Because the network server runs inside IONA, the keys and decoded data never leave the controller unless you choose to send them elsewhere. That avoids a dependency on a third-party cloud network server and keeps the sensor data inside the same security boundary as the rest of the BMS. Treat device keys like passwords: store the commissioning spreadsheet securely and do not email it around.
IONA LoRaWAN or separate gateways?
The integrated option is ideal when one controller and its gateway cover the area where sensors are needed. Separate gateways still make sense when:
- a large building or campus needs several gateways for coverage, in which case a central network server with multiple Milesight gateways is easier to manage
- the client already runs a LoRaWAN network and wants every sensor on it
- the gateway must sit far from the plant room, for example on a roof, for coverage
The two approaches mix well: IONA can integrate data from an existing LoRaWAN network server through MQTT or a driver while still using its own gateway for local sensors.
Sending LoRaWAN data onwards
Data arrives in Niagara as ordinary points, so everything Niagara can do with a point applies: histories, alarms, graphics, analytics, export to a supervisor. If other systems also need the data, for example a workplace app or an ESG reporting platform, publish selected points through MQTT from the station rather than adding a second LoRaWAN network server. One network, one source of truth.
Troubleshooting the LoRaWAN option
A sensor will not join. Check the DevEUI, JoinEUI and AppKey were entered exactly, that the device is set to the EU868 band, and that it is within range. Many sensors only attempt to join for a limited time after power-up, so reset the device once the registration is complete.
A sensor joined but no values appear. The payload decoder is missing or does not match the device model or firmware. Confirm the decoder, then check the raw uplink is arriving.
Values arrive intermittently. Usually a coverage problem. Look at the signal strength (RSSI) and signal-to-noise ratio (SNR) for the device. Move the antenna out of the metal enclosure, fit the external antenna kit, or reposition the sensor.
Battery life is much shorter than expected. The sensor is reporting too often or is stuck at a high spreading factor because of poor coverage. Improve coverage and review the reporting interval.
Troubleshooting the 4G option
No connection. Confirm the SIM is activated for data, the APN settings match the provider, and the antennas are connected. Check signal strength at the panel location; basements and steel enclosures often need the external antennas.
Connects but remote access fails. Mobile networks often use carrier-grade NAT, so inbound connections to a public IP do not work. Use a private APN, a VPN, or an outbound cloud connection for remote access.
Unexpected data usage. Check history exports, cloud connections and software update downloads. Large station backups should be scheduled over the wired network if one exists.
Example: retrofit with LoRaWAN
On a garden centre project, an IONA with embedded LoRaWAN was installed alongside the existing Trend BMS. LoRaWAN energy meters gave visibility of where energy was going, and new wireless devices improved heating and ventilation control in areas the old BMS did not reach. With the heating plant enabled on demand instead of on stand-by, the site cut energy consumption by 40% month-on-month and 14% year-on-year, with no rewiring of the existing system.
Frequently asked questions
Does IONA have a built-in LoRaWAN gateway?
Yes, as an option. The LoRaWAN option adds a gateway and network server inside the controller, so LoRaWAN sensors report straight into the Niagara station.
Do I need a cloud LoRaWAN network server with IONA?
No. The network server runs on the IONA itself, so no cloud service is needed. You can still forward data to cloud platforms through MQTT if you want to.
What 4G modem does IONA use?
The cellular option uses a Quectel EG25-G LTE Cat 4 module with a standard SIM.
Can IONA have both LoRaWAN and 4G?
Yes. Both options can be fitted to the same controller.
Which LoRaWAN frequency does IONA use in the UK?
UK and European installations use the EU868 band (863–870 MHz), which is licence-exempt.
Can IONA forward LoRaWAN data to the cloud?
Yes. Decoded sensor values are Niagara points, so they can be published to a cloud platform or workplace app through MQTT, exported to a Niagara supervisor, or shared through the Niagara Cloud Suite.
How far does the IONA LoRaWAN gateway reach?
Indoors, typically several floors of a conventional building, depending on construction. Concrete cores and metal enclosures reduce range; the external antenna kit and a high antenna position extend it. Survey before committing to one gateway for a large building.
Can a JACE 9000 do LoRaWAN?
Not natively. A JACE needs a separate LoRaWAN gateway and network server plus an integration into Niagara.