<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi folks,<br>
<br>
So, I'm trying to play "customer" with the 3.1 module, and have
confirmed :) the issue with killing off WiFi by enabling client + AP
mode. Tried to recover by using the USB console and issuing a
module factory reset command, but that didn't enable wifi because
the ssid passkey wasn't set up. Fixed that (again, usb console) and
got back to what I think was "factory" state. <br>
<br>
Also got stuck trying to navigate an OTA update. Can't connect to
the Internet with an AP-only WiFi config. Trying to configure
AP+Client killed things off, so a bit gun-shy there. If I play
customer without a means to play with an SD card, I can't apparently
do the update.<br>
<br>
The key to both of these is to actively configure a client wifi
network before messing around with practically anything else, but
that's not obvious in the normal workflow of setting up the module.
Can we clarify that in either the documentation, or (preferably) in
the Webserver UI? I think the key here is that configuring
AP+Client needs to <i>first</i> have the Client config set, because
one never has a wide-open WiFi network at home (for scan "any" to
work).<br>
<br>
That was topic #1...<br>
<br>
Topic #2, once I did get the module on the home network and hit the
OTA Flash button, it seemed to never complete (looking just at the
web page). As a developer, I had a USB console running on the side,
and saw the reason was a continuous stream of queue overflow
messages. Rebooted (ignoring the warning not to do so) the module
and tried again; same result, though apparently the updates actually
did work (it shows I'm on version 3.1.003). Rebooting the module
stopped the queue overflows, i.e. they weren't associated with
normal operation. Is something not getting cleaned up after the OTA
process completes?<br>
<br>
Greg<br>
<br>
<br>
<br>
</body>
</html>