Dashboard & Monitoring
Relevant source files
The following files were used as context for generating this wiki page:
The Dashboard & Monitoring system provides a centralized interface for observing the real-time health and performance of OpenWrt routers. It aggregates metrics including CPU load, memory usage, network throughput, and wireless signal strength into a single view for administrative oversight.
Sources: README.md:14-16, full_description.txt:13-15
System Health & Metrics
The application retrieves core system data to visualize the router's operational state. Key metrics include uptime, local time, and system identification.
System Metadata
System information is derived from the UCI configuration, specifically the system type. This includes the hostname, timezone, and a user-defined description.
| Field | Type | Description |
|---|---|---|
| hostname | String | The network name of the router |
| description | String | A short summary of the router's purpose |
| timezone | String | The configured time zone (e.g., UTC) |
Sources: assets/mock/uci_system.json:4-15, full_description.txt:23-23
Performance Monitoring
The monitoring system tracks hardware resource consumption. This data allows the dashboard to display interactive charts for performance analysis.
The diagram shows the flow of performance data from the hardware to the mobile dashboard.
Sources: README.md:14-15, full_description.txt:13-15
Network Interface Monitoring
Monitoring covers both physical and logical interfaces, capturing traffic statistics and connection states.
Interface Status
The app parses interface dumps to determine if a connection is up, available, or pending. It identifies the underlying physical device (e.g., eth0, br-lan) and the protocol used (e.g., dhcp, static).
Sources: assets/mock/interface_dump.json:3-15, README.md:18-19
Addressing & Routing
For active interfaces, the system monitors IPv4 and IPv6 assignments along with default gateways.
Sources: assets/mock/interface_dump.json:16-35
Wireless & Client Monitoring
Wireless monitoring provides visibility into radio performance and the specific behavior of connected stations.
Radio & WiFi State
The system tracks radio-level metrics such as frequency, channel, transmit power, and noise floor. It distinguishes between different hardware modes (e.g., 802.11ac) and HT/VHT modes.
Sources: assets/mock/wireless_devices.json:5-18, README.md:18-19
Connected Clients
Client monitoring combines data from DHCP leases and wireless association lists to provide a comprehensive view of network participants.
The sequence diagram illustrates how the application correlates DHCP information with wireless signal data to populate the client list.
Sources: assets/mock/dhcp_leases.json:2-3, assets/mock/assoclist_wlan0.json:4-20, full_description.txt:17-18
Client Metrics
The following data points are monitored for every connected wireless client:
- Signal Strength: Measured in dBm (e.g., -56 dBm).
- Throughput: Current RX/TX bitrates and total bytes transferred.
- Connectivity: Total connected time and time since last activity (inactive time).
- Hardware Capabilities: MCS index, NSS, and use of Short Guard Interval (SGI).
Sources: assets/mock/assoclist_wlan0.json:4-40, README.md:18-19
Connectivity Architecture
The monitoring system relies on the LuCI RPC protocol over HTTP or HTTPS. It uses a secure storage mechanism for credentials and handles real-time updates through parallel requests.
Sources: README.md:31-33, PRIVACY_POLICY.md:12-16
The Dashboard & Monitoring module serves as the primary diagnostic tool in LuCI Mobile, enabling users to verify router health and network performance through real-time data aggregation and visualization.