[Mudi 7 / GL-E5800, firmware 4.10.0 beta2] Live radio metrics (RSRP/SINR/RSRQ) never reach ubus — modem_signal enabled but registers no ubus object

Router
1

On GL-E5800 running 4.10.0 beta2, live signal metrics (RSRP/SINR/RSRQ/RSSI) are absent from every cellular.* ubus object, even though the modem is fully registered and the radio returns those values directly over AT. This breaks any consumer that reads signal quality from ubus.

Environment

  • Device: GL-E5800 (Mudi 7)

  • Firmware: 4.10.0 beta2

  • Carrier: A1 (AT), NR5G-NSA, active SIM slot 1, data up (rmnet, APN A1.net)

  • Modem fully registered: AT+CREG? -> 0,1, AT+COPS? -> 0,0,"A1",13, AT+CPIN? -> READY

Observed vs expected

The radio HAS the values (direct AT works):

AT+QCSQ
+QCSQ: "LTE",-73,-101,9,-8      # RSSI -73, RSRP -101, RSRQ 9, SINR -8

But ubus exposes none of them:

  • ubus call cellular.modem status '{"bus":"cpu"}' -> only slot-switch fields, no rsrp/sinr/band

  • ubus call cellular.modem info '{"bus":"cpu"}' -> only static band capability list

  • ubus call cellular.network info '{"bus":"cpu"}' -> has dl_bandwidth/ul_bandwidth but no cell_info and no rsrp/sinr

  • ubus call cellular.status info / cellular.collect info -> no signal fields

Suspected cause

/etc/init.d/modem_signal is enabled and running, but registers no ubus object:

ubus call modem_signal status
Command failed: Not found

It looks like the AT->ubus signal poller that should populate the live metrics (historically under cellular.network -> networks[].cell_info) is not publishing on this build. A reboot does not fix it (metrics stay absent after a clean boot).

Impact

Any tool reading signal quality from ubus (GL UI signal display, third-party dashboards) shows null/empty metrics. Battery, SIM, cell-lock and data all work — only the live RSRP/SINR/RSRQ telemetry is missing.

Repro

  1. E5800 on 4.10.0 beta2, SIM registered, data up.

  2. ubus call cellular.network info '{"bus":"cpu"}' — note absence of cell_info/rsrp/sinr.

  3. AT+QCSQ via the modem AT port — values are present.

  4. ubus call modem_signal status — "Not found".

  5. Reboot — no change.

Question @will.qiu

Has the signal telemetry path changed in 4.10.x (new ubus object / field names), or is modem_signal failing to register its object on the SDX72/E5800 build? Where are live RSRP/SINR expected to surface in ubus on this firmware?

2

Hi,

Thank you for the report.

Yes, since we refactored some of the cellular-related features in v4.10 (users who have already tested it may have noticed significant changes in the related interface), the ubus interfaces have also been adjusted.

Currently, if you want to retrieve the SIM card signal information, please use the following ubus objects/methods:

# Check the currently used SIM slot:
ubus call cellular.modem status '{"bus":"cpu"}' | jsonfilter -e '@.current_sim_slot'

# Check the signal information for the corresponding SIM slot:
ubus call cellular.network cell_info '{"bus":"cpu","slot":2}'

image
image1870×1186 95.5 KB

Additionally, the GL UI should have already been adjusted accordingly and should now be able to display the signal values correctly.

image
image1289×905 38.5 KB

Are you encountering any issues with signal value display on E5800 v4.10? If so, could you please provide the exact path and screenshots so we can better investigate?

4

Hi Will, thank you so much — that solved it perfectly! :folded_hands:

I confirmed it on my E5800 (4.10.0 beta2): the new method gives me everything:

ubus call cellular.network cell_info '{"bus":"cpu","slot":1}'

returns a signal[] array with rsrp/rsrq/rssi/sinr and the *_level fields, and the GL UI signal display is working great here too.

In case it helps anyone else who finds this thread with a third-party dashboard showing empty signal: the values just moved to this new cell_info method in 4.10, so tools reading the older location need a small update. Nothing wrong with the firmware at all — just the new interface.

Thanks again for the quick and clear answer, really appreciate it!

1 Like