You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! First, thank you for creating this client. I'm trying to use it with the R09 ring model (which does use the QRing application) and have encountered some issues:
Current Behavior
The client has intermittent connection issues with the R09 ring
After successfully connecting once (for example able to get heart rate log settings), subsequent connection attempts fail with BleakDeviceNotFoundError
Here I first successfully use: colmi_r02_client --debug --name R09_0605 get-heart-rate-log-settings
And afterwards non-successfully (an example): colmi_r02_client --debug --name R09_0605 get-heart-rate-log
Real-time heart rate monitoring fails with the same issue - it initially connects for basic information but fails with BleakDeviceNotFoundError when trying to get the actual heart rate data
Environment
OS: macOS 23.6.0
Python version: 3.13
Ring model: R09
Questions
Are there any specific connection requirements for the R09 model that differ from other models that you know of?
Is there a way to maintain a stable connection with the R09 for operations that require multiple interactions?
Let me know if you need any additional information!
Thanks for the great work!
The text was updated successfully, but these errors were encountered:
Hi! First, thank you for creating this client. I'm trying to use it with the R09 ring model (which does use the QRing application) and have encountered some issues:
Current Behavior
BleakDeviceNotFoundError
Here I first successfully use:
colmi_r02_client --debug --name R09_0605 get-heart-rate-log-settings
And afterwards non-successfully (an example):
colmi_r02_client --debug --name R09_0605 get-heart-rate-log
BleakDeviceNotFoundError
when trying to get the actual heart rate dataEnvironment
Questions
Let me know if you need any additional information!
Thanks for the great work!
The text was updated successfully, but these errors were encountered: