![\"Raspberry](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/Raspberry-Pi-Pico-BLE-Getting-Started.jpg?resize=1200%2C675&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\nNew to the Raspberry Pi Pico? Check out our eBook: Learn Raspberry Pi Pico\/Pico W with MicroPython<\/a><\/strong>.<\/p>\n\n\n\n To follow this tutorial, you need MicroPython firmware installed on your Raspberry Pi Pico board. You also need an IDE to write and upload the code to your board.<\/p>\n\n\n\n The recommended MicroPython IDE for the Raspberry Pi Pico is Thonny IDE. Follow the next tutorial to learn how to install Thonny IDE, flash MicroPython firmware, and upload code to the board.<\/p>\n\n\n\n The Raspberry Pi Pico W and Raspberry Pi Pico 2 W come with an Infineon CYW43439 chip that adds Wi-Fi and Bluetooth support.<\/p>\n\n\n\n This tutorial is only compatible with the W versions of the Raspberry Pi Pico:<\/p>\n\n\n\n The documentation mentions it supports both Bluetooth Classic and Bluetooth Low Energy. However, I couldn’t find examples for Bluetooth Classic with MicroPython at the moment. So, our examples will be focusing on Bluetooth Low Energy.<\/p>\n\n\n MicroPython support for Bluetooth with the Pico W is relatively recent, so there is still little support in terms of examples, libraries, documentation, and functionality. Additionally, some libraries are still in beta version, and either they don’t have all their methods developed, or they don’t provide examples or documentation, or have bugs or issues. So, at the moment, take that into account when dealing with Bluetooth on the Raspberry Pi Pico. Nonetheless, we’ll provide you with some essential information and basic working examples that we could run and test that will help you get started.<\/p>\n\n\n\n Bluetooth Low Energy, BLE for short (also called Bluetooth Smart), is a power\u2011conserving variant of Bluetooth. BLE\u2019s primary application is short-distance transmission of small amounts of data (low bandwidth). Unlike Bluetooth, which is always on, BLE remains in sleep mode constantly except for when a connection is initiated. This makes it consume very little power. BLE consumes approximately 100x less power than Bluetooth (depending on the use case).<\/p>\n\n\n\n Before proceeding, it\u2019s important to get familiar with some basic BLE concepts<\/p>\n\n\n\n When using Bluetooth Low Energy (BLE), it\u2019s important to understand the roles of BLE Peripheral and BLE Controller (also referred to as the Central Device).<\/p>\n\n\n The Pico W can act either as a Peripheral or as a central device. When it acts as a peripheral it sets up a GATT profile and advertises its service with characteristics that the central devices can read. On the other hand, when it is set as a central device, it can connect to other BLE devices to read or interact with their profiles and read their characteristics.<\/p>\n\n\n\n In the above diagram, the Pico takes the role of the BLE Peripheral, serving as the device that provides data or services. Your smartphone or computer acts as the BLE Controller, managing the connection and communication with the Pico.<\/p>\n\n\n\n With Bluetooth Low Energy, there are two types of devices: the server and the client. The Pico can act either as a client or as a server. In the picture below it acts as a server, exposing its GATT structure containing data. The BLE Server acts as a provider of data or services, while the BLE Client consumes or uses these services.<\/p>\n\n\n The server advertises its existence, so it can be found by other devices and contains data that the client can read or interact with. The client scans the nearby devices, and when it finds the server, it is looking for, it establishes a connection and can interact with that device by reading or writing to its characteristics.<\/p>\n\n\n\n The BLE server is basically the BLE peripheral before establishing a connection. The BLE Client is the BLE controller before establishing a connection. Many times, these terms are used interchangeably.<\/p>\n\n\n\n GATT, which stands for Generic Attribute Profile, is a fundamental concept in Bluetooth Low Energy (BLE) technology. Essentially, it serves as a blueprint for how BLE devices communicate with each other. Think of it as a structured language that two BLE devices use to exchange information seamlessly.<\/p>\n\n\n Let\u2019s take a more in-depth look at the BLE Service and Characteristics.<\/p>\n\n\n\n The top level of the hierarchy is a profile, which is composed of one or more services. Usually, a BLE device contains more than one service, like the battery service and the heart rate service.<\/p>\n\n\n\n Every service contains at least one characteristic. There are predefined services for several types of data defined by the SIG (Bluetooth Special Interest Group) like: Battery Level, Blood Pressure, Heart Rate, Weight Scale, Environmental Sensing, etc. You can check the following link for predefined services:<\/p>\n\n\n\n A UUID is a unique digital identifier used in BLE and GATT to distinguish and locate services, characteristics, and descriptors. It\u2019s like a distinct label that ensures every component in a Bluetooth device has a unique name.<\/p>\n\n\n\n Each service, characteristic, and descriptor has a UUID (Universally Unique Identifier). A UUID is a unique 128-bit (16 bytes) number. For example:<\/p>\n\n\n\n There are shortened and default UUIDs for services and characteristics specified in the SIG (Bluetooth Special Interest Group). This means that if you have a BLE device that uses the default UUIDs for its services and characteristics, you\u2019ll know exactly how to interact with that device to get or interact with the information you\u2019re looking for.<\/p>\n\n\n\n You can also generate your own custom UUIDs if you don\u2019t want to stick with predefined values or if the data you\u2019re exchanging doesn\u2019t fit in any of the categories.<\/p>\n\n\n\n You can generate custom UUIDs using this UUID generator website<\/a>.<\/p>\n\n\n\n Here are the usual steps that describe the communication between BLE Devices.<\/p>\n\n\n To write code to use Bluetooth with the Raspberry Pi Pico, we\u2019ll install the aioble<\/span> package\u2014that\u2019s currently the recommended library to use for BLE communication. Before proceeding to the actual examples, you need to install it on your board.<\/p>\n\n\n\n 1) <\/strong>Connect the board to your computer and connect it to Thonny IDE.<\/p>\n\n\n\n 2)<\/strong> On Thonny IDE, go to Tools <\/strong>> Manage Packages\u2026<\/strong><\/p>\n\n\n\n 3) <\/strong>Search for aioble<\/em> and click on the aioble<\/span> option.<\/p>\n\n\n 4)<\/strong> Finally, click the Install<\/strong> button.<\/p>\n\n\n 5) <\/strong>Wait a few seconds while it installs.<\/p>\n\n\n\n That’s it. Now you can use the aioble<\/span> functions to program the Raspberry Pi Pico.<\/p>\n\n\n\n For this example, you need two Raspberry Pi Pico W or 2W boards. We\u2019ll set one board as a BLE peripheral and another as a BLE Central device. You\u2019ll learn how the peripheral device advertises data and how the central device can read data from the peripheral device.<\/p>\n\n\n Only have one Raspberry Pi Pico W Board?<\/strong><\/p>\n\n\n\n If you only have one Raspberry Pi Pico W board, you can only test and follow the peripheral device example, but you have to skip the central device.<\/p>\n\n\n\n In this example, we\u2019ll create a BLE peripheral with the Environmental Sensing Service<\/em> (a service defined by the SIG) with one characteristic for the temperature<\/em>.<\/p>\n\n\n\n We\u2019re going to use the default UUIDs for the Environmental Sensing Service and the Temperature characteristic.<\/p>\n\n\n\n If you go to this page<\/a> and open the Assigned Numbers Document (PDF)<\/a>, you\u2019ll find all the default assigned UUID numbers. If you search for the Environmental Sensing Service<\/em>, you\u2019ll find all the permitted characteristics that you can use with that service. You can see that it supports temperature.<\/p>\n\n\n There\u2019s a table with the UUIDs for all services. You can see that the UUID for the Environmental Sensing service is 0x181A<\/strong>.<\/p>\n\n\n Then, search for the temperature characteristic UUIDs. You\u2019ll find a table with the values for all characteristics. The UUID for the temperature is 0x2A6E<\/strong>.<\/p>\n\n\n In summary, the UUIDs are:<\/p>\n\n\n\n The following code sets the Raspberry Pi Pico W or 2 W as a BLE peripheral with the Environmental Sensing Service<\/em> and the Temperature characteristic<\/em>. The BLE device will be writing on the Temperature<\/em> characteristic continuously to update it with the latest temperature and will be advertising its service and characteristic. We\u2019ll get the temperature from the Raspberry Pi Pico on-board temperature sensor (you need the picozero package installed<\/a><\/strong>).<\/p>\n\n\n View raw code<\/a><\/p>\n\n\n\n This example is based on the aioble<\/span> example that you can find here<\/a>.<\/p>\n\n\n\n Let\u2019s take a quick look at the relevant parts of the code for this example.<\/p>\n\n\n\n You need to include the aioble<\/span> and the bluetooth<\/span> libraries to use Bluetooth with the Pico.<\/p>\n\n\n\n Our code will be asynchronous. For that, we\u2019ll use the asyncio<\/span> library. We recommend following this tutorial to get familiar with asynchronous programming: Raspberry Pi Pico Asynchronous Programming \u2013 Run Multiple Tasks (MicroPython)<\/a>.<\/p>\n\n\n\n We define the UUIDs for the environmental sensing service and for the temperature characteristic.<\/p>\n\n\n\n Then, register the GATT service and characteristic.<\/p>\n\n\n\n When setting the characteristic, we set the read <\/em>and notify<\/em><\/span> arguments to True<\/span>. This defines the way that the central device can interact with the characteristic. It can read the characteristic and be notified when it changes.<\/p>\n\n\n\n To write the actual temperature value to the temperature characteristic, it needs to be in a specific format. The _encode_temperature()<\/span> function does that.<\/p>\n\n\n\n We have an asynchronous function that gets temperature from the internal temperature sensor and writes to the temperature characteristic using the write()<\/span> method on the temp_characteristic<\/span>. This task is repeated continuously every second. You can adjust the delay time as needed.<\/p>\n\n\n\n Besides writing to the temperature characteristic, we also need to advertise the Raspberry Pi Pico as a BLE service. For that, we use the peripheral_task()<\/span> function.<\/p>\n\n\n\n In that function, we define the BLE device name. <\/p>\n\n\n\n You can change its name if you want to. In the next example, we\u2019ll connect to this device by referring to its name, so you\u2019ll need to make sure you use the same name in both codes, as we\u2019ll see later.<\/p>\n\n\n\n Finally, we create an asynchronous main()<\/span> function, where we\u2019ll write the base for our code. We create two asynchronous tasks: one for advertising and another to write on the temperature characteristic.<\/p>\n\n\n\n Run the previous code on your Raspberry Pi Pico. It will start writing the temperature on the temperature characteristic and will advertise its service.<\/p>\n\n\n To connect to this peripheral, and read its characteristic we\u2019ll create a BLE Central device on another Raspberry Pi Pico board.<\/p>\n\n\n\n Before proceeding, you can use an app like nRF Connect<\/em><\/strong> to search for BLE devices and read their characteristics.<\/p>\n\n\n\n The nRF Connect<\/em> app from Nordic works on Android (Google Play Store) and iOS (App Store). Go to Google Play Store or App Store, search for \u201cnRF Connect for Mobile<\/strong>\u201d and install the app on your smartphone.<\/p>\n\n\n Go to your smartphone, open the nRF Connect app from Nordic<\/em>, and start scanning for new devices. You should find a device called RPi-Pico<\/strong>\u2014this is the BLE server name you defined earlier.<\/p>\n\n\n Connect to it. You\u2019ll see that it displays the Environmental Sensing<\/em><\/strong> service with the temperature <\/em><\/strong>characteristic. Click on the arrows to read the characteristic and activate the notifications.<\/p>\n\n\n Then, click on the second icon on the left to change the format (this option may only be available for iPhone, and it will automatically display the temperature in the correct format).<\/p>\n\n\n You can change the format to Unsigned Int.<\/p>\n\n\n\n You\u2019ll start seeing the temperature values being reported every 10 seconds. It will display the temperature in Celsius multiplied by 100 (on the iPhone).<\/p>\n\n\n Now that we know that our BLE peripheral is working as expected, we can program another Raspberry Pi Pico board as a BLE Central device to read the temperature characteristic from this board.<\/p>\n\n\n\n The following code should be run on another Raspberry Pi Pico board. We\u2019ll set it as a BLE Central device that will look for the RPi-Pico<\/strong> device, search for the environmental sensing service<\/em>, and read the temperature <\/em>from the characteristic.<\/p>\n\n\n View raw code<\/a><\/p>\n\n\n\n This example is based on the aioble<\/span> example that you can find here<\/a>.<\/p>\n\n\n\n Let\u2019s take a quick look at the relevant parts of the code for this example.<\/p>\n\n\n\nPrerequisites \u2013 MicroPython Firmware<\/h2>\n\n\n\n
\n
Bluetooth with the Raspberry Pi Pico W<\/h1>\n\n\n\n
\n
![\"Raspberry](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/RPi-Pico-2-Blink-LED-OFF.jpg?resize=750%2C422&quality=100&strip=all&ssl=1\")
What is Bluetooth Low Energy?<\/h2>\n\n\n
![\"Bluetooth](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2020\/03\/Bluetooth-low-energy.png?resize=400%2C129&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\nBluetooth Low Energy Basic Concepts<\/h2>\n\n\n\n
BLE Peripheral and Controller (Central Device)<\/h3>\n\n\n\n
![\"BLE](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/BLE-Peripheral-and-controler-RPi-PicoW.png?resize=750%2C459&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\nBLE Server and Client<\/h3>\n\n\n\n
![\"BLE](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/BLE-Server-Client-RPi-Pico.png?resize=750%2C307&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\nGATT<\/h3>\n\n\n\n
![\"BLE](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/BLE-GATT-structure.png?resize=750%2C466&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n\n
BLE Service<\/h4>\n\n\n\n
\n
UUID<\/h4>\n\n\n\n
55072829-bc9e-4c53-938a-74a6d4c78776<\/code><\/pre>\n\n\n\nCommunication between BLE Devices<\/h2>\n\n\n\n
![\"RPi](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/RPi-Pico-Communication-bwtween-BLE-devices.png?resize=750%2C761&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n\n
Installing the aioble <\/em>Package<\/h2>\n\n\n\n
![\"Install](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/aioble-package-rpi-pico-thonny-ide.png?resize=644%2C464&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n![\"Install](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/aioble-package-rpi-pico-thonny-ide-2.png?resize=644%2C464&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n
\n\n\n\nRaspberry Pi Pico BLE Peripheral and Central Device – Communication Between Two Boards<\/h2>\n\n\n\n
<\/figure><\/div>\n\n\nBLE Peripheral<\/h3>\n\n\n\n
\n
\n
Finding the Default UUIDs<\/h3>\n\n\n\n
![\"Characteristics](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/environmental-sensing-service-and-characteristics-SIG.png?resize=608%2C633&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n![\"BLE](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/environmental-sensing-service-uuid.png?resize=612%2C76&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n![\"BLE](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/BLE-temperature-uuid.png?resize=618%2C115&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n\n
\n
Code – Raspberry Pi Pico W as a BLE Peripheral<\/h2>\n\n\n\n
# Rui Santos & Sara Santos - Random Nerd Tutorials\n# Complete project details at https:\/\/RandomNerdTutorials.com\/raspberry-pi-pico-w-bluetooth-low-energy-micropython\/\n\nfrom micropython import const\nimport asyncio\nimport aioble\nimport bluetooth\nimport struct\nfrom picozero import pico_temp_sensor\n\n#org.bluetooth.service.environmental_sensing\n_ENV_SENSE_UUID = bluetooth.UUID(0x181A)\n# org.bluetooth.characteristic.temperature\n_ENV_SENSE_TEMP_UUID = bluetooth.UUID(0x2A6E)\n# org.bluetooth.characteristic.gap.appearance.xml\n_ADV_APPEARANCE_GENERIC_THERMOMETER = const(768)\n# How frequently to send advertising beacons.\n_ADV_INTERVAL_MS = 250_000\n\n# Register GATT server.\ntemp_service = aioble.Service(_ENV_SENSE_UUID)\ntemp_characteristic = aioble.Characteristic(\ntemp_service, _ENV_SENSE_TEMP_UUID, read=True, notify=True)\naioble.register_services(temp_service)\n\n# Helper to encode the temperature characteristic encoding\n# (sint16, hundredths of a degree).\ndef _encode_temperature(temp_deg_c):\n return struct.pack("<h", int(temp_deg_c * 100))\n\n# Get temperature and update characteristic\nasync def sensor_task():\n while True:\n temperature = pico_temp_sensor.temp\n temp_characteristic.write(_encode_temperature(temperature), send_update=True)\n print(temperature)\n await asyncio.sleep_ms(1000)\n \n# Serially wait for connections. Don't advertise while a central is connected.\nasync def peripheral_task():\n while True:\n try:\n async with await aioble.advertise(\n _ADV_INTERVAL_MS,\n name="RPi-Pico",\n services=[_ENV_SENSE_UUID],\n appearance=_ADV_APPEARANCE_GENERIC_THERMOMETER,\n ) as connection:\n print("Connection from", connection.device)\n await connection.disconnected()\n except asyncio.CancelledError:\n # Catch the CancelledError\n print("Peripheral task cancelled")\n except Exception as e:\n print("Error in peripheral_task:", e)\n finally:\n # Ensure the loop continues to the next iteration\n await asyncio.sleep_ms(100)\n\n# Run both tasks\nasync def main():\n t1 = asyncio.create_task(sensor_task())\n t2 = asyncio.create_task(peripheral_task())\n await asyncio.gather(t1, t2)\n \nasyncio.run(main())\n<\/code><\/pre>\n\tHow the Code Works<\/h3>\n\n\n\n
Include Libraries<\/h4>\n\n\n\n
import aioble\nimport bluetooth<\/code><\/pre>\n\n\n\nimport asyncio<\/code><\/pre>\n\n\n\nDefine UUIDs and Register the GATT Service and Characteristic<\/h4>\n\n\n\n
# org.bluetooth.service.environmental_sensing\n_ENV_SENSE_UUID = bluetooth.UUID(0x181A)\n\n# org.bluetooth.characteristic.temperature\n_ENV_SENSE_TEMP_UUID = bluetooth.UUID(0x2A6E)<\/code><\/pre>\n\n\n\n# Register GATT server.\ntemp_service = aioble.Service(_ENV_SENSE_UUID)\ntemp_characteristic = aioble.Characteristic(\n temp_service, _ENV_SENSE_TEMP_UUID, read=True, notify=True\n)\naioble.register_services(temp_service)<\/code><\/pre>\n\n\n\ndef _encode_temperature(temp_deg_c):\n return struct.pack(\"<h\", int(temp_deg_c * 100))<\/code><\/pre>\n\n\n\nGet Temperature and Write on Characteristic<\/h4>\n\n\n\n
# Get temperature and update characteristic\nasync def sensor_task():\n while True:\n temperature = pico_temp_sensor.temp\n temp_characteristic.write(_encode_temperature(temperature), send_update=True)\n print(temperature)\n await asyncio.sleep_ms(1000)<\/code><\/pre>\n\n\n\nAdvertising<\/h4>\n\n\n\n
# Serially wait for connections. Don't advertise while a central is connected.\nasync def peripheral_task():\n while True:\n try:\n async with await aioble.advertise(\n _ADV_INTERVAL_MS,\n name=\"RPi-Pico\",\n services=[_ENV_SENSE_UUID],\n appearance=_ADV_APPEARANCE_GENERIC_THERMOMETER,\n ) as connection:\n print(\"Connection from\", connection.device)\n await connection.disconnected()\n except asyncio.CancelledError:\n # Catch the CancelledError\n print(\"Peripheral task cancelled\")\n except Exception as e:\n print(\"Error in peripheral_task:\", e)\n finally:\n # Ensure the loop continues to the next iteration\n await asyncio.sleep_ms(100)<\/code><\/pre>\n\n\n\nname=\"RPi-Pico\",<\/code><\/pre>\n\n\n\nMain Function<\/h4>\n\n\n\n
# Run both tasks.\nasync def main():\n t1 = asyncio.create_task(sensor_task())\n t2 = asyncio.create_task(peripheral_task())\n\n await asyncio.gather(t1, t2)\n\nasyncio.run(main())<\/code><\/pre>\n\n\n\nTesting the Code<\/h3>\n\n\n\n
![\"RPi](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/RPi-Pico-advertising-BLE-service-thonny-IDE.png?resize=674%2C262&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\nnRF Connect App<\/h4>\n\n\n\n
![\"nRF](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/nRF-connect-app-test-BLE-devices.png?resize=250%2C541&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n![\"Scanning](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/scanning-rpi-pico-BLE-device.png?resize=250%2C541&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n![\"RPi](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/rpi-pico-read-characteristic-on-nrf-connect-app.png?resize=250%2C541&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n![\"nRF](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/nrf-connect-change-format-icon.png?resize=60%2C60&quality=100&strip=all&ssl=1\"){kind=icon}
<\/figure><\/div>\n\n\n![\"nRF-connect-change-data-to-unsigned-int\n\"](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/nrf-connect-change-data-format-unsigned-int.png?resize=500%2C89&quality=100&strip=all&ssl=1\")
<\/figure>\n\n\n\n![\"RPi](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/RPi-Pico-as-bLE-device-read-temperature-value.png?resize=500%2C659&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\nCode – Raspberry Pi Pico as a BLE Central Device (BLE Client)<\/h2>\n\n\n\n
# Rui Santos & Sara Santos - Random Nerd Tutorials\n# Complete project details at https:\/\/RandomNerdTutorials.com\/raspberry-pi-pico-w-bluetooth-low-energy-micropython\/\n\nfrom micropython import const\nimport uasyncio as asyncio\nimport aioble\nimport bluetooth\nimport struct\n\n# org.bluetooth.service.environmental_sensing\n_ENV_SENSE_UUID = bluetooth.UUID(0x181A)\n# org.bluetooth.characteristic.temperature\n_ENV_SENSE_TEMP_UUID = bluetooth.UUID(0x2A6E)\n\n# Name of the peripheral you want to connect\nperipheral_name="RPi-Pico"\n\n# Helper to decode the temperature characteristic encoding (sint16, hundredths of a degree).\ndef _decode_temperature(data):\n try:\n if data is not None:\n return struct.unpack("<h", data)[0] \/ 100\n except Exception as e:\n print("Error decoding temperature:", e)\n return None\n\nasync def find_temp_sensor():\n # Scan for 5 seconds, in active mode, with a very low interval\/window (to\n # maximize detection rate).\n async with aioble.scan(5000, interval_us=30000, window_us=30000, active=True) as scanner:\n async for result in scanner:\n print(result.name())\n # See if it matches our name and the environmental sensing service.\n if result.name() == peripheral_name and _ENV_SENSE_UUID in result.services():\n return result.device\n return None\n\nasync def main():\n while True:\n device = await find_temp_sensor()\n if not device:\n print("Temperature sensor not found. Retrying...")\n await asyncio.sleep_ms(5000) # Wait for 5 seconds before retrying\n continue\n\n try:\n print("Connecting to", device)\n connection = await device.connect()\n except asyncio.TimeoutError:\n print("Timeout during connection. Retrying...")\n await asyncio.sleep_ms(5000) # Wait for 5 seconds before retrying\n continue\n\n async with connection:\n try:\n temp_service = await connection.service(_ENV_SENSE_UUID)\n temp_characteristic = await temp_service.characteristic(_ENV_SENSE_TEMP_UUID)\n except asyncio.TimeoutError:\n print("Timeout discovering services\/characteristics. Retrying...")\n await asyncio.sleep_ms(5000) # Wait for 5 seconds before retrying\n continue\n\n while True:\n try:\n temp_data = await temp_characteristic.read()\n if temp_data is not None:\n temp_deg_c = _decode_temperature(temp_data)\n if temp_deg_c is not None:\n print("Temperature: {:.2f}".format(temp_deg_c))\n else:\n print("Invalid temperature data")\n else:\n print("Error reading temperature: None")\n except Exception as e:\n print("Error in main loop:", e)\n break # Break out of the inner loop and attempt to reconnect\n\n await asyncio.sleep_ms(1000)\n\n# Create an Event Loop\nloop = asyncio.get_event_loop()\n# Create a task to run the main function\nloop.create_task(main())\n\ntry:\n # Run the event loop indefinitely\n loop.run_forever()\nexcept Exception as e:\n print('Error occurred: ', e)\nexcept KeyboardInterrupt:\n print('Program Interrupted by the user')\n<\/code><\/pre>\n\tHow the Code Works<\/h2>\n\n\n\n
Include Libraries<\/h4>\n\n\n\n
![\"Thonny](\"https:\/\/i0.wp.com\/randomnerdtutorials.com\/wp-content\/uploads\/2025\/05\/thonny-ide-allow-multiple-instances.png?resize=561%2C558&quality=100&strip=all&ssl=1\")
<\/figure><\/div>\n\n\n