Preferred way to get signal information

[Aleksander Morgado]

Hey Nick,

> Is there a preferred way to get the signal information from modem manager periodically for the purposes of illuminating some LED’s?  Currently I am running mmcli -m 0 and using grep to strip it down to just the number and taking action based on that value. (—signal-get is not producing any output for me, I’m afraid.) I am just wondering if there is a preferred solution out there already that I am missing.
>

In order to have --signal-get start reporting values, you first need
to set it up specifying how often you want those values reported, e.g.
--signal-setup=30 for every 30s. After that, you can use --signal-get
and get more detailed values.

> Also, I see that uqmi has some more signal values available, but I have witnessed that running uqmi while modem manager controls a modem could cause modem manager to lose access to the modem.  I vaguely recall a whisper that there may be a preferred way to run uqmi commands from within modem manager, is that correct?  Is there a way to get the full uqmi —get-signal-info information from mmcli directly?  I suppose I could always just run the AT commands to get the signal info via modem manager.
>

I guess you're referring to "running QMI commands" while MM is
running. Not with uqmi, but you can run qmicli commands while MM is
running by adding an additional "-p" to the qmicli command you would
use. uqmi AFAIK doesn't play well with MM+libqmi.

-- 
Aleksander
https://aleksander.es