The connector requests GAN device and service identifiers, detects the available service and routes the cube to a Gen1, Gen2, Gen3 or Gen4 protocol driver. A listed family means the protocol path exists; it is not a guarantee that every regional revision or future firmware behaves identically.
Current matrix
Documented model-family support
| Cube family | Path | Status | Notes |
|---|---|---|---|
| GAN 356 i Carry / i Carry S | Gen2 | Supported | Move-aware timing and CFOP analysis when synchronized. |
| GAN 356 i Carry 2 | Gen3 | Supported | Newer packet format with recent-move recovery for short gaps. |
| Original GAN 356i | Gen1 | Legacy | Polling-based path; hardware, firmware and host differences matter more. |
| GAN 12 ui family, including compatible FreePlay revisions | Gen2/3/4 by revision | Supported family | Exact electronics revision determines the detected path. |
| Other GAN, AiCube, GAN Mini ui or Monster Go 3Ai variants | Compatible GAN services | Varies | Discovery may work, but unlisted revisions are not promised as fully tested. |
| Giiker, GoCube, Rubik’s Connected and non-GAN protocols | Not implemented | Not supported | Use manual timing unless a connector is added. |
Browser requirements
Where Web Bluetooth works best
Chrome or Edge
Recommended on Windows, macOS or ChromeOS. Bluetooth must be enabled and the live page uses HTTPS.
Chrome
Commonly exposes Web Bluetooth; manufacturer permission behavior can vary.
Not native Safari support
Safari lacks the same Web Bluetooth path. A compatible BLE browser may work but must be tested.
Not a primary path
Firefox is not treated as supported for the direct connector.
Before connecting
Conditions for a reliable session
- Open the live HTTPS site in a supported browser; localhost is allowed for development.
- Enable Bluetooth and keep the cube close.
- Close CubeStation, other timers and tabs that may hold the connection.
- Turn the cube before choosing it so it is awake and advertising.
- Compare several physical turns with the on-screen cube before a serious solve.
What supported means
Connection is only the first test
A reliable session needs service discovery, protocol initialization, live decoding, correct move order, synchronized state and a clean solved event. Seeing a device in the chooser does not prove full support.
If states disagree, discard the analysis, solve the physical cube, reconnect and validate moves. See the connection guide and disconnect guide.
Improve the matrix
Report a model or firmware result
Use the contact page with the printed model, approximate purchase year, OS, browser and whether discovery, connection or moves failed. Do not include a Bluetooth MAC address or account secret.