9 Web Management Interface Guide
The IMX93-GW8016 gateway provides a web management interface based on OpenWrt LuCI. Daily configuration and status monitoring can be completed through a browser without command-line operations. This chapter introduces the main gateway front-end pages and their features.
9.1 LoRa Gateway Status Page
Entry: Menu Network → LoRa GW → Status
The LoRa Status page displays real-time operational status and statistics for the gateway radio forwarder, helping users verify normal gateway operation.
9.1.1 Connection Status Panel
The top of the page displays the GWMP connection status between the gateway and the NS (network server), including:
| Field | Description |
|---|---|
| GWMP PUSH status | Uplink data channel status (online/offline) |
| PUSH ACK % | Uplink packet acknowledgement rate (%) |
| Network latency | PUSH round-trip delay (ms) |
| GWMP PULL status | Downlink data channel status (online/offline) |
| PULL ACK % | Downlink packet acknowledgement rate (%) |
9.1.2 Statistics Panel
| Field | Description |
|---|---|
| Gateway ID | Gateway EUI (derived from 8-byte MAC address) |
| Uptime | Duration the gateway has been continuously running |
| Total RX RF packets | Cumulative count of received LoRa data packets |
| Uplink ACK Percentage | ACK success rate for uplink packets |
| Downlink ACK Percentage | ACK success rate for downlink packets |
| Total TX LoRa packets | Cumulative count of transmitted LoRa data packets |
| Success / Collision count | Downlink send success and collision statistics |
| Beacon TX count | Class B beacon transmission count |
| RF temperature | Current RF module temperature (°C) |
9.1.3 Frequency Band Configuration
Displays the currently active LoRaWAN regional parameters, including the frequency and spreading factor (SF) configuration for all 9 channels (Channels 0–7 BW125, Channel 8 BW250/BW500, Channel 9 FSK).
9.1.4 MQTT Connection Status
Displays the enabled MQTT connection status, including:
- NS MQTT：NS Direction MQTT(send/receive/Topic)
- APP1/APP2/APP3 MQTT: Application-layer MQTT connection status
- ChirpStack MQTT: MQTT status of the built-in NS
9.1.5 Uplink/Downlink Data Lists
The bottom of the page displays the most recently received uplink packets and the pending downlink queue in table form. Supports filtering by DevEUI and paginated browsing (10/20/50 items per page).
Uplink List Fields: time, type, DevEUI, DevAddr, frequency, data rate, frame data, length, counter, port, frequency offset, RSSI/SNR, payload, parsed object
Downlink Queue Fields: type, DevEUI, DevAddr, frequency, data rate, frame, counter, port, payload
9.2 LoRa Gateway Configuration Page
Entry point: Menu Network → LoRa GW → Configuration
The LoRa Configuration page is used to set the gateway's RF parameters, LoRaWAN regional band, and operating mode. It is divided into two tabs:
9.2.1 General Settings
| Setting | Description |
|---|---|
| Operating Mode | Normal Mode: normal operation; TX power test: transmit power test mode |
| Full-duplex mode | Supported only on CN470 full-duplex hardware; other bands use half-duplex |
| LoRaWAN Region | Select LoRaWAN band: CN470, EU868, RU864, IN865, US915, AU915, AS923-1/2/3/4, KR920 |
| Initialize band parameters | After each band switch, you must click Switch LoRaWAN frequency band to apply the parameters |
After switching the LoRaWAN band, you must click Switch LoRaWAN frequency band first, then click Save & Apply. Otherwise the RF parameters will not be updated correctly.
9.2.2 Detailed Settings
Advanced users can manually adjust settings on this tab:
| Setting | Description |
|---|---|
| Receive RF type | SX1250 / SX1255 / SX1257 (auto-detected based on hardware) |
| RX0 center frequency | RF0 center frequency for the first group of 8 channels |
| RX1 center frequency | RF1 center frequency for the second group of 8 channels |
| Per-channel frequency offset | Offset of Channels 0–7 relative to the center frequency |
| LoRa Standard channel (Ch8) | BW250/BW500 wideband channel frequency and SF |
| FSK channel (Ch9) | Whether FSK is enabled, and the channel frequency/bit rate |
| TX min/max frequency | Compliant downlink frequency range |
| LBT configuration | Listen Before Talk on/off switch and RSSI threshold |
| Spectral Scan | Noise-floor scan starting frequency, channel count, scan count and interval |
9.3 IoT Device Asset Status Page
Entry point: Menu Network → IoT Hub → Status
The IoT Device Asset Management page displays the thing-model mapping status and real-time data for all registered LoRaWAN devices. It is the central monitoring interface for IoT Hub.
9.3.1 Global Statistics Panel
The top of the page shows total device count, online count, and offline count for a quick overview of the network status.
9.3.2 Device List
All devices are listed in table form with the following key fields:
| Field | Description |
|---|---|
| DevEUI | Unique device identifier |
| Device name | User-defined name |
| Sensor Type | Device model (e.g., AN-301, AN-303, W8004, etc.) |
| Online Status | Green (online) / Gray (offline) |
| Last updated | Timestamp of the most recently received data |
| Modbus Configuration | Enabled Modbus TCP port and slave ID |
| BACnet Configuration | Enabled BACnet device instance ID |
Supports filtering devices by DevEUI, sensor type, and online/offline status, with paginated browsing (20 items/page, adjustable).
9.3.3 Edit Device
In the list, click the Edit button to modify:
- Device name, offline detection time
- Modbus TCP mapping: enable switch, port number, slave ID
- BACnet BIP mapping: enable switch, device instance ID
9.3.4 Device Details
Click the Details button to view all current attribute values for the device, displayed as cards. Fields include: attribute name, current value, unit, data type, Modbus register address, BACnet object instance number, and most recent update time.
9.4 IoT Hub Global Configuration Page
Entry: Menu Network → IoT Hub → Configuration
The IoT Hub configuration page manages global parameters for the IoT Hub service, organized into multiple tabs:
9.4.1 Service Tab
| configuration项 | Description |
|---|---|
| Enable HTTP Server | Enables the IoT Hub HTTP REST API service |
| HTTP Port | HTTP service port (default 6060) |
| BACnet instance number | Base BACnet Device instance number for this gateway |
| Auto-Save | Periodically persists runtime data to storage |
| Save Interval | Auto-save interval (seconds) |
| Maintenance interval | Storage inspection interval (seconds) |
| Cleanup threshold | Auto-cleanup is triggered when storage usage exceeds this value (%) |
| Cleanup Delete Percentage | Percentage of oldest data to delete per cleanup cycle (%) |
9.4.2 Sync Tab
| configuration项 | Description |
|---|---|
| Enabled Sync | Enables the device registration information sync feature |
| Sync Interval | Synchronization interval (seconds) |
9.4.3 Defaults Tab
Used to set the default parameters when registering a new device:
| configuration项 | Description |
|---|---|
| Default Keep-Alive Time | If a device does not report data within this period, it is marked offline (seconds) |
| Default sensor type | Default sensor model when creating a new device |
| Default Modbus TCP | Whether Modbus mapping, port, and slave ID are enabled by default |
| Default BACnet | Whether BACnet mapping is enabled by default and the device instance ID |
9.4.4 Retry Tab
| configuration项 | Description |
|---|---|
| Unicast Max Retries | Maximum number of automatic retries for failed unicast downlink commands |
| Multicast Max Retries | Maximum number of automatic retries for failed multicast downlink commands |
9.4.5 Reference Tab
This read-only reference table lists all supported attribute fields for each sensor model, including:
- Field name (JSON Key), attribute name, Data Type, Unit, access permission (read/write)
- Value range (minimum/maximum)
- Modbus register offset address and data type
- BACnet object instance offset and object type
Modbus address formula: Runtime Modbus Register Address = 6 fixed header registers + Slave ID × sensor span + field offset
BACnet object instance formula: Runtime BACnet object instance = 2 fixed header objects + Device Instance ID × sensor span + field offset
9.5 LoRaWAN Application Server Status Page
Entry: Menu Network → grpc-bridge → Status
The grpc-bridge service bridges ChirpStack built-in NS device data to IoT Hub, Modbus, BACnet, and other downstream systems. This page displays the connection status and live uplink/downlink data for each device.
9.5.1 Global Statistics
Displays the total number of connected devices, online device count, and offline device count.
9.5.2 Device List
All connected devices are displayed in a table. Supports search by DevEUI and paginated browsing. Main fields:
| Field | Description |
|---|---|
| DevEUI | Unique device identifier |
| Device Name | Device name in ChirpStack |
| Sensor Type | Device model |
| Application ID | ChirpStack application ID this device belongs to |
| Application name | Name of the ChirpStack application this device belongs to |
Action buttons: Edit (modify Modbus/BACnet mapping configuration), Details (view attribute details), Delete
9.5.3 Uplink Data List
Displays the most recently received uplink packets in real time. Fields include: timestamp, DevEUI, DevAddr, frame type, frame data, counter, MAC commands, port, payload length, payload content, and parsed object.
9.5.4 Downlink Queue
Displays the pending downlink packet list. Fields include: timestamp, DevEUI, gateway ID, DevAddr, frame type, frame data, counter, MAC commands, port, payload length, and downlink payload content.
9.5.5 Device Import/Export
- Import Devices: Batch import devices from a CSV/JSON file, specifying tenant, application, and device profile
- Export Devices: Export the current device list to a file for backup or migration
9.6 LoRaWAN Historical Data Query Page
Entry point: Menu Network → grpc-bridge → History
The Historical Data Query page provides query and export functionality for LoRaWAN historical data stored in the PostgreSQL database.
9.6.1 Database Statistics
The top of the page displays statistics for all data tables in tabular form:
| Field | Description |
|---|---|
| Table name | Data table name (e.g., device_join, device_up, device_down) |
| Size | Database table storage space used |
| Record Count | Total records |
| Earliest record | Timestamp of the oldest record |
| Database | PostgreSQL database name |
9.6.2 Query Configuration
| configuration项 | Description |
|---|---|
| DevEUI | Enter the target device DevEUI to query |
| Query Type | By count (recommended): search up to 200, export up to 10,000; by time range: up to 100 results (memory limit) |
| Count Options | 20 / 50 / 100 / 200 / 1000 / 10000 records |
| Time Range | Specify start and end time (earliest queryable time is the oldest record in the database) |
9.6.3 Query Result Tables
Query results are displayed in three separate tables:
Join records: time, DevEUI, TX information (join request log)
Uplink Records: time, DevEUI, DevAddr, frame type, frame data, counter, MAC commands, port, payload length, payload content, parsed object
Downlink Records: time, DevEUI, gateway ID, DevAddr, frame type, frame data, counter, MAC commands, port, payload length, downlink payload content
Each table supports independent pagination (20/50/100 records per page).
9.6.4 Export to Excel
After the query completes, click the Export Excel button to export data from the Join, Uplink, and Downlink tables to an Excel file (.xlsx) for offline analysis and archiving.
Export notes: search preview is limited to 200 records; batch export is limited to 10,000 records. It is recommended to export in segments by time range. Time-range queries are limited to 100 records at a time to prevent memory overflow.