How to Pair a Pico Remote: Build & Debug a Raspberry Pi Pico W BLE HID Controller

If you want to know how to pair a Pico remote to a PC, smartphone, or tablet, the most reliable method is configuring the Raspberry Pi Pico W as a Bluetooth Low Energy (BLE) Human Interface Device (HID). Unlike proprietary 2.4GHz RF remotes that require a dedicated USB dongle, a BLE HID remote pairs natively with Windows, macOS, iOS, and Android using the host device’s built-in Bluetooth stack.

This guide walks through the exact hardware requirements, the MicroPython code to emulate a BLE keyboard, and the specific debugging steps required when the Cypress CYW43439 wireless chip throws synchronization errors during the pairing process.

Project Overview & Hardware Requirements

Building a wireless remote requires managing both the logical BLE stack and the physical power delivery. The Raspberry Pi Pico W is the target board variant for this build because it integrates the RP2040 microcontroller with the Infineon CYW43439 WiFi/BLE coprocessor on a single module.

Parts List

• Microcontroller: Raspberry Pi Pico W (with pre-soldered pin headers). Do not use the standard Pico or Pico 2; they lack the BLE radio.
• Switches: 4x 6x6x5mm Tactile Pushbuttons (Through-hole).
• Power: 3.7V 500mAh 1S LiPo Battery (e.g., Adafruit 3898 or equivalent with JST-PH 2.0 connector).
• Charging: TP4056 LiPo charging module (must include the DW01A protection IC to prevent over-discharge).
• Substrate: 5x7cm Perfboard or custom PCB.

Pico W Pin Mapping & RF Power Specifications

Before wiring the tactile switches, you must understand the power constraints of the Pico W. The CYW43439 chip draws significant peak current during BLE advertising and transmission. If your power supply cannot deliver this current, the radio will brownout and fail to initialize.

For authoritative details on the Pico W power tree, refer to the Raspberry Pi Pico W Datasheet, specifically Section 3.4 regarding the CYW43439 power domains.

Step-by-Step: Flashing and Pairing the Pico Remote

Pairing a BLE HID device is not the same as pairing a standard serial Bluetooth module. The host OS expects a specific GATT (Generic Attribute Profile) service tree. Follow these steps to establish the bond.

1. Flash the Firmware: Download the latest stable MicroPython UF2 specifically built for the Raspberry Pi Pico W from the official MicroPython download page. Hold the BOOTSEL button, plug in USB, and drag the UF2 file to the RPI-RP2 drive.
2. Upload the Code: Use Thonny or VS Code (with the MicroPython extension) to upload the complete HID script (provided below) as main.py on the Pico W.
3. Power Cycle: Disconnect USB and plug in your LiPo battery. The onboard LED will pulse slowly, indicating the BLE stack is advertising.
4. Initiate Host Pairing (Windows 11): Go to Settings > Bluetooth & devices > Add device > Bluetooth. Look for Pico-HID-Remote.
5. Complete the Bond: Click the device. Windows may prompt you to type a PIN on the remote. Because this is a custom macro remote, Windows will usually bypass the PIN prompt and show "Connected". If it asks for a PIN, click "Cancel" or "Try connecting without a PIN" (Windows 11 allows this for HID devices without keyboards).
6. Verify: Open a text editor on your PC. Press Button 1 on the Pico remote. The letter 'A' should appear.

Complete MicroPython BLE HID Code

This code targets the Raspberry Pi Pico W. It uses the native bluetooth module to register a standard Keyboard HID service. It includes explicit pin definitions, a standard 54-byte HID report descriptor, and error handling for the CYW43439 SPI sync failures.

import bluetooth
import struct
import time
from machine import Pin, Timer

# --- PIN DEFINITIONS ---
BUTTON_PINS = [10, 11, 12, 13]
LED_PIN = 25  # Note: On Pico W, GPIO 25 is the CYW43439 WL_GPIO0 pin, not the physical board LED.
# We use the physical LED via the wireless chip if needed, but keep it simple here.

# --- BLE HID DESCRIPTOR (Standard Keyboard) ---
HID_REPORT_DESCRIPTOR = bytes((
    0x05, 0x01,  # Usage Page (Generic Desktop Ctrls)
    0x09, 0x06,  # Usage (Keyboard)
    0xA1, 0x01,  # Collection (Application)
    0x85, 0x01,  #   Report ID (1)
    0x05, 0x07,  #   Usage Page (Kbrd/Keypad)
    0x19, 0xE0,  #   Usage Minimum (0xE0)
    0x29, 0xE7,  #   Usage Maximum (0xE7)
    0x15, 0x00,  #   Logical Minimum (0)
    0x25, 0x01,  #   Logical Maximum (1)
    0x75, 0x01,  #   Report Size (1)
    0x95, 0x08,  #   Report Count (8)
    0x81, 0x02,  #   Input (Data,Var,Abs)
    0x95, 0x01,  #   Report Count (1)
    0x75, 0x08,  #   Report Size (8)
    0x81, 0x01,  #   Input (Const)
    0x95, 0x06,  #   Report Count (6)
    0x75, 0x08,  #   Report Size (8)
    0x15, 0x00,  #   Logical Minimum (0)
    0x25, 0x65,  #   Logical Maximum (101)
    0x05, 0x07,  #   Usage Page (Kbrd/Keypad)
    0x19, 0x00,  #   Usage Minimum (0x00)
    0x29, 0x65,  #   Usage Maximum (0x65)
    0x81, 0x00,  #   Input (Data,Array)
    0xC0         # End Collection
))

# Bluetooth SIG UUIDs
UUID_HID_SERVICE = bluetooth.UUID(0x1812)
UUID_HID_REPORT = bluetooth.UUID(0x2A4D)
UUID_HID_INFO = bluetooth.UUID(0x2A4A)

class PicoHIDRemote:
    def __init__(self, ble):
        self._ble = ble
        self._ble.active(1)
        self._ble.irq(self._irq)
        self._setup_services()
        self._connections = set()
        self._buttons = [Pin(p, Pin.IN, Pin.PULL_UP) for p in BUTTON_PINS]
        self._last_state = [1, 1, 1, 1]
        
    def _setup_services(self):
        # HID Information: 0x00C1 (Keyboard), 0x00 (Country), 0x02 (Normally Connectable)
        hid_info = struct.pack('