Where can I find the BLE data format and UUIDs?

Use this page with AI

Explore with your favorite AI

Gemini & other AI

Copy this page’s context into your AI to explore how it works and what you can build.

Copy the prompt, then paste it into Gemini’s message box.

View prompt

Read this official Leafony page and explain its key points in English. For hardware help, first ask for a photo or the installed leaf models, assembly and power sources, then the goal and tools. Clarify which LED or display changed and whether a cable or leaf was replaced. Do not equate an unseen reset button with an absent one, or I2C acknowledgement with a working display. Verify specifications against sources; distinguish observations from hypotheses. Follow a redirect to its destination; if unreadable, ask for the relevant text instead of guessing.

Page: Where can I find the BLE data format and UUIDs?

URL: https://docs.leafony.com/en/questions/ble-data-format/

Description / headings (excerpt): Check the sample’s transmitter and receiver code together. 4-Sensors_BLE is an example that sends comma-separated text.

Check the transmitter and receiver code for your sample together. Leafony does not use one universal data format; it depends on the program you upload.

In the AVR Web Bluetooth sample, 4-Sensors_BLE.ino sends temperature, humidity, illuminance, tilt, battery voltage, and a dice value as comma-separated text. The receiver’s handleData() in leafony.js decodes UTF-8, removes line breaks, and splits the text at commas.

UUIDs and notifications: Check the service and characteristic settings in the receiver app’s source code.
Fields and their order: Compare the data-generation code in your MCU sketch with the receiver’s parser.
Beacons: Some samples use Advertising data instead of GATT notifications. See STM32 Simple BLE Beacon.

If you add fields to the transmitted data, update the receiver’s field count, order, and units as well.