A browser-based setup tool for the OpenHome Raspberry Pi DevKit smart speaker. Pairs the speaker with your Wi-Fi and links it to your OpenHome account — entirely from your browser, over Bluetooth.
Live tool: https://devkit.shaal.devSource: this repository.
OpenHome ships an iOS/Android app for DevKit setup, and a Python BLE script for users who can't install the app. The script (scripts/devkit_setup.py) requires installing Python, a virtualenv, and bleak, and doesn't work on WSL because WSL has no Bluetooth. This page replaces it with a single static HTML file you can open in a browser.
It speaks the same BLE GATT protocol as OpenHome's Pi firmware:
- Discovers devices advertising
openhome_<mac> - Triggers a Wi-Fi scan, lists networks with signal strength
- Sends Wi-Fi credentials and watches the connection state machine
- Sends your OpenHome API key/credential and shows the verification result
- Power on your DevKit speaker and wait ~1 minute.
- In Chrome or Edge on a desktop, or Chrome on Android, open https://devkit.shaal.dev.
- Click Connect via Bluetooth and pick the
openhome_…device. - Scan for Wi-Fi → pick your network → enter password.
- Paste your OpenHome credential and submit.
Web Bluetooth is required:
| Browser | Supported |
|---|---|
| Chrome (desktop, Android) | ✓ |
| Edge (desktop) | ✓ |
| Opera | ✓ |
| Firefox | ✗ |
| Safari (macOS, iOS) | ✗ |
| iOS Chrome / Edge | ✗ (uses Safari engine) |
This is a browser-platform limitation, not something this tool can work around.
You're handing this page your Wi-Fi password and an account credential. Here's how to verify it doesn't do anything sneaky with them:
- Read the source. The whole tool is one file:
index.html. No build step, no minification, no bundler, no CDN dependencies. What's in the repo is what runs in your browser. View the served page's source (Ctrl+U) and diff it against the file in this repo if you want to be thorough. - Watch the network. Open DevTools → Network tab before clicking Connect. You will see exactly zero outbound HTTP requests after page load. All traffic is Bluetooth GATT, between your browser and the speaker.
- Content-Security-Policy enforces this.
_headerssetsconnect-src 'none', which means the browser will refuse to make any network request from this page. Even if the page were compromised, it could not exfiltrate anything to a remote server. - Deployments are tied to commits. Cloudflare Pages builds from this GitHub repo. Every deploy maps to a specific commit hash visible in Cloudflare's deployment log. The
mainbranch is the source of truth. - No external dependencies. No fonts, no analytics, no Tailwind, no jQuery. Removing third-party trust removes whole classes of supply-chain risk.
If you find something concerning, please open an issue.
Service UUID: 12345678-1234-5678-1234-56789abcdef0
| Characteristic | UUID | Use |
|---|---|---|
| Wi-Fi Scan | …abcdef1 | Write 0x01 to trigger; receive networks via notify |
| Wi-Fi Connect | …abcdef2 | Write {"ssid","password"} JSON |
| Wi-Fi Status | …abcdef3 | Read {"state","message"} JSON |
| API Key | …abcdef4 | Write {"api_key"} JSON; verification result via notify |
| Heartbeat | …abcdef5 | Notify-only; subscribed to keep the link alive |
The notification state machines (scan, status, API key) match OpenHome's Python reference client.
index.html The setup tool. Self-contained.
_headers Cloudflare Pages security headers.
scripts/devkit_setup.py OpenHome's original Python BLE client (for reference).
- Fork this repo.
- In Cloudflare Pages, Connect to Git → pick your fork.
- Build command: (empty). Output directory:
/. - Add your custom domain in the Pages project settings.
Cloudflare Pages will redeploy on every push to main.
MIT.
- The OpenHome team for the DevKit and the underlying BLE firmware protocol.
- This page was created by an OpenHome DevKit user as a community contribution and is not officially affiliated with OpenHome.