01Before you start
Confirm the computer or phone has a functioning Bluetooth Low Energy adapter and that Bluetooth is enabled. A normal Bluetooth headset working does not automatically prove the browser exposes Web Bluetooth, so check the browser support guide if the Connect Cube control reports an unsupported platform.
Know the model if possible. SupaKewber selects among GAN Gen1, Gen2, Gen3 and Gen4 service families after the chooser returns the device. Model and firmware differences affect the handshake even though the visible connection button is the same.
02Why this process works
Web Bluetooth requires a secure page and a user gesture before showing nearby devices. That is why SupaKewber cannot silently reconnect to an unknown cube on page load and why the permission chooser must follow your click.
Closing other clients matters because many smart cubes maintain one active GATT connection. If CubeStation is connected, the browser may still show the device but fail while discovering services or starting notifications.
03How to verify the result
A successful browser pairing is not enough on its own. The useful test is a live turn: rotate one face, confirm the 3D cube follows in the correct direction and check that subsequent moves continue to arrive.
Next, solve the physical cube and make sure the virtual state is also solved. Starting a tracked scramble from mismatched states produces incorrect validation and unreliable stage timing.
04If it still does not work
If the chooser is empty, wake the cube again and move it closer. If selection succeeds but the handshake fails, close competing apps, toggle host Bluetooth and refresh SupaKewber before selecting the device again.
Only after the basic sequence fails should you remove saved operating-system pairings, restart the device or investigate firmware. The dedicated not-connecting guide separates chooser, GATT and move-stream failures.