You will get the message at first connection after every software update. That is, if the HR strap is connected in BLE. You just have to acknowledge. Either the native connection or AlphaHRV is in BLE, so you’ll get it anyway.
There’s no strict necessity to encrypt, but EU law requires to let the user know if it isn’t.
That’s why you get the message after every software update. And also after a ‘reset to factory’.
About the only benefit I could see after our insane decision to leave the EU was that we wouldn’t be subject to some of the more bureaucratic and controlling dictates that they issue from time to time. Sadly and unsurprisingly the rest of the world doesn’t bother using a slightly different product or software update for us and just lumps us in with the EU.
I’ve been reading through this thread and it seems like this group is really knowledgeable about HRV data and Garmin devices, even if my specific question isn’t about alphaHRV!
I’m an AI Endurance user, so getting accurate and complete HRV data is super important for my training guidance.
I use the Garmin Forerunner 965 and the HRM-Pro Plus strap.
For the winter, I’ll be doing a lot of treadmill running, and I need my Running Dynamics from the HRM-Pro Plus. This brings up a couple of questions:
ANT+ for Running Dynamics: Is it true that the Running Dynamics data from the HRM-Pro Plus only calculates and transfers to the Forerunner 965 when the strap is connected via ANT+?
HRV Data Transfer (Offloading): If I have to use ANT+ for the Running Dynamics, is there still a way to get the full HRV data to sync?
I know the HRM-Pro Plus has an offloading feature (like for swimming, it downloads the data from the strap after the activity), but I’m unsure if that data includes the complete HRV information and if it can be accessed/synced to AI Endurance if I don’t connect the strap via Bluetooth to the watch during the run.
Essentially, is there a way I can get both Running Dynamics (via ANT+) and the complete HRV data for AI Endurance when running indoors?
The 965 can measure all running dynamics except GCT balance from the wrist. So if you connect the strap via BLE, you’ll still get most running dynamics.
I’m curious what you use running dynamics for - personally I haven’t found them very actionable.
Not really, starting at L/R balance – which I actively use, even from the indoor trainer.
As I am considering to move from Wahoo to Garmin, that’s interesting/worrisome: does this limit include all fields, e.g., speed, advanced cycling metrics, etc.?
Are you saying the Tymewear HR sensor is sufficiently for (good) HRV measurements?
Not sure if there is a misunderstanding. Garmin can connect with standard sensors and get information from them with no restriction as your current Wahoo likely does. Garmin also allows 3rd party developers to build custom data fields (small pieces of software that run inside the main activity app) that can show information on the screen. Usually these data fields use some information (speed, hr, power, etc) that your Garmin exposes to them. However, there are some case where the 3rd party data fields need to establish s direct connection with a specific sensor to get information that Garmin wouldn’t expose to them (for example raw RR-ints) In these cases, it is not possible to connect the sensor to Garmin (native standard connection) and to the 3rd party data field simultaneously under the same mode (ANT or BLE).
If you are not using these kind of data fields you don’t need to worry about. If you use them, sensors supporting both ANT and BLE parallel connections are the best solution.
Tymewear has used several HRM till now. I haven’t checked the latest one provided now with the vital pro strap for HRV, but previous ones work fine. BTW you can attach any other HRM (H10, Garmin, …) that you feel confidence with to the strap
Hola Inigo no logro que carregue los datos me aparece el mensage " collection data 0%"
Y no passa de esso. El HR si me mostra y lá potencia, Pero nada mas. Que ago para funcionar és un Garmin 530?
First try to remove the HR sensor pairing with your device. Then check if the AlphaHRV IQ field connects to the HR sensor.
You can’t use ANT+ or BLE for both connections. If one is BLE, then the other must be ANT+.
Though unfortunately the pin distance or some other alignment doesn’t match perfectly BTW so when I put on my H10 sensor, it clicks out quite easily by accident. I wish there was a more precise standard for this…
Yeah, the H10 pins are a bit “recessed” and the original Polar strap has some “knobs” on the strap… but for me it works nicely once it’s on. I put on the strap without the sensor and then click in the sensor last… and then it holds.
After updating my Polar H10 heart rate monitor to firmware version 4.1.10 , the alphaHRV data field on my Garmin watch is no longer able to connect to it via Bluetooth (BLE) . alphaHRV was working perfectly before this update.
The alphaHRV data field fails to find the H10 over BLE (after full reset, not paired, no other apps connected). The connection still works flawlessly over ANT+.
Just a guess: could be that they want to fulfil EU regulation, and are encrypting BLE.
Is there an option to disable encryption? For Garmin sensors it’s possible to disable it.
No, there isnt that option with firmware version 4.1.10.
Garmin BLE normal connection to H10 is always encrypted, as Ant+ connection to H10 is always unencrypted.
And if Garmin is using Ant+, AlphaHRV datafield cannot find the H10.
I’ve had something similar happen with a couple of my power meters which suddenly ( possibly after an update) stopped connecting automatically to my head unit. I have to manually connect them every time. I’ve no idea why but speculated that it might be something to do with EU legislation. I also get seemingly random messages saying that something is using an open connection..
I don’t have exact knowledge of the different situations but this might help:
Make sure all your sensors are OFF! For Polar H10, disconnect the POD from the strap because the slightest movement will wake it up.
Start your Garmin device (if it is a head unit) or start an activity (if it is a watch), to initiate sensor search.
Now, activate one of your sensors. If it has been connected before in BLE, you will probably get a notification on your device that it either is being connected or the message that it will use an ‘Unsafe’ connection. That message needs to be acknowledged and, if my theory is correct, no longer be displayed on future connections. Unless your device got an update, then it will reappear and must be acknowledged again.
Do this for every sensor with BLE connection.
When it comes to AlphaHRV, I’m not sure if the above will work, but if you use BLE on AlphaHRV, it’s probably a good idea to first connect the H10 as a standard HR sensor on the device to be able to acknowledge the message. Then disconnect the BLE mode again to make it available for AlphaHRV.
PS: it has been mentioned before that it is better to connect the H10 to the device in BLE and to AlphaHRV in ANT+. That will ensure that the HRV measured by Garmin (if enabled) is also correct. The Garmin BLE stack has an issue where R-peaks may be missed at high HR. AlphaHRV does not have that issue because it uses it’s own connection protocol. Alphahrv is always correct in both BLE and ANT+.
In settings > Sensors & Accessories Delete all parings to Polar H10,
Add new, Search for External Heart Rate, add the ANT+ connection.
Repeat the process for BLE and
After that, alphaHRV does find the Polar H10 sensor in unencrypted BLE mode.