QiYi, GiiKER & MoYu notes

cubrs also connects to QiYi, GiiKER, and MoYu smart cubes. These drivers are experimental — connect one expecting it to work, but also expecting the occasional rough edge, since they haven’t had the same hardware pass the GAN family has. When a cube is running an experimental driver, its header device name reads “(experimental)” so you always know. Here’s what to know per brand.

1. QiYi Smart Cube / X-Man Tornado V4

QiYi cubes stamp every move with a native cube timestamp, which means their timing is as accurate as cubrs can get — the same class of source it uses for GAN cubes. State comes through, battery comes through, and the cube pushes its own state automatically. cubrs works out the MAC address from the device name for you, falling back to a manual prompt only if that fails. There’s no hardware “reset to solved” command, so getting the cube believed-solved is done by syncing its state (see when the cube is out of sync).

2. GiiKER i2 / i3 / i3s

GiiKER cubes need no MAC address, and they broadcast their full state on every turn, so cubrs always knows where the cube is. Timing uses your computer’s clock rather than a cube timestamp. There’s no hardware reset command either, so Mark as solved is emulated in the driver by replaying your turns onto a solved cube. One caveat: the GiiKER i3SE uses a different protocol and is not supported.

3. MoYu WeiLong V10 / V11 AI

The MoYu WeiLong V10 and V11 AI (they show up as WCU_MY32) report moves with timestamps, full state, battery, and a hardware reset. cubrs derives the MAC from the device name automatically. Gyroscope-core models also stream orientation — if yours does, run the ⚲ Calibrate wizard once so cubrs learns the sensor frame (its gyro scaling is still an unverified hardware detail, so expect orientation to be the roughest part). The older MoYu AI 2019 / WeiLong AI legacy uses a different protocol and is not supported.