In the last few days, I downloaded the OLED-P4wnP1 ALOA .img file and flashed it onto a MicroSD card.

After tinkering around with various WiFi-config Python scripts without success, I wandered toward the P4wnP1 CLI.

The wrapper script scans WiFi, has user choose, then shows this Enter Password screen

P4wnP1 CLI (Simply amazing)

Within a minute or two, I was able to instantly connect my P4wnP1 to my WiFi network using P4wnP1 CLI.

For me, this was a huge success in the scope of my current goal:  Allow a user to connect to a WiFi network using only the buttons on the front of the OLED P4wnP1.

Since I've essentially already put the pieces together to get the WiFi network name and ask the user for the WiFi password, getting the P4wnP1 to use that info to connect to WiFi was the last big piece of the process.


P4wnP1 Connect to WiFi Using OLED Buttons ONLY

To review, here's the flow of how I see the OLED P4wnP1 connect-to-WiFi process happening:

WiFi SSID scan results
  1. Scan for WiFi networks
      1. [DONE] I just finished the "core" of this function last night.  The "iwlist-parser" script from Github does the actual WiFi scanning using the "iwlist" command.  I modified the iwlist-parser script to export the Top 10 highest-signal WiFi networks (sorted by signal strength) to a text file.

    sudo python3 wlan0

  2. Display WiFi networks on OLED screen
      1. [DONE] After the scanned WiFi networks are sent to a text file, my custom-written "oledHorizMenu" Python script reads the same text file and displays the contents of the file on the OLED screen.

    sudo python3

  3. User presses a physical button on OLED screen to select WiFi network name
    1. [DONE][IN PROGRESS] Have the script return the WiFi network name - and/or replace the text file contents with just the 1 selected WiFi network name.  Selected WiFi network name is sent to ssid.txt.
  4. [TO DO] Ask user for WiFi password using my custom-written OLED-joystick input script
  5. [TO DO] Use P4wnP1-CLI to connect P4wnP1 to WiFi using selected WiFi network name and user-submitted password
  6. [TO DO] Test connection / show connection status using WiFi icon.
  7. [BONUS] Add CLI speedtest function


Progress made today:


WiFi Scan-and-Select Linux-CLI DEBUGGING Workflow:

  1. python3
  2. tail ssids.txt  # To make sure the scan script sent to txt properly
  3. python3  # Now use the joystick to select a network
  4. Ctrl+C to close the display program
  5. tail ssid.txt  # To make sure the display script sent to txt properly


To Do:  Write a wrapper script to execute Steps 1 and 3 above, in order to combine everything into 1 easy script.


Update 1:  Added code to skip empty SSIDs

if myessid == '':
print('Skipping Empty SSID when writing to file')
elif myessid != '':
f.write(myessid + '\n')


And I changed the script in a way that writes the SSID to text file without extra info (such as Signal strength).

Ex:  Now shows "NETGEAR69"  instead of "1) NETGEAR69 -53".

Since the list is auto-sorted by signal strength anyway, it's unnecessary and confusing to display the signal strength.  That makes it too complex and can hide some of the SSID.

So the WiFi connect command can simply read the text file without stripping or removing any characters.


Update 2:  Wrapper Script

I made a python script which opens a subprocess to launch and

So now the WiFi Scan-and-Select package includes 3 files:

Just run the command below to launch the whole shebang:

sudo python3


The result is the user-selected SSID written to ssid.txt in the current folder.


Here's where I'm currently at in the scope of the Connect-OLEDP4wnP1-to-WiFi project:

0. DONE - Take the iwlist-parser script, output the top 10 network SSIDs to ssids.txt file.
1. DONE - Take oledhorizmenu and load the ssids.txt file as the menu
2. DONE - Change oledhorizmenu to show the FIRST 3 lines of txt file instead of LAST
3. DONE - On center button press, write ssid to ssid.txt

