I also have that. Easiest way to reset is to briefly change profiles. I created a separate profile on my Edge for that with only one field (speed for example). Tap the screen, go to Home, change profile and immediately return to your normal profile. AlphaHRV will reinitialize.
This may be the key clue. Suspension causes some issues because the data field keeps some previous state partially when you wake up the device. Connection to sensors can be affected by this (I have even read some issues with native connection from some Garmin users)
I guess that going to alphaHRV in the store, you are just forcing a clean reinitialization. If this is the case, the solution is more simple and does not need using the phone Follow any of this procedures:
- A) For any device (touch and non touch screen)
Before entering into the activity profile you will use, move to another one in the main screen of your Garmin and come back again. For instance, if you will use ROAD, go to INDOOR (just show it, no need to enter) and come back again to ROAD - B) For touch screen devices
Full screen layout: Change alphaHRV by any other data field and set it again: long touch on alphaHRV ā tap on it ā select any (for instance distance) ā long touch on distance ā tap on it ā select alphaHRV
If alphaHRV is not using full screen size, just move it to another position: long touch on alphaHRV ā tap on any other data field
By the way, correct me but I donāt see any advantage using suspension instead of powering off the device. Powering off after finishing the activity is quite more clean and avoids issues caused by suspension
1 Like
@MedTechCD it seems we have noticed the same point.
In fact, a specific profile is not needed. You can go to any even if alphaHRV is also set for it
Thatās clear. I was referring to the data you select to be displayed. TV (tidal volume) doesnāt show strict increasing trend with intensity and I donāt see how you use it already having VE and BR. You have other configurable options to display
1 Like
I implemented it that way for a couple of reasons:
- If you notice that it is stuck when you already resumed your ride, switching to āIndoorā for example will write a couple of samples without GPS data to the FIT and that can cause errors in speed/altitude charts.
- I do use the suspension mode on longer rides with a significant break, like 30+ minutes for a meal or a coffee-stop for example. On short stops, when remaining outside with GPS signal, I simply Pause the unit.
- I also have seen the Power meter not reconnecting in some of those occasions. The switch to a very basic profile with only one non-IQ field and GPS activated, resolves that too.
Iām now used to this method and have basically no problems with resulting FIT files.
2 Likes
Just be careful on the position of the empty profile relative to the one you are using. To avoid non desired content on the fit file, you have not to go through any other profile to reach it. Activity profiles are initiated just when the icon is shown in the screen menu. The empty profile has to be immediately on the left or right of the one you are using, so that you reach it directly
1 Like
Exactly, I have it in between my Ride and Indoor profile and named it ResetAlpha.
1 Like
The tymeware CIQ app always has 3 values IIRC. I have VE displayed as main value, and two smaller numbers/displays for BR and VT. I effectively use only VE during rides. I use BRR (BR-reserve) in comparison to HRR in post-ride analysis.
Reading your comment again, I have to check and see how I display the tyme-data betterš
But thatās only relevant if I do this after starting the recording, not?
Yes, only if you have already started the activity
1 Like
I have been doing some test with my Garmin HRM Pro Plus, that I think clarify how Garmin HRMs can be used with alphaHRV
- Using ANT for alphaHRV and BLE for the native deviceās connection
This configuration works normally. The sensor sends RR-int values, so that alphaHRV can process the data.
Although it could be enough for cycling, runners are missing all running metrics in their Garmin watches, because they are only transmited in ANT mode. - Using BLE for alphaHRV and ANT for the native deviceās connection
In this case, running metrics are available in the Garmin watch, but alphaHRV is stuck at āCollecting data ā¦ā usually at 0%. The reason is that the sensor behaves as a simple HRM that only provides HR values, but not RR-ints, so alphaHRV shows HR values, but it canāt collect data needed for DFA.
This was weird because it is clear that Garmin sensors are able to provide RR-ints and from time to time, I have received these data even in BLE mode. When you subscribe to HR notifications, thereās no way to specify that you are expecting for whole data including HR + RR-int. Itās the sensor who decides what to send.
It seems that in case of communication with CIQ apps, Garmin HRM enter into this minimum data transmission mode when they detect some ātraffic jamā can occur and they open complete data transmission otherwise.
Considering this, I have managed to use BLE successfully for alphaHRV, disabling bluetooth on my phone just before starting alphaHRV (the HRM Pro plus is paired with the phone by GCM even if you are not using this app in foreground). In this way, the sensor activates full data transmission. Then you can enable again bluetooth in the phone.
In case that the phone is far away or you hadnāt added the HRM to GCM, BLE should work normally.
Please, confirm that this also works for any of you using Garmin HRM Pro Plus and even for new sensors like HRM200 and HRM600
1 Like
I use HRM600. With the HRM600, Garmin switched from broadcasting running dynamics from ANT+ to secure BLE. In fact, you can only get the advanced running dynamics, like Running Economy, by using secure BLE. This benefits Alpha HRV since I can use ANT+ for AlphaHRV.
1 Like
Stupid question, canāt you connect both AlphaHRV and the watch with Ant+? So you get running dynamics on the watch and RR in AlphaHRV which then write the values to the FIT file.
No, you canāt. AlphaHRV uses itās own connection protocol and the device doesnāt allow double connections. AlphaHRV is not using the existing connection but sets up a totally independent communication channel with the HR monitor.
The reason that AlphaHRV uses itās own protocol for connection is to avoid the flaws on the Garmin connection protocols.
Just use BLE for alphaHRV. I guess you are using Garmin HRM. Check my post below to know how to use BLE in this case.
Do you mean the watch or the HRM Pro Plus? Because the chest band can have an unlimited amount of connection using ant+. I just tried to start a run to test, the band was connected to the watch with ant+ and it was also connected to alphaHRV using ant+. My next run is Wednesday, Iāll test further.
Go to the ConnectIQ store and check the instructions in the data field description. You have to use different connection modes for the watch and for alphaHRV. ANT for both will never work for one of them
The watch.
Stop testing, just believe what weāre saying.
If the watch natively connects the strap with ANT+, you canāt have a second āindependent connectionā in ANT+. And thatās what AlphaHRV is doing. Itās setting up its own connection to the strap. Itās NOT re-using the native connection. AlphaHRV is an āappā running on your device, totally independent of your recording device. But the device is not allowing multiple connections to the same sensor. Unless one is using ANT+ and the other BLE. And thatās because, to the recording device, these look as a different sensor.
I have the same issue with the Tymewear HR strap. It connects to the watch either via alphaHRV or as an HR sensor.
On my Garmin watch, the Tymewear HR sensor only has an ANT+ option, and I donāt see a BLE/ANT+ choice.
Most likely Iām connecting something incorrectly. With the Core sensor everything is fine.
If you tested the Tymewear HRM in alphaHRV without any issues, could you recommend the correct pairing order for connecting the HR sensor to a Garmin watch while also broadcasting via alphaHRV at the same time?