Sensor keeps disconnecting

[Fbrufino]

Hi guys. First off, congrats for a great app, I'm really enjoying it so far.

The problem I have is my Polar H10 keeps disconnecting exactly 150 seconds after connection -- importantly, I'm referring to system-wide connection and disconnection, not within the app --, which is the same behavior I get when I just connect the H10 to the system and do nothing with it.

What made me conclude it's something related to the software -- or that the software can override, at least -- is that the same thing doesn't happen when I use another python HRV training module called Every Breath You Take (although I much prefer OpenHRV's feedback and recording capability).

I've tested this on two machines, and the behavior is the same across them:

1. Debian 12, 6.1.0-20-amd64 kernel, TP-Link UB500 USB bluetooth adapter;
2. Debian 12, 6.8.8-x64v3-xanmod1, onboard bluetooth adapter

Polar H10 info:

• Firmware Revision: 5.0.0
• Hardware Revision: 00760690.03
• Software Revision: 3.2.0

I've tried changing /etc/bluetooth/input.conf, setting idletimeout=0 and userspaceHID=true, all with no success.

[JanCBrammer]

Thanks for the issue and thorough investigation @Fbrufino! I can confirm the issue on Ubuntu 22.04.4 (6.5.0 kernel) with an onboard Bluetooth adapter (Intel Corp. AX200 Bluetooth), OpenHRV 1.0.0, and a Polar H9 (firmware version 1.0.6). I'll dig into this if I find time. Which version of OpenHRV are you using? Are you running OpenHRV.bin from https://github.com/JanCBrammer/OpenHRV/releases/tag/v1.0.0, or via python -m openhrv.app?

[Fbrufino]

Sorry, I did forget to mention I'm using OpenHRV 1.0.0 via python -m openhrv.app, CPython v3.9.11.

Don't know if it's relevant, but I couldn't determine if the disconnection is issued by Linux or the sensor, but my initial assumption is it's the sensor.

[JanCBrammer]

My initial hypothesis is that the disconnection is caused by a Qt timeout.
Every time the sensor disconnects, the following line shows up in the terminal:

OpenHRV/openhrv/sensor.py

Line 151 in 211d4ce

print(f"Discarding sensor at {self._sensor_address()}.")

[Fbrufino]

My initial hypothesis is that the disconnection is caused by a Qt timeout. Every time the sensor disconnects, the following line shows up in the terminal:

OpenHRV/openhrv/sensor.py

Line 151 in 211d4ce

print(f"Discarding sensor at {self._sensor_address()}.")

I dunno, if I understood correctly that would be something the application does. The fact that either launching OpenHRV or doing nothing with the sensor (i.e. don't launch any application that interacts with it) after connection have the exact same result (disconnection from Linux after 150 secs) points me toward some internal configuration within the sensors to avoid idle connections.

Crucially, during some rounds of testing in the last few days, I ended up discovering that if I launch Every Breath You Take after connection, I can close it immediately after the app shows the first data points and then the sensor no longer disconnects even if I do nothing with it. So, as well as being a temporary workaround, this suggests the issue is something OpenHRV is not doing, rather than something it is doing. More exactly, I think there's some signal the Polar sensors are expecting in order to conclude that the connection is an "active" or valid one, and EBYT is sending that, possibly indirectly through its usage of bleak.