3B.  Make a wrapper script ( to call all the other scripts (,, etc)

4. IN PROGRESS - Launch the oledp4wnp1 input script from within
5. TO DO - Have the input script temporarily store the password in a variable
5. TO DO - From within the input script, launch the "P4wnP1_cli wifi set sta SSIDgoeshere PWhere or whatever" to connect to the wifi!


Replaced Code with Loop in

I also replaced a long chunk of 10 chunks of code with ONE loop.  This also completely circumented the "index out of range" python error I kept getting (when trying to access a variable that wasn't there).  Hooray for loops!


Update 3:  Added into!

Now the wrapper script scans, selects, and then asks for password.

The wrapper script scans, has user choose, then shows this Enter Password screen

Now just to get the input script to store the Password in a variable.

Then run the P4wnP1_CLI command to connect to WiFi!


Then run a ping command to see if Google responds?

If so, say "Connected".  If not, then blah.


Update 4:  Boned the WiFi & ReFlashing My OLED P4wnP1 Image (Do over)

On trying to complete the Connect-to-WiFi process, my p4wnp1 installation was unable to properly manage the WiFi connection.  This was true even though just a few hours earlier it worked fine.

So my conclusion was that I changed some p4wnp1 setting which boned the WiFi.

I collected my python scripts, flashed a new image of a p4wnp1 installation that I know works onto a fresh SD card, and I'm currently deploying the Connect-to-Wifi environment onto that new installation.

I edited the BeBox file by adding a new menu item under Wireless Things.

The new menu item is "Connect to WiFi"

I told the file to load my connect-to-wifi scripts (in the same exact way my script does).

But I needed to install a dependency:  numpy (pip3 install numpy)

I'm currently waiting for that to finish (takes forever since it builds a wheel or whatever, which is slow on RPi 0 W).  Building/installing numpy on Raspberry Pi 0 W is so slow that I may re-build the .img file after it's done, so I don't have to do it again.

Building numpy takes for. Ever.

After this finishes, I'll complete moving the connect-to-wifi package to the fresh BeBox install.  I do this by testing the script in /P4wnP1/myscripts/oledhorizmenu/ and see if there are any unmet dependences (other than numpy) left to be installed.  Then I'll move the connect-to-WiFi script "package" to /P4wnP1/ and test it there.

Finally, test it using the actual BeBox menu script.

Hopefully the BeBox menu actually launches my scripts.

Hopefully I get further than this with BeBox and having it launch my scripts


Update 5:  Set Up My WiFi Connect Package in P4wnP1 BeBox + Test CLI

I currently have 2 mini objectives:


After installing numpy on Bebox's OLEDP4wnP1, install fontawesome and PIL (Pillow):


The Raspberry Pi Zero W finally finished installing Pillow, fontawesome, and numpy on BeBox P4wnP1 OLED.

I ran my script-wrapper ( and it executed seemingly-well, except the BeBox OLED menu script interfered with it (wrestles with it).  Basically I need to kill the process.  Then run my script.

So here's how to kill a process in Python by name:

How to Kill BeBoX Process

ps aux | grep



Then run the "ps aux..." part again to make sure was killed.

Finally, I re-ran my script - and - Voila!  It worked!


At this point, I want to do two things:

1) Test P4wnP1_cli

2) Insert the successfully-tested command into

Result 1: Test P4wnP1_cli

Manually-Running P4wnP1_cli to Connect to WiFi Worked!

I tested this command:

P4wnP1_cli wifi set sta -n -s MyWiFiNetworkName -k MyPassword

and almost instantly received this output:

mode:STA_CONNECTED channel:4 ssid:"home"..

Additionally, the P4wnP1 ALOA web GUI auto-refreshed to show the new WiFi network name (and password - eesh - so be careful on that).

OLED P4wnP1 successful at connecting to WiFi in client mode via CLI

Note:  I used my Android Google Pixel 3 phone's WiFi hotspot for this test.  I made the WiFi network name nice and short ("home") so it's quick and easy to type in.  Keep this in mind (time to enter info using joystick) when creating your WiFi hotspot, if you choose to do that instead of connect P4wnP1 to a land-line type WiFi network.

Last, but not least, I ran a ping on to make sure DNS works right:

ping -c3


Result 2:  (IN PROGRESS) Add the p4wnp1_cli command into

Not yet done.  TBD.

This would accomplish the goal of connecting P4wnP1 to WiFi, but it would skip past the BeBox GUI.  That's fine though - could even run BeBox GUI after connecting to WiFi.


Extra: Testing BeBox's with My WiFi-Connect Scripts

So I tried using BeBox's to run my scripts, but nothing happened.

I'll investigate in the morning and start a new post on it.  Hopefully tomorrow I at least get my script to successfully run the P4wnP1_cli command to connect RPi 0 W to WiFi using only the OLED buttons!