Thanks Daniele,

It seems the disable command is not much different than "--simple-disconnect". 
The disable command as it stands today is a bit misleading because it gives an 
impression that modem is disabled (the state is reported "disabled" in mmcli -m 
0 output) but modem is actually still registered on a network.

Amol
________________________________
From: Daniele Palmas <dnl...@gmail.com>
Sent: Friday, July 19, 2024 4:00 PM
To: Amol Lad <amol....@4rf.com>
Cc: ModemManager (development) <modemmanager-devel@lists.freedesktop.org>
Subject: Re: mmcli --disable command

Hi Amol,

Il giorno sab 13 lug 2024 alle ore 08:50 Amol Lad <amol....@4rf.com> ha scritto:
>
> Hi,
>
> I'm trying this with ModemManager release 1.22.0 with Telit FN990A28 modem 
> (but it might be true for other modems as well).
>
> # mmcli -m 0 --disable
> successfully disabled the modem
> # mmcli -m 0 --command=AT+COPS?
> response: '+COPS: 0,0,"IND airtel",13'
>
> The modem stays registered with the network (and also receives SMS) even 
> after disabling the modem. Is the expected?

No dms set operating mode is sent, so the result is expected. If you
want the modem to deregister you should then send:

# mmcli -m 0 --set-power-state-low

I don't remember if this is a behavioral change happened in 1.22.0, or
if it's always been as it is (maybe a look at the git log could help).

Regards,
Daniele

>
> Thanks,
> Amol

Reply via email to