Muse boards / Build

Build: Seeed SenseCAP Watcher

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 stepsBack up its nvsfactory partition first, flash through the CH342 port ending in 3, and wait about 3 minutes for the paced flash.

A working Muse Gadgets: ESP32 Device SDK (Full UI) build on Seeed SenseCAP Watcher, paired to your Muse account and ready for first prompts.

Screen and voiceBoard $61 · about $64 with cable/parts
Download build.md

See inside

Take the Seeed SenseCAP Watcher 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

Loading 3D model
1

Get the parts

You need the board and any build-specific accessories before flashing or pairing.

1 × USB-C data cable
Requiredpart

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.

Buy from seeedstudio.com
1 × USB-C power adapter (5 V / 2 A or more)
Optionalpart

Optional. Runs the gadget from a wall outlet instead of your computer. A phone charger that supplies 5 V / 2 A or more works.

Find on amazon.com
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-muse-sensecap-watcher/sdkconfig after the board build command has created that file, then run the build command again. idf.py -B build-muse-sensecap-watcher -DIDF_TARGET=esp32s3 -DSDKCONFIG=build-muse-sensecap-watcher/sdkconfig -DSDKCONFIG_DEFAULTS="sdkconfig.defaults;devices/sdkconfig.muse;devices/sdkconfig.muse-sensecap-watcher" 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.

Read this first: flashing this board

  • Port: Use the bottom USB-C port. Its CH342 bridge shows up as two ports, both /dev/cu.usbmodem* on macOS. Use the port ending in 3: that is the ESP32-S3 console. The first one is the Himax camera chip.
  • Flash only with tools/muse/board.sh flash watcher PORT. It sends 64 bytes at a time at 115200 baud. Plain esptool and idf.py flash fail on the CH342 (0107: Checksum error, or 0105) after they have erased the bootloader, so the board can't boot until a flash succeeds. It isn't bricked: the ROM loader still answers.
  • A lower baud or another USB port doesn't help, and WCH's driver isn't needed on macOS.
  • Camera capture is off by default. To use it, turn on CONFIG_MUSE_WATCHER_CAMERA=y (menuconfig > Muse > SenseCAP Watcher camera capture and live preview) and rebuild.
  • Before the first flash, back up the Watcher's nvsfactory partition (its factory data at 0x9000, unique to each Watcher, which Muse overwrites): tools/muse/paced_esptool.py --chip esp32s3 -p PORT read-flash 0x9000 0x32000 nvsfactory.bin. Keep nvsfactory.bin safe, outside Git.
  • To go back to Seeed's firmware, flash it first, then write the backup back: tools/muse/paced_esptool.py --chip esp32s3 -p PORT write-flash 0x9000 nvsfactory.bin.
  • A Watcher flash shows nothing for about 3 minutes. Don't interrupt it: that leaves the board unbootable again.
  • Never flash the Watcher with plain esptool or idf.py flash.
  • Don't unplug the cable or stop the command while it flashes.

Source: https://github.com/facebookincubator/muse-gadget-sdk/blob/main/esp32/AGENTS.md

Let your agent do it

Give your coding agent the build brief at https://www.hackshop.dev/build/seeed-sensecap-watcher/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.usbmodem* 2>/dev/null || ls /dev/ttyACM* /dev/ttyUSB* 2>/dev/null; on Windows, use Device Manager to find the COM port, then run commands in the ESP-IDF shell. Before the first flash, it must back up the Watcher's nvsfactory partition (its factory data at 0x9000, unique to each Watcher, which Muse overwrites).

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/muse/board.sh build watcher once to create build-muse-sensecap-watcher/sdkconfig, set CONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN" in that file, run tools/muse/board.sh build watcher 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/muse/board.sh build watcher
printf '\nCONFIG_GADGET_SDK_TOKEN="mgst_YOUR_TOKEN"\n' >> build-muse-sensecap-watcher/sdkconfig
tools/muse/board.sh build watcher
ls /dev/cu.usbmodem* 2>/dev/null || ls /dev/ttyACM* /dev/ttyUSB* 2>/dev/null
tools/muse/paced_esptool.py --chip esp32s3 -p PORT read-flash 0x9000 0x32000 nvsfactory.bin
tools/muse/board.sh flash watcher PORT
4

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 wheel 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. To reset pairing, open Settings > MUSE > Reset pairing on the device and tap again to confirm.

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 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.

“Take a picture of my 3D printer and tell me if the print failed.”“Is anyone at my desk right now?”

Hand it to your agent

# Build: Seeed SenseCAP Watcher as a Muse gadget
Difficulty: Intermediate (extra steps). Back up its nvsfactory partition first, flash through the CH342 port ending in 3, and wait about 3 minutes for the paced flash.

## Goal
A working Muse Gadgets: ESP32 Device SDK (Full UI) build on Seeed SenseCAP Watcher, paired to your Muse account and ready for first prompts.

## Warnings (read before flashing)
- SenseCAP Watcher: back up the nvsfactory partition (read-flash 0x9000 0x32000) before the first flash, use the CH342 port ending in 3, and flash only with tools/muse/board.sh flash watcher. It shows nothing for about 3 minutes; don't interrupt it.

## Hardware
- [Seeed SenseCAP Watcher](https://www.seeedstudio.com/SenseCAP-Watcher-W1-A-p-5979.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.