Skip to content

Using BLE for Heart Rate Monitors, newer belts don't work #837

Closed
@Vulture-in-the-woods

Description

@Vulture-in-the-woods

Hi Neil.

First of all thank you for your library and the subsequent work you've been putting in it.

I've been using your library together with the ESP32 and a 64x32 RGB LED matrices to show my Heart rate while I work out. The idea is based on a sketch by Andreas Spiess, which I use as a test/benchmark file.
I've been using it toghter with a Polar H7 pulse belt and everything has been working like a charm, so far.

Now I've gotten two new puls pelts, the Polar H10 and the Wahoo Tickr.
Both of them show the same GATT with the Service UUID 0x180D and CharUUID 0x2A37
Neither connects to the ESP32, that is, they get to the "- Created client" step, but not the "- Connected to server" which is given by these lines of code:

BLEClient* pClient = BLEDevice::createClient();
Serial.println(" - Created client");

// Connect to the remove BLE Server.
pClient->connect(pAddress);
Serial.println(" - Connected to server");

I've tried changing the CharUUID in case the sensor had 0x2A38 or 0x2A39 instead for what ever reason, but nothing helps.

I can find both belts on my Iphone SE, and connect to them via apps like the Wahoo Fitness app, Polar Beat and Endomondo.

I can also see them via the nRF Connect app and verify that the serviceUUID infact is 0x180D

The common denominator for these belt are that they have some sort of extra capacity, primarily memory function

My questions are:

What is the difference which prohibits me from connecting the ESP32 to the pulse belt?
Which measures could be taken to make the BLE connection work in order for the belts to connect to the ESP32?

Best Regards
Erik

bluetooth_andreass_spiess.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions