Skip to content

Your Devices

A device is one phone line, end to end: the board you flashed, the bridge tab hosting it, and the phone paired to it — or, with Parrot App for Windows, the PC running the app and the phone paired to it. The console's Devices section is where you check on a line — whether it's up, what it's doing, and whether anything about the audio path needs attention.

The call path — a device is the highlighted stretch

A device is the highlighted stretch of the path: bridge + board + phone.

The Devices page

Open Devices in the console. Every line you own is listed, with four summary tiles up top — Online (reachable / total), Active calls, Bound (how many have an assistant), and the newest Firmware seen — plus a search box and All / Online / Offline filters.

The Devices page: summary tiles, one row per line

Each row shows the line's three states side by side:

  • Bridge — whether a Parrot Bridge tab is currently hosting the board (with uptime when it is). This is the "is it online" column; an offline row offers Open bridge right there.
  • Bluetooth — whether the board is currently connected to its phone. A board can be online but not paired; it can't carry calls in that state.
  • Call — idle, or on a call with its running time.

The Assistant column shows the line's assistant (during a call, the one running it). Under the device name: the device id and the firmware → bridge versions the board last reported (the thing troubleshooting will ask for). An offline row offers Remove — unbind a board you've retired (the board itself can always be re-flashed back in).

Can I run more than one line?

Yes — each board is its own device with its own assistant binding and its own keys. Flash and pair each one the same way, one Bridge tab per board.

The device page

Click a device for the full picture of that one line:

The device page: readiness, assistant, connection, phone, Place a call and recent calls

Top to bottom:

  • Header — the line's name and whether a call can start right now (and, if not, the one thing to do), with MCP (connect an agent to this line, Connect your AI agent) and Live monitor (turns green during a call).
  • Assistant — which assistant this line runs. The Who is calling? picker changes it for every later call on this line; Edit opens it, and Reset to default drops a per-device choice (Customizing your assistant).
  • Parrot Cloud connection — whether the board is connected to Parrot, with its response time and how long it has been connected (or when it was last seen).
  • Your phone — the paired phone, its Bluetooth signal, and its own cell signal as the phone reports it over the Hands-Free Profile (HFP) (how that works). If a call sounded bad, "one bar of signal" is a very different diagnosis than a Parrot problem.
  • Place a call — the number and what the call should accomplish (Making & receiving calls). During a call this is replaced by Current call: the other party, the duration, whether the AI session is connected, and the AI credits used so far.
  • Connection & diagnostics — the AI session lifecycle (Idle, AI off and no billing → Active, audio connected and AI running → a 25-second Grace window when audio drops, so a Bluetooth blip doesn't end the session → back to Idle; you pay for AI-connected time, not for the board sitting idle), and How this call connects: the live audio path drawn end to end, Parrot Cloud ↔ Parrot bridge ↔ Parrot device ↔ your phone ↔ the other party, so you can see which link is broken rather than just "it doesn't work." Hover or click a hop for its detail card. Each hop has its own chapter; this diagram is the wiki's map. What it looks like across the line's life:

    Path while offline Path when idle and ready to call Path during a live call - Recent calls — the last calls on this line, linking into Call history.

View past calls in Call history and credit usage in Billing, credits & API keys.

If the server refused the board's connection, a banner at the top says why in plain terms (see below).

When a device shows Offline

Offline means the board currently has no connection to Parrot. The usual causes, in order of likelihood:

  1. The Bridge tab was closed — the board's connection runs inside that browser tab. Reopen the Parrot Bridge page (/bridge/), and with auto-start on it comes back by itself; otherwise click Run the bridge.
  2. The board lost power — check its USB cable.
  3. It just rebooted — give it ~10 seconds and refresh.

If the line is Parrot App for Windows, the bridge runs inside the app: open Parrot App on that PC (the banner's Open Parrot App link) and keep the PC awake and online.

The console (or the Bridge page) says the server rejected the board

The banner names the reason. If it mentions the board not being yours or not provisioned, re-run setup on the Bridge page while signed in to the right account — flashing is what claims a board. If it mentions an outdated version, re-flash to update the firmware (or just reload the tab if it's the bridge that's outdated). Details: when the server refuses the connection.