Main board or device for this build.
Build: Seeed SenseCAP Indicator (D1 series)
About 30-45 minutes · needs a Mac or PC and a USB-C data cable · some Terminal, or let your agent do it
Intermediate · extra stepsIts air sensors need Seeed's stock RP2040 firmware, which you keep while flashing the ESP32-S3.A working Muse Gadgets: ESP32 Device SDK (Status) build on Seeed SenseCAP Indicator (D1 series), paired to your Muse account and ready for first prompts.
See inside
Take the Seeed SenseCAP Indicator (D1 series) apart
Drag to turn it, pull the slider to explode it, and tap a part to learn what it does. Open the full 3D view
Get the parts
You need the board and any build-specific accessories before flashing or pairing.
Must carry data, not just charge. Most flashing problems are charge-only cables. This Seeed cable is USB-C to USB-A and carries USB 3.1 data ($2.50 on 2026-10-05). If your computer has only USB-C ports, use the USB-C to USB-C option.
The base D1 has no CO2/tVOC sensors; Muse can only read sensors the variant has.
Optional. Runs the gadget from a wall outlet instead of your computer. A phone charger that supplies 5 V / 2 A or more works.
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-sensecap-indicator/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.
Flash the firmware
The board needs the Muse ESP32 firmware configured with your SDK token.
Read this first: flashing this board
- Port: This board has a CH340 USB bridge. It shows up as /dev/cu.usbserial-* or /dev/cu.wchusbserial* on macOS and /dev/ttyUSB* on Linux, not as usbmodem or ttyACM. On Linux, add yourself to the dialout (or uucp) group.
- Muse reads the D1S and D1Pro sensors through the RP2040, which needs Seeed's stock RP2040 firmware. Leave the RP2040 as it shipped; the Muse build flashes the ESP32-S3.
Source: https://github.com/facebookincubator/muse-gadget-sdk/blob/main/esp32/devices/README.md
Let your agent do it
Give your coding agent the build brief at https://www.hackshop.dev/build/seeed-sensecap-indicator/build.md. Tell it to keep the token private, use mgst_YOUR_TOKEN as the placeholder, and find the serial port before flashing. It should find the port with ls /dev/cu.usbserial-* /dev/cu.wchusbserial* 2>/dev/null || ls /dev/ttyUSB* 2>/dev/null; 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 sensecap-indicator build once to create build-sensecap-indicator/sdkconfig, set CONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN" in that file, run tools/board.sh sensecap-indicator 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 sensecap-indicator build
printf '\nCONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN"\n' >> build-sensecap-indicator/sdkconfig
tools/board.sh sensecap-indicator build
ls /dev/cu.usbserial-* /dev/cu.wchusbserial* 2>/dev/null || ls /dev/ttyUSB* 2>/dev/null
tools/board.sh sensecap-indicator flash-monitor PORTPair 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-Disp-XXXXXX and press the BOOT button when the screen or edge status 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 pairing button for 5 seconds to reset pairing.
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 cable through the slot or open edge, power it, and check that the buttons and display are reachable.
Try it
A first prompt proves the device is paired, reachable, and useful for the project.
Hand it to your agent
# Build: Seeed SenseCAP Indicator (D1 series) as a Muse gadget
Difficulty: Intermediate (extra steps). Its air sensors need Seeed's stock RP2040 firmware, which you keep while flashing the ESP32-S3.
## Goal
A working Muse Gadgets: ESP32 Device SDK (Status) build on Seeed SenseCAP Indicator (D1 series), paired to your Muse account and ready for first prompts.
## Warnings (read before flashing)
- Seeed SenseCAP Indicator: keep Seeed's stock RP2040 firmware. Muse reads the D1S and D1Pro sensors through the RP2040; the Muse build flashes only the ESP32-S3.
## Hardware
- [Seeed SenseCAP Indicator (D1 series)](https://www.seeedstudio.com/SenseCAP-Indicator-D1-p-5643.html) x1 (required, board): Main board or device for this build.
- [USB-C data cable](https://www.seeedstudio.com/USB-3-1-Type-C-to-A-Cable-1-Meter-3-1A-p-4085.html) x1 (required, part): Must carry data, not just charge. Most flashing problems are charge-only cables. This Seeed cable is USB-C to USB-A and carries USB 3.1 data ($2.50 on 2026-10-05). If your computer has only USB-C ports, use the USB-C to USB-C option.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.