1 × Home Assistant Voice Preview Edition
Requiredboard
Main board or device for this build.
Build: Home Assistant Voice Preview Edition
A working Muse Gadgets: ESP32 Device SDK (Status) build on Home Assistant Voice Preview Edition, paired to your Muse account and ready for first prompts.
Status~$691-3 hr setup
1
Get the parts
You need the board and any build-specific accessories before flashing or pairing.
Buy from home-assistant.io
1 × USB-C power supply (5 V / 2 A)
Requiredpart
The Voice PE is USB-C powered; a phone charger that supplies 5 V / 2 A works.
1 × USB-C data cable
Requiredpart
Must carry data, not just charge. Most flashing problems are charge-only cables.
Hackshop never buys for you. Links open the store.
2
Get your Muse SDK token
Muse gadgets pair with your account by using a private SDK token.
Create a token at gadgets.muse.ai > Account > SDK tokens (https://gadgets.muse.ai/settings/sdk-tokens). It starts with mgst_. For this ESP32 build, set CONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN" in build-home-assistant-voice/sdkconfig after the board build command has created that file, then run the build command again. idf.py menuconfig > ESP32 Device SDK > Muse Gadgets SDK token is the interactive alternative. Never commit the real token or paste it anywhere public.
3
Flash the firmware
The board needs the Muse ESP32 firmware configured with your SDK token.
Let your agent do it
Give your coding agent the build brief at https://www.hackshop.dev/build/home-assistant-voice-pe/build.md. Tell it to keep the token private, use mgst_YOUR_TOKEN as the placeholder, and find the serial port before flashing. On macOS it should run ls /dev/cu.usbmodem* /dev/cu.usbserial*; on Linux, ls /dev/ttyACM* /dev/ttyUSB*; on Windows, use Device Manager to find the COM port, then run commands in the ESP-IDF shell.
Do it yourself
Install ESP-IDF v6.0.1 and only the esp32s3 target for this board. Muse's ESP32 README verifies macOS and Linux. Windows is not documented by the Muse SDK; if you use it, install ESP-IDF v6.0.1 with Espressif's Windows installer and run commands in the ESP-IDF shell. Clone the Muse Gadget SDK, run tools/board.sh home-assistant-voice build once to create build-home-assistant-voice/sdkconfig, set CONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN" in that file, run tools/board.sh home-assistant-voice build again, then flash. If flashing cannot connect, hold BOOT, tap RESET, then release BOOT.
git clone -b v6.0.1 --recursive https://github.com/espressif/esp-idf.git ~/esp/esp-idf-v6
~/esp/esp-idf-v6/install.sh esp32s3
. ~/esp/esp-idf-v6/export.sh
git clone https://github.com/facebookincubator/muse-gadget-sdk
cd muse-gadget-sdk/esp32
tools/board.sh home-assistant-voice build
printf '\nCONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN"\n' >> build-home-assistant-voice/sdkconfig
tools/board.sh home-assistant-voice build
ls /dev/cu.usbmodem* /dev/cu.usbserial* 2>/dev/null || ls /dev/ttyACM* /dev/ttyUSB* 2>/dev/null
tools/board.sh home-assistant-voice flash-monitor PORT4
Pair it with the Muse app
Pairing links the freshly flashed board to your Muse account.
In the Muse app, turn on Settings > Devices > Developer mode, then Settings > Devices > Add Device (+). Pick MuseGadget-XXXXXX and press the center button when the LED ring breathes blue. Green means connected. Status meanings: orange = ready for setup, blue breathing = press the button, blue = joining Wi-Fi and connecting, green = connected, yellow blinking = reconnecting, purple = unpaired, red blinking = error. Hold the button for 5 seconds to reset pairing.
5
Put it together
A physical agent body needs to sit safely, keep the cable clear and leave controls reachable.
Put the board in its stand, case or a stable spot on the desk. Route the USB-C cable through the slot or open edge, power it, and check that the buttons and display are reachable.
6
Try it
A first prompt proves the device is paired, reachable, and useful for the project.
“(Press the button) What's on my calendar tomorrow?”“(Press the button) Turn the volume down.”
Hand it to your agent
# Build: Home Assistant Voice Preview Edition as a Muse gadget
## Goal
A working Muse Gadgets: ESP32 Device SDK (Status) build on Home Assistant Voice Preview Edition, paired to your Muse account and ready for first prompts.
## Hardware
- [Home Assistant Voice Preview Edition](https://www.home-assistant.io/voice-pe/) x1 (required, board): Main board or device for this build.
- [USB-C power supply (5 V / 2 A)](https://www.amazon.com/s?k=USB-C%20power%20adapter%205V%202A) x1 (required, part): The Voice PE is USB-C powered; a phone charger that supplies 5 V / 2 A works.
- [USB-C data cable](https://www.amazon.com/s?k=USB-C%20data%20cable) x1 (required, part): Must carry data, not just charge. Most flashing problems are charge-only cables.
## Shopping list (ask before buying)
- Home Assistant Voice Preview Edition x1 (required, est. $69; buy: https://www.home-assistant.io/voice-pe/)Caveats + terms
Personal, non-commercial use with your own Muse account. A token can be linked to at most 50 devices. You may not put it in any device you sell, advertise, or list publicly or in a marketplace or app store; other distribution needs Meta's written permission. Provided as-is; Meta can change, withdraw or revoke access at any time. Read terms.
- The home-network tunnel lets Muse reach devices on your LAN that expose a local HTTP API. Treat it like giving the agent a foothold on your network.
- Pairing has no manufacturer verification and can't prevent an active man-in-the-middle attack.
- Builds are signed with the included development key and never enable Secure Boot. Enable NVS encryption (CONFIG_HOMEHUB_NVS_ENCRYPTION).
- Custom ESP32 commands are not a documented API yet: the command set (display.draw_url, sensors.read, camera.capture, ...) is hardcoded in main/app.c.