Cross platform application for controlling your brick creations using a your computer, your programs (via http), or a bluetooth gamepad.
- macOS 15+ (Mac Catalyst) - with HTTP web service host
- iOS 12.2+
- Ubuntu 24.04+ / Linux GTK4 (experimental UI; Bluetooth LE and gamepad input are not implemented in the UI head yet)
- Ubuntu 24.04+ / Linux headless API host (BlueZ Bluetooth LE central over HTTP)
- Windows 10 version 1809 or higher
- Windows 11
- Android 5.0+
- SBrick - both normal and plus (output only)
- SBrick Light
- BuWizz 1
- BuWizz 2
- BuWizz 3
- LEGO® PowerFunctions infrared receiver on Android devices having IR emitter
- LEGO® Powered-Up hub
- LEGO® Boost Hub
- LEGO® Technic Hub
- LEGO® WeDo 2.0 Smart Hub
- LEGO® Technic Move Hub (PLAYVM mode)
- LEGO® Duplo Train Hub
- Circuit Cubes
- Mould King DIY Module
- Mould King 3.8 Powered Module
- Mould King 4.0 Powered Module
- Mould King 5.0 Powered Module
- Mould King 6.0 Powered Module
- CaDA Race Car
- PFx Brick (lights & Power Functions ports only)
- JieStar 4 Channel Smart Creative Module
- JieStar 8 Channel Smart Creative Module
- Generic Bluetooth / USB gamepads
- LEGO® Power Functions infrared remotes (part numbers 8885 and 8879) — requires an Android device with an IR emitter
- LEGO® Powered Up Remote (part number 88010)
- Built-in motion sensor — when supported by the device
BrickController is a MAUI application and can be compiled using Visual Studio 2026 (Professional, Enterprise and Community Editions) or Visual Studio for Mac. Desktop installer scripts are documented in docs/desktop-installers.md, and the Linux headless Bluetooth API is documented in docs/linux-headless-api.md.
For a researched overview of supported controllers, receiver hubs, motors, lights, product availability, and servo-control options, see Controllers and powered equipment.
LEGO® is a trademark of the LEGO Group of companies, which does not sponsor, authorize, or endorse BrickController2.
The Mac app can expose a HTTP control API for external tools. For local testing, start the app with:
BRICKCONTROLLER_HTTP_ENABLED=1BRICKCONTROLLER_HTTP_PORT=5081BRICKCONTROLLER_HTTP_TOKEN=test-tokenBRICKCONTROLLER_HTTP_LISTEN_MODE=Loopback
The example client in example/http_mk38_motor_test_client.py creates a virtual controller named HTTP MK3.8 Test with five axis capabilities:
mk38Channel0/MK38_Channel_0mk38Channel1/MK38_Channel_1mk38Channel2/MK38_Channel_2mk38Channel3/MK38_Channel_3mk38Channel4/MK38_Channel_4
To run the end-to-end Mac MK 3.8 HTTP smoke test without running the packager:
test/test-http-mk38-client.shThe script builds the Debug Mac Catalyst app, starts it with HTTP enabled and token test-token, enables the diagnostic profile host with BC2_HTTP_MK38_E2E_TEST=1, waits for BC2_HTTP_MK38_E2E_READY in /tmp/brickcontroller2-http-test-app.log, then runs the Python client. The app-side diagnostic creates or refreshes the normal BrickController creation/profile HTTP MK3.8 End-to-End Test, maps HTTP MK3.8 Test capabilities MK38_Channel_0..4 to the Mould King MK 3.8 channels 0..4, connects the MK 3.8 device through the normal app path, and forwards HTTP controller events through PlayLogic.
Each channel is set to 50% for one second, then reset to zero before the next channel. Override defaults as needed:
BRICKCONTROLLER_TOKEN=my-token BRICKCONTROLLER_HTTP_PORT=5082 test/test-http-mk38-client.sh --power 0.5 --seconds 1For a lower-level MK 3.8 Bluetooth advertising smoke test that does not use HTTP or a controller profile, run:
test/test-mk38-motor.shIstván Murvai
Maintainer of Mac and 2026 app store version: Prof. Dr. Raphael Volz (Pforzheim University)
Prof. Dr. Raphael Volz (Pforzheim University)