Request for Bluetooth LE Advertisement Parsing Data for Hearing Aids (Phonak, Oticon, Widex, ReSound, etc.)

[bertie25795]

Hello everyone,

I'm developing a mobile application called "Bluetooth Bertie" - designed to help users stop losing their hearing aids and locate lost devices, with a particular focus on hearing aids (and TWS earbuds).

The core functionality relies on parsing manufacturer-specific data from Bluetooth Low Energy (BLE) advertisements to retrieve critical information such as:

Individual Left/Right device connection status: For TWS (True Wireless Stereo) devices and bilateral hearing aids, determining if both the left and right components are connected to the Master device.
Individual Left/Right battery levels: Obtaining the battery percentage for each earbud/hearing aid and potentially the charging case.
Specific device identification: Beyond generic Bluetooth names, identifying the exact model and type (e.g., "Phonak Audéo Lumity," "Oticon More Left").
We currently have robust parsing logic for popular consumer earbuds like Apple AirPods and Samsung Galaxy Buds, often leveraging existing community-contributed research.

We are now seeking similar detailed parsing specifications or any reverse-engineered information for popular hearing aid brands, including but not limited to:

Phonak (e.g., Audéo, Paradise, Lumity models)
Oticon (e.g., More, Real models)
Widex (e.g., Moment, PureSound models)
GN ReSound (e.g., ONE, Nexia models)
Starkey (e.g., Evolv AI, Genesis AI models)
Any other major hearing aid manufacturers prevalent in the UK/European market.
Specifically, we are looking for insights into:

Manufacturer Specific Data (AD Type 0xFF): How is the data structured for these devices? What byte offsets contain connection status, battery levels, and other relevant metrics for individual components of a pair?
GATT Services/Characteristics: Are there specific standard (e.g., Battery Service UUID 0x180F) or proprietary GATT characteristics that expose this information when connected?
Advertisement Data Patterns: Any unique patterns in their general advertisement packets that indicate connection state or device type.
Why this information is crucial for our app:

For TWS devices and hearing aids, the phone often only connects to one "Master" device, which then communicates with its "Slave" counterpart. Our app needs to understand the proprietary messages sent by the Master to determine the status (connected, disconnected, battery level) of both the Master and Slave components. This allows us to accurately tell a user, for example, "Your Left Phonak has disconnected!" and log the location where that disconnection was detected.

Any existing research, documentation, code snippets, or pointers to relevant discussions would be immensely helpful. We believe that by collectively understanding these proprietary communication methods, we can build more powerful and useful tools for users.

Thank you in advance for any contributions or guidance you can provide!

Best regards,

Bertie