Facebook Incubator Releases Open Source Muse Gadget SDK for DIY Hardware Enthusiasts

The Facebook Incubator has released the open source Muse Gadget SDK, providing developers and hobbyists with tools to build custom hardware devices using off-the-shelf ESP32 boards or Raspberry Pi setups. According to the project repository, the release aims to support tinkerers in connecting displays, buttons, sensors, and actuators.

Getting Started and Hardware Requirements

• Supported Hardware: Off-the-shelf ESP32 boards and Raspberry Pi devices.
• Companion App: iOS and Android Muse app for pairing ESP32 and Linux gadgets via Settings > Devices after enabling Developer mode.
• Authentication: Every gadget requires an SDK token to pair, and users are advised to review the Gadget SDK Terms before flashing or pairing.
• Documentation: Each directory contains a README.md file for getting started and an AGENTS.md file intended for coding agents like Muse Code.

Diagnostics and Power Profiling

• Power Profiling: A porting recipe is available for battery-input power profiling.
• Diagnostic Core: An opt-in diagnostic core is board-neutral, allowing boards to supply hooks and state matrices while `power_sweep.py` drives the USB-free sweep.
• Safety Notice: The isolated diagnostic does not pair or require an SDK token, though fixture safety and hardware authorization remain primary requirements as outlined in the PPK2 rules.

Licensing and Community

• Open Source License: Muse Gadgets is licensed under the Apache License, Version 2.0, with specific exclusions for third-party files, build-time dependencies, and the Jollybot avatar.
• App Licensing: Built APK or iPhone applications may fall under the GPL due to dependencies such as x264 usage in test applications.
• Community Support: Builders can connect via the project's community Discord to share projects and troubleshoot builds.

Project maintainers note that tinkering carries inherent risks such as bricked boards, voided warranties, brownouts, or bankruptcies, and users proceed at their own risk. Verification of the SDK, terms, and documentation can be conducted directly through the official GitHub repository.