MicroPython Forum (Archive)

In the default MicroPython build for the ESP8266, the AP interface is enabled by default via modules/_boot.py and modules/inisetup.py and I was wondering if there is a reason for this. It doesn't seem you can do much with it without first doing some other initial setup tasks via a serial REPL (like enabling webrepl).

JennaSys wrote: ↑

Sat Jul 24, 2021 11:42 pm

In the default MicroPython build for the ESP8266, the AP interface is enabled by default via modules/_boot.py and modules/inisetup.py and I was wondering if there is a reason for this. It doesn't seem you can do much with it without first doing some other initial setup tasks via a serial REPL (like enabling webrepl).

I'm not sure, unfortunately there's no information in the git history for that code. I notice that ESP32 doesn't do this (and this is likely because on ESP32 the wifi configuration is not persistent).

It's quite neat to be able to just run "import webrepl_setup" and then you're all set to go...

Yea I could definitely see it as a benefit for doing an initial setup wirelessly if webrepl was also enabled. I seem to recall reading somewhere that it used to be, so it might be that the AP being enabled is an artifact of that.

I put the question out there just to see if there was some other feature or workflow I was unaware of where having AP enabled by default makes sense.