If you just unboxed your bike and are pulling your hair out because the ADO companion app refuses to pair, fails the handshake, or gets stuck on the connection screen—turn off your Wi-Fi and switch your phone to mobile data.

Here is what happened during my setup and why this happens:

The Red Herring: Thinking It’s Bluetooth

When you first try to connect, the natural assumption is that it’s a local Bluetooth issue or a phone bug:

* You force-close and restart the app.

* You toggle Bluetooth on and off.

* You reset the bike display.

* You check location and nearby device permissions.

None of that solved it.

The Real Culprit: Home Firewalls & DNS Threat Blocking

Even though the bike communicates with your phone via Bluetooth, the ADO app requires an active handshake with ADO’s cloud servers during initial device binding to register the bike’s serial number and firmware profile to your account.

If you run a mesh network with built-in security filters—like an Amazon eero system (with eero Plus / Advanced Security enabled), a router firewall, or a network DNS blocker (like Pi-hole or AdGuard)—it can silently flag and block the outbound request to ADO’s backend server as an unknown or foreign IoT domain.

Because the request gets blocked at the router level, the app simply fails to bind the bike.

The 10-Second Fix

1. Swipe down on your phone and turn off Wi-Fi completely.

Hopefully this saves someone a couple of hours of unnecessary troubleshooting during unboxing day! Did anyone else run into this with their home router setup?