WakeMyPC
Companion CLI for wakemypc.com.
Runs on your computer, talks to a Pi Pico W (or W 2) over USB, and your wakemypc.com account over HTTPS.
Install
Create a virtual environment, if you want.
python -m venv .venv
Activate virtual environment.
source .venv/bin/activate #linux/MacOS
.venv\Scripts\Activate.bat #Command prompt
.\.venv\Scripts\Activate.ps1 #Powershell
Use pip to install:
pip install wakemypc
Verify:
wakemypc --help
On Linux you may need to add yourself to the dialout group so you can talk to the Pico's serial port without sudo:
sudo usermod -a -G dialout $USER
# log out and back in
What it does
wakemypc detect # list connected Picos (flashed and BOOTSEL-mode)
wakemypc flash --uf2 … # write MicroPython firmware to a BOOTSEL Pico
wakemypc upload … # copy wakemypc-firmware .py files onto the Pico
wakemypc provision … # write WiFi creds + server URL to secrets.json
wakemypc register … # register with the server, get a device token
wakemypc restart # soft-reboot the Pico (or reboot into BOOTSEL)
wakemypc identify # blink the Pico's LED to find it physically usefull when multiple pico(s) connected
wakemypc status # read WiFi state + secrets summary over USB
wakemypc logs # Read logs from Pico over USB serial connection
wakemypc --help and wakemypc <subcommand> --help have the full reference.
First Setup
The most common flow for a brand new Pico is:
# 1) Plug Pico in BOOTSEL mode (hold BOOTSEL while connecting USB).
wakemypc detect
wakemypc flash --uf2 RPI_PICO2_W-…uf2
# 2) Plug the now-flashed Pico to upload latest firmware from GitHub.
wakemypc upload --github
# 3) Configure WiFi + server.
wakemypc provision --add-new-wifi --wifi-ssid HomeWiFi --wifi-pass mypassword
# 4) Register on wakemypc.com using browser login
wakemypc register --oauth --name "My Pico"
Auth Token registeration (Manual)
Register the token offline when
- You obtained the auth token by manually registering Pico device on dashboard
wakemypc register --token <Token>
This doesn't require any username or password. The Pico will automatically communicate with the server if the Pico is registered on Transmitters on the dashboard.
Token rotation
In the event that you'd like to rotate the auth token used while authenticating with the server.
Two modes:
wakemypc register --username … --password … --rotate # rotate existing
wakemypc register --token <T> # offline, no server call
--rotate calls the server's rotate-token endpoint and writes the new token to the Pico in one step.
--token <T> skips the server -- handy when you've already rotated through the dashboard and just need to push the new token over USB.
What this CLI does NOT do
- It does not need root / sudo (apart from the one-time
dialoutgroup add on Linux). - It does not support Pico Token registeration through dashboard yet. The only network calls go to the api url with
usernameandpasswordthat you pass toregister. - It does not store your password. Login uses the JWT the api server returns; the password is forwarded once and then forgotten.
License
Source-available, non-commercial. PolyForm Noncommercial 1.0.0.
You can run it, audit it, modify it, and share patches. You can't sell it or run a paid service on top of it. Patches welcome.
Metadata
Release files for wakemypc 1.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wakemypc-1.2.4.tar.gz | 47.0 kB | With provenance | Details for wakemypc-1.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wakemypc-1.2.4-py3-none-any.whl | Python 3 | none | any | Details for wakemypc-1.2.4-py3-none-any.whl |
Total release size: 96.5 kB
Release files / wakemypc-1.2.4.tar.gz
| Download URL | wakemypc-1.2.4.tar.gz |
|---|---|
| Size | 47.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7d2d81e97b08697c7505276faed62b37f801d8911e6bdd69f1bd31da349fcd0f
|
|
BLAKE2b-256 checksum How to use checksums |
24315206ffd960d02bed1bc3e1249beef7ff553828ef1fa79ea35f3ff231e2af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 5, 2026.
Transparency logRelease files / wakemypc-1.2.4-py3-none-any.whl
| Download URL | wakemypc-1.2.4-py3-none-any.whl |
|---|---|
| Size | 49.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a37be47928331c497320223aedcce9e9db1f755cc3cbb024f869fb59d670c31
|
|
BLAKE2b-256 checksum How to use checksums |
1a97888fc8b8b6c8d34b3d5fe44b6ad4c07408d128f646046fb96612b509e635
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 5, 2026.
Transparency logSecurity for wakemypc 1.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wakemypc-1.2.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.