First setup
Getting a freshly flashed pedal onto your Wi-Fi and talking to a console, from the captive portal to your first confirmed mapping.
Updated
A pedal with no stored Wi-Fi credentials sets up its own network, so you never need a cable or a serial console to configure it.
Join the pedal’s own network
On first boot, the pedal starts an access point named pedal-XXXX, where the
last four characters come from its MAC address. Join it from a phone or a
laptop and the setup page should open by itself — the pedal answers the
connectivity checks that iOS, Android and Windows use to detect captive
portals.
If it does not open automatically, browse to any address and you will be redirected.
The portal stays open for five minutes. After that the pedal goes back to trying its stored networks, which stops a pedal left powered on backstage from sitting there as an open access point all night.
Give it your Wi-Fi
Enter your network name and password. The pedal tries each stored network in turn, three times around, with a 15 second timeout each, before falling back to the access point. That matters more than it sounds: it means a pedal that boots before the venue’s router is up will still find the network once it appears.
Use the 2.4 GHz band. The ESP32-C3 has no 5 GHz radio.
Reach it on your network
Once it has joined, the pedal is reachable two ways:
http://pedal-XXXX.local— mDNS, which works on most networkshttp://<its-ip-address>— always works
The configuration page is served by the pedal itself, compressed, from its own flash. There is no CDN and no external request, so it loads identically on a venue network with no internet at all.
Point it at a console
In Setup, add your console:
| Console | Address | Port |
|---|---|---|
| Behringer X32 family | its IP address | 10023 |
| Soundcraft Ui | its IP address | 80 |
You can store up to eight console definitions and keep three candidate addresses for each connection, optionally tied to a particular Wi-Fi network — so a rig that moves between a rehearsal room and a venue can find the right desk without being reconfigured.
When it connects, it starts caching live state from the console. You will see values appear in the Live view.
Make your first mapping
Pick a template, choose a channel, and save. The page waits for the device to confirm the write rather than assuming it landed, which is the same principle the pedal applies to the console.
Then step on it. If the LED goes green, the console really did it.
If you need to start over
Hold the footswitch for three seconds while powering on. That clears stored Wi-Fi credentials and brings the captive portal back. Mappings are not affected.