When a robotics kit refuses to pair over Bluetooth, the culprit is almost never a broken hub. Nine times out of ten the host device, your laptop, tablet or phone, has Bluetooth switched off in the wrong place or is clinging to a stale entry from a previous session. Fix those two things in order and the hub usually connects on the next try.

Quick Answer

Enable Bluetooth on the host device first, then remove the kit's old entry from the Bluetooth cache and re-pair. A stale device name causes the host to refuse the connection even when the hub is broadcasting correctly. This two step fix resolves most pairing failures across LEGO SPIKE, mBot2, micro:bit and similar kits.

Step by Step: The Fix That Works Most Often

Work through these in order rather than jumping around, since each step rules out a likely cause.

  1. Confirm Bluetooth is on at the host. Open your device settings and check that Bluetooth is actually enabled, not just the app's own connection screen. Many failed pairings are simply a host with Bluetooth toggled off.
  2. Power cycle the hub. Switch the robotics kit fully off, wait a few seconds, then switch it back on so it starts broadcasting fresh. A hub that has been sitting in a half connected state will not always advertise itself.
  3. Forget the old device entry. In your Bluetooth settings, find the kit's previous entry and remove or forget it. This clears the stale cache that makes the host reject a hub it thinks it already knows. This is the single most effective step.
  4. Re-pair from scratch. With the cache cleared and the hub freshly powered, start the pairing process again from the app or the system Bluetooth menu and select the hub when its name appears.
  5. Move closer and reduce interference. Bring the host within a metre of the hub for the initial pairing and step away from crowded wireless areas, since other devices can drown out the hub's signal during the handshake.

Why the Stale Cache Causes So Much Trouble

Bluetooth hosts remember devices by name and identifier. When a robotics hub reconnects, the host expects it to match the stored entry exactly. If the kit's firmware updated, the hub was renamed, or the previous session ended uncleanly, that stored entry no longer matches what the hub is now broadcasting. The host sees a mismatch and quietly refuses, even though the hub is advertising itself perfectly.

Forgetting the device wipes that outdated record so the host treats the hub as brand new and accepts the fresh handshake. This is why clearing the cache fixes so many cases that look like hardware faults but are not.

When the Basics Do Not Solve It

If the hub still will not pair after a clean cache and re-pair, check a few more things. Make sure the hub's battery is charged, since a low hub can broadcast weakly or drop mid handshake. Confirm only one host is trying to claim the hub at a time, because two devices fighting over the same hub will both fail. If you use a USB Bluetooth dongle on a desktop, make sure the right adapter is selected and its driver is installed. For desktops missing built in Bluetooth, a quality adapter from the accessories best sellers range is a cheap fix. You can also explore compatible hubs and smart devices on the smart home and appliances page if you suspect the kit itself.

Frequently Asked Questions

Why does my robotics kit show but not connect?

The hub is broadcasting but the host is rejecting the handshake, usually because of a stale cached entry that no longer matches the hub's current name or firmware. Forget the old device and re-pair to clear it.

Should I enable Bluetooth in the app or in settings?

Both, but system settings first. The app cannot pair if Bluetooth is disabled at the operating system level, so confirm it is on there before troubleshooting inside the kit's app.

Does a firmware update break pairing?

It can. A firmware update sometimes changes how the hub identifies itself, leaving the host's stored entry outdated. Forgetting and re-pairing the device resolves this cleanly.

My desktop has no Bluetooth, what now?

Use a USB Bluetooth adapter and make sure its driver is installed and the correct adapter is selected. Many desktops lack built in Bluetooth, so a dongle is the standard solution.

Need a reliable Bluetooth adapter or a fresh robotics hub to get pairing on the first try? Browse the smart devices on the Evetech smart home and appliances page.