Wiki / Other software
RemoteBlaBla
A Pybricks program that turns the LEGO Powered Up handset into a configurable remote: you say once which button does what, and the hub remembers it. MIT licensed.
What it reaches
| Capability | State | Note |
|---|---|---|
| Map handset buttons to whatever is plugged into the hub | works, untested here | the config mode, done on the hub itself |
| Keep the mapping across a power cycle | works, untested here | which is the point: play mode needs no setup |
| Run on a Technic hub | works, untested here | it has the memory for config mode |
| Configure on a City hub | out of reach | not enough memory; the mapping has to be made on a Technic hub and carried over |
| Run under Pybricks 3.2 | out of reach | that version restricts connecting and disconnecting devices, and the program depends on it |
| Show anything | out of reach | seven buttons and two lights are the whole interface; there is no screen |
Why it is here
It is the same idea as this project's five slots, reached from the LEGO side: define the layout once, then drive with no phone. The difference is what holds the definition — a hub running replacement firmware there, the bridge here — and what does the driving: LEGO's own handset rather than a gamepad.
Memory, not protocol, is what decides which hub can hold a configuration, and that constraint shows up again in Powered Up hub (Pybricks VLL), where the poorest hub in the family dictates how the program has to be written.
Links
- vascolp/RemoteBlaBla — version 1, no longer developed; a second version has succeeded it
- Pybricks — the firmware it needs
- Powered Up — the hubs and the handset