PyBLEGet PyBLE
Menu

Beta help

Support

Start with the quick checks below. If the problem remains, send a small, reproducible report and we will help you narrow it down.

New to PyBLE? Follow the guided tutorials.

Get started

  1. 1

    Check firmware status before installing

    Public v0.6.1 firmware is available for all five exact profiles, following owner qualification confirmation. Select your exact board on the firmware page and back up its files before installation. Only the Waveshare B-version image includes the TFT runtime and fresh-install splash. Confirm the active release, exact profile, and enabled action; this initial step uses a cable.

  2. 2

    Power the board and open PyBLE

    Allow Bluetooth access, choose the nearby PyBLE board, and wait for the connected workspace.

  3. 3

    Choose pins explicitly

    Boards route LEDs, buttons, and NeoPixels differently. Check your board documentation before running GPIO code.

  4. 4

    Save, run, and watch the console

    Keep the board powered; editing, files, execution, and console traffic now travel over BLE.

If the board does not appear

Restart nearby

Power-cycle the board, keep it close to the tablet, and scan again after its agent starts.

Check Bluetooth access

Confirm Bluetooth is on and PyBLE still has the platform permission needed to scan.

Release other connections

Disconnect the board from another phone, tablet, or BLE tool before trying again.

Confirm the firmware

Generic MicroPython alone does not advertise the PyBLE service; the matching PyBLE agent firmware must be installed.

If code does not behave as expected

  • Read the full console traceback, beginning with the first error.
  • Confirm the GPIO number, voltage, and wiring for your exact board.
  • Stop the current program or soft reboot before running a new one.
  • Reduce the program to the smallest file that still reproduces the behavior.