Posts: 12
Threads: 2
Joined: Jun 2026
Is there a way to force the WiModem232 Pro to use a specific Wi-Fi channel or access point MAC? My home network supports roaming with one SSID across multiple access points, and my WiModem seems to be stuck on a channel that is associated with a more distant AP with a weaker signal. I think this might be the cause of some performance issues I've been seeing.
I've tried using the AT*NS command to associate with a specific AP but the WiModem remains on the weaker channel.
Thanks!
Posts: 2,989
Threads: 149
Joined: Nov 2013
The channel is selected based on traffic. I am not sure there is a way in the WiFi stack to force a channel. I will look into it.
Posts: 12
Threads: 2
Joined: Jun 2026
07-28-2026, 04:57 AM
(This post was last modified: 07-29-2026, 01:20 AM by screwtop.)
Thanks! My workaround for now has been to run an RF scan on the distant AP, which kicked off any connected devices. That's bumped the troublesome WiModem to a nearby channel/AP.
I am seeing a strange pattern in the ping times for the WiModem devices, though: a clear sawtooth/ramp with a period of about 5 seconds and a range of about 15-100 ms. Both my WiModems show this pattern (gping graph):
Code:
192.168.5.151 (192.168.5.151) last 14.1ms min 14.1ms max 135ms avg 66.703ms jtr 806.s p95 112ms t/o 0
129.096ms.
.
. .
. .
. .
109.695ms. .
. ..
. . . ... .. . .
. .. .. ... . . .. ..
. .... . . . . . . . . . . . . .
90.294ms . . . .. . . . . . . . . . . . .
. . . . . . . . . . . . . ... .
. .. . . . . . . .. . .... . . . .
. . . . . . . . .. . . . .. . . .
. .. . .. . .. . . . . . . . . . .
70.893ms . . . . . . . . .. . . . . .
. . . . . . . . . . . . . .
. .. . . . . . . . . . .. .
. . . . . .. . . . . . . .
. . . . . . . . . .. . . .
51.492ms . . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . .. . . . . . . . . .
. . . . . . . . . . . .. .
.. . . . . . .. . .. . . .
32.091ms . ... . . . . . . . . .
. ... . .. . . . . .. .
. . .. .. .. .. .
. . . . . . .
12.69ms .
...................................................................................................................................
23:21:21 23:21:36 23:21:51
For comparison, here's the pattern for a Chromecast on the same AP:
Code:
192.168.5.192 (192.168.5.192) last 1.43ms min 1.25ms max 39.1ms avg 3.75ms jtr 254.s p95 13.4ms t/o 1
37.023ms. .
. . .
. . .
. . .
31.04ms . . .
. . ..
. . . ..
25.057ms. . . ..
. . . .. .
. . . .. .
19.074ms. . .. .. .
. . .. .. .
. . . . . . .. .
13.091ms. . .. . . . . . .. .
.. .. . . .. . .. . . . . . . ..
.. .. . .. . .. . .. . . .. . . . ..
7.108ms .. . . .. . . . . .. .. . . . . . . . . . . . . . ..
. . . . . . .. . . . . . . .. . . . . . .... . . . . . .... . .. .
. ..... .. .. .. ... ......... ..... ............ ...... ......... . ....... ........... .... . .. ............. ....
1.125ms .
..................................................................................................................................
23:34:55 23:35:10 23:35:25
The sawtooth ping pattern is still there when the WiModem is connected, but only while idle, so maybe it's not a problem and is normal (power-saving?) behaviour.
Posts: 2,989
Threads: 149
Joined: Nov 2013
I am not sure, that is all handled automatically through the WiFi stack that is provided with the ESP32.
Posts: 12
Threads: 2
Joined: Jun 2026
I see, thank you. From further reading it seems it could be a power-saving measure: on ESP-IDF at least, the default WIFI_PS_MIN_MODEM power state offers reduced power consumption with higher latency, while WIFI_PS_NONE trades off the other way. I don't believe the WiModem provides an AT command for changing this, only AT*MODE for toggling the radio.
It's useful to know that the ping times are not indicative of the true latency in active use.