• State Verified Answer
  • Replies 1 reply
  • Subscribers 87 subscribers
  • Views 655 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 273081
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

receiving BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION when trying to connect to bonded HRS POLAR watch

Erikk

I am using the softdevice S132 with my nRF52832 and am running into a problem with a heart rate band by POLAR.

The Problem is that I get a disconnect from the HRS side (BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION).

It occurs when I first bond with the HRS, then turn the HRS off and on again. My device will send a connect request since it has the HRS saved as a peer and it is advertising again.

But then after the connect request and the first read request of characteristics, the HRS send BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION. This can be seen in the wireshark log file attached. message 1115 is the reconnect and message 1125 is the deconnection triggers by the HRS band.

Notes:

- other HRS like a HRS belt work fine

- when using the HRS band with nRF connect and trying to bond, a PIN is required. when I bond I do it with Just Works

- its not due to connection parameters (I set exactly the requested ones)

- strangely the HRS band will show that it's connected by my device is not connected. the HRS deletes my device as a peer after this second connection but before had it as peer

- I also tried with LESC but its not working

Thank you for any help.

wireshark in google drive: https://drive.google.com/file/d/1vEPYtHKzu5OBJZjGI4GQ6MgVzPxHwEtg/view?usp=sharing

Parents
  • +1

    I could somehow solve the problem with a workaround.

    What I did previously was to initiate bonding as soon as I connected even with already bonded devices. The bonding caused an error on my side.

    Now upon successful connection when in "whitelist scanning mode" and I don't want to connect to a new device, I do not bond anymore and just start the service discovery instead.

    - My device has the watch saved as a peer and finds it in the whitelist and then connects to it when the HRS advertises

    - The HRS does NOT have my device as a peer. But since I do no longer start a new bonding this is no problem

    - The HRS still sends a disconnect but somehow this doesn't matter

Reply
  • +1

    I could somehow solve the problem with a workaround.

    What I did previously was to initiate bonding as soon as I connected even with already bonded devices. The bonding caused an error on my side.

    Now upon successful connection when in "whitelist scanning mode" and I don't want to connect to a new device, I do not bond anymore and just start the service discovery instead.

    - My device has the watch saved as a peer and finds it in the whitelist and then connects to it when the HRS advertises

    - The HRS does NOT have my device as a peer. But since I do no longer start a new bonding this is no problem

    - The HRS still sends a disconnect but somehow this doesn't matter

Children
No Data
Related
Terms of service