Skip to main content

Radium BLE Gateway

The RADIUM is Iongrade's BLE → MQTT gateway: it continuously scans the environment, captures the signals from Bluetooth Low Energy (BLE) beacons, filters what matters and publishes everything, in real time, to the IonGuard platform's MQTT broker.

Beyond relaying signals, the gateway has local intelligence: it detects panic and tamper events, drives sirens and signaling devices through its own outputs, and keeps operating — storing events for later delivery — when the network goes down.

Overall view of the Radium gateway board


Overview

The RADIUM is built on an ESP32-S3 with Bluetooth 5.0 and support for LE Coded PHY (long-range scanning), scanning LE 1M and Coded PHY in parallel.

Key features:

  • Two network media — WiFi 2.4 GHz or Ethernet 10/100-Base-T (RJ45), with automatic failover between them.
  • High-precision internal clock (RTC) with NTP synchronization — every event carries a reliable timestamp.
  • Embedded web server — all configuration is done through a browser, with no dedicated software.
  • 4 inputs and 4 outputs for call buttons, tamper sensors, sirens and signaling devices, with a local alarm engine.
  • USB-C or PoE power, with a 1000 mAh internal battery, fuel gauge and power-saving profile.
  • Network security — TLS/mTLS on MQTT and 802.1X authentication on WiFi and Ethernet.
Configuration only through the local portal

For security reasons, the network and broker configuration is done only through the portal served by the board itself — it is never changed remotely over MQTT. This prevents a remote command from locking the gateway out of the network.


How It Works: From Beacon to MQTT

The information flow has three links:

LinkRole
BeaconBLE device that transmits signals periodically (about 1 per second, configurable). It can be a panic button, an asset tag or a person tag.
RADIUM gatewayFixed BLE receiver installed in a zone. It captures the signals of every beacon in range, applies the configured filters, converts each signal into a standardized message and publishes it over MQTT.
IonGuard platformReceives the signals, identifies each beacon by its MAC, estimates the location zone from the antenna with the strongest RSSI and detects events (panic, low battery, device offline).

In ION Guard, the RADIUM is registered as an Antenna of the Synapsys (Indoor Location) module and assigned to a zone — the platform considers the zone of the antenna that heard the beacon with the strongest RSSI as its location.

Iongrade's antenna, and third-party ones

The RADIUM is Iongrade's proprietary hardware for this role. ION Guard also accepts third-party BLE gateways — currently the Minew MG4C —, which act as antennas in the same way. Both can coexist in the same installation.

On every scan cycle the gateway assembles a batch with all captured signals and publishes it to the signals topic. The batch starts with a gateway health entry and continues with one entry per beacon signal, each carrying the MAC (the beacon's unique identifier), the signal strength (RSSI), the signal type and the capture timestamp.

Location is estimated by the antenna, not by the beacon

The beacon does not know where it is. It is the platform that estimates the zone by comparing the RSSI with which each gateway heard that beacon — which is why antenna placement defines the resolution of indoor location.


Local Intelligence

The RADIUM does not depend on the cloud to react. Even without internet, it:

  • detects panic — from a beacon (BLE button) or from a physical input, always with top priority;
  • triggers alarms — sirens, signaling devices and other loads on outputs S1–S4, with configurable delay, pulse and latch;
  • stores events — signals and panic events go to memory and are re-sent, with their original timestamp, as soon as the connection returns;
  • signals its state through the RGB LED, with a blink code per problem type.
Panic is a silent alarm

A beacon PANIC never shows on the LED, for safety reasons. Panic signals are also immune to every publishing filter — they are never discarded by the minimum RSSI, by a disabled category or by duplicate removal.


Portal Access Accounts

The gateway portal works with a cumulative permission ladder: each account does everything the lower levels do, and gains pages of its own.

AccountUserWhat it is for
Normal (common)radiumDay-to-day operation — network, MQTT, inputs, outputs, scanning, filters, LED, alarms, information and diagnostics.
Integratorradium_integradorField commissioning — adds the Power profile and the beacon registration, and changes the common user's password.
AdministrativeIongrade's internal accounts (production line and fleet administration), with their own restricted-circulation manual.

Permission checking is done on the server, inside the gateway itself, on every request: the menus merely hide the icons the account cannot use, but typing a page address by hand does not bypass the control.


Technical Specifications

ItemSpecification
Processor and memoryESP32-S3, 16 MB of permanent memory (flash) and 8 MB of temporary memory (PSRAM)
BluetoothBLE 5.0, with LE 1M and LE Coded PHY (long range)
NetworkWiFi (2.4 GHz) and Ethernet RJ45, with automatic failover
Network securityTLS/mTLS on MQTT; 802.1X (WiFi: PEAP/TTLS · Ethernet: EAP-MD5/PEAP)
Inputs4 digital inputs for dry contact (IN1–IN4)
Outputs4 electronic outputs (S1–S4), up to 24 V / 1 A each — mind the polarity
Power supplyUSB-C (5 V / 1 A min.) and PoE (IEEE 802.3at Class 2)
BatteryInternal 1000 mAh with fuel gauge; typical runtime of 6 h (up to ~10 h with power saving)
ClockHigh-precision internal clock + automatic synchronization (NTP)
Status LEDRGB
Beacon capacity5000 registered beacons
Signals per cycle512 signals per scan cycle (maximum)
Offline reportsUp to 24 thousand signals in temporary memory and up to ~47 thousand in permanent memory; panic events have a dedicated area (1024)
ConfigurationWeb portal (at 192.168.4.1), pt-BR / en-US
UpdatesOTA (firmware in two A/B banks with rollback; pages updated independently)
Operating temperature-40 °C to +80 °C
Typical consumption200 mA (average) at 5 V
Version of this documentation

Documentation based on the RADIUM v1.0 manual and on firmware 1.0.0.


Next Steps