No valid data from Garmin HRM-Dual

The connection to my Garmin watch is ANT+, the connection to my mobile phone is via BLE.

I'd like to point out one more fact: Some other random heart rate app on my mobile phone successfully shows the data from the heart rate monitor.

Hello Menion,

Thanks for your effort. My mobile phone is a Samsung M31 and unfortunately it does not support ANT.

Please keep me updated here if the update is done or if you stumble upon anything.

Thanks

Hello Menion,

Thanks for caring about my issue, but I'm afraid the problem persists.

You mentioned that no other user has reported this issue yet. Well, I don't know how many users have the same combination of hardware (Samsung M31, Garmin HRM-Dual) and software (Android Version, HRM-Firmware).

Hello Stefan,

persist, hmm. Are you willing to invest some time and give a try to the special version that will print out some information into the log? No matter what combination are you using, this really should work. Let me know.

Menion

Sure, I'll try.

Hello Stefan,

so if you have a moment, please give a try to one more test:

- Beta version: http://bit.ly/lmVersionsTest

- after install > long click on the app main menu and enable "Log to file"

- then try to connect to your "Garmin HRM" as a common "BT4 Heart rate monitor"

- once you will be sure, there should be a HR values, just close Locus Map app

- send me log that may be found in the Locus/logs directory,

Thanks!

As I own HRM-Dual I can help with this test as well. I know that many people are having the same problem with other apps and Garmin is not able to help, probably we will finally figure out what is the problem and provide them relevant data.

Hello Roman, thanks very much, appreciate it.

Seems that ANT+ connection works correctly right?

In case of BT4, it is interesting. Sensor seems to be correctly detected, app also correctly asks for data, but no data are received. It seems you have disabled connection manually after 10 seconds. On my own Polar HRM, it usually takes 10 - 20 seconds till it starts report fresh data, so did you tried to let it be longer? Also, does this HR belt works with any other application? Just for sure ...

Menion

Its fw version was 2.30, tried to wait a bit longer (still not receiving any data) + connected my watch to it via ant+ (no issues). In nRF Connect is no field containing HRM visible. So wanted to connect to Garmin edge via BLE, but it proposed an update to 2.50... after update (not sure if it was working before) I have connected it via BLE to Edge and no issues, but I really have no idea how it can receive these as I still don't see any relevant data in nRF Connect. And still no HRM in Locus. Will try to sniff it with my nRF52840

Edit: In nRF Connect with connected nRF52840 as a sniffer and in nRF Connect on my mobile phone it is fine - showing HRM, but still no HRM in Locus.

Hmm, seems you are a lot more skilled then me, at least based on technical hardware you use :). Nice.

I just today morning hopefully fixed minor issue in reading of "power meter" values where app incorrectly registered for read-only characteristics and waited for notifications. This is just fixed in published MapGooglePlay_4.4.3.5_1044_beta . May you give a try to this version and if this won't work, log with BT connection will be welcome, thanks a lot!

Menion

I have the tools (wanted to play with BLE and ANT+, but had no time to actually work with), but I have no idea what I am doing :D I have attached log from sniffer - maybe it will help...

Yea, I will try and I can try power meter as well as I have two, well three, powermeters - 4iii, Garmin Rally RS200 (double side) and then TACX Neo 2T trainer (ANT+ FE-C and it can advertise power/cadence via BLE).

Because quite a lot has changed during last 24 hours, may you please also try this Garmin HR monitor with recent MapGooglePlay_4.4.3.9_1044_beta version? Thank you very much!

Still no data

Thanks to work we did last day, I see clearly in logs that app tries to connect to Dual HRM, request correctly data, but seems you waited 20 seconds and absolutely no data were received.

As I see on the internet like here and many other places, there is many many users who has troubles with this device. Till I or anyone find any hack, I have no other ideas so from my point of view, this device belongs to new category "Unsupported".

Just tried it again this time with nRF connect and I got data, then I connected Locus (it is able to handle two BLE sessions) to it and it is showing battery and heart rate. I would say it is supported, just sometimes it has issues that can't be fixed on Locus side.

Thanks for your interest in this issue Roman Priesol.

@Menion, I had no time to produce the logs yet. However I followed the comments here and I'm wondering if my logs are still needed.

If so, please let me know.

I think they aren't. There is nothing more I need to know or that helps me here.

In the mentioned topic, also as Roman confirmed, few users wrote that some side-connection may push the sensor to work. I'm not sure, but from a few articles and discussions I read, it really looks like the software in this HRM device does not work correctly. Sorry ... next time rather purchase Polar or any other HR device... thanks for understanding.

Jiří M. aka Menion

I have been getting the same "No valid data" for Polar H10 ever since the new sensor management has been introduced. If I want to connect the sensor, I usually have to remove it completely from Locus and add it again. Disconnect/Connect from Locus rarely works. So normally I connect it, it works for a random amount of time correctly, then the heart rate stops getting updated and "No valid data" is shown on the sensor screen while the sensor is still connected. I have to remove the sensor and add it again for Locus to start showing (and logging) the heart rate again.

edit: using Locus 4.4.3, gold

Hello Phil, I just solved minor issue in reconnecting to some BT4 sensors, that may hopefully fix also a problem to you.

Wait please to next app version. If same issue happens again with this new version, please let me know in separate topic. It will need a little more testing with special version.

Thanks!