Velo-Volts: Platform for monitoring sensor battery status and alerting

External Projects
21

Analyzing you fit files, i see you have a Stryd NextGen or 5 model but you didn’t activate RD Pod feature. So no battery status.

Battery Status mod Activity Field:

imagem

Pls activate that feature.
In your Garmin watch Settings Sensors:

imagem
imagem646×164 4.18 KB

Added bonus:
Your jittering cadence (as well as the other running dynamics) charts at present coming from the wrist watch sensor:

imagem
imagem1133×122 13.3 KB

will turn in something like this, coming from the Stryd foot pod:
imagem
imagem1165×116 11 KB

22

I have done two very brief tests of what devices show up. Tymewear breathing sensor shows in both FITs though not in the Battery Staus Mod

The first had the Stryd & just the Tymewear breathing sensor active.

The second has the Stryd, Tymewear breathing sensor & Tymewear (shows as Cardiosport) HRM

23

Hopefully I have done this. i will test tomorrow. Thanks

1 Like
24

Heya David!

Did you mange to get it working? Would love to see the examples to ensure we support your use case well!

1 Like
25

Apologies I thought that I had posted but obviously not. Yes it is working fine with the Dropbox sync to Intervals.

Capture.PNG
Capture.PNG1715×886 158 KB

Capture3.PNG
Capture3.PNG1698×884 160 KB

Capture2.PNG
Capture2.PNG1419×883 106 KB

26

@Velo_Volts I am no longer able to login and reset password. there is any issue there?
Thank you

27

Looks really good and helpful. Just wondering what happens to the „rest“ of my data from my fit file? I would like to understand and know where I send my data to and how it is used. I am obviously more than happy to hand out battery status data and have that stored wherever, but I try to avoid just sending all data without knowing what happens to it or what it is used for.

28

Apologies for not observing your feedback on the forum here @Wilson75!

I’ve just verified that the reset password function does not have any issues when i try it out. If any problems persist do let me know!

29

I can login now.

30

It is entirely understandable that everyone would be worried about the data retention. That is why there is a well described and documented privacy policy as listed on the site!

Sadly it is not really possible to “opt out” of more sensitive data from services when fetching fit files, from various cycling computers. So while there is in no way any processing or sharing of data to any third party as per the privacy policy, the raw fit files is still subject to retention for some time, in a bid to learn more about the more proprietary and hidden fields used by vendors, and to be able to reverse engineer and support these, to provide an overall better service!

31

Thanks for your answer

32

@Velo_Volts
I get some strange results: battery level reported low (20%), general summary page shows that . Once in the device itself battery level is displayed as 95%. The history secion shows readings from within seconds of eachother wirh both those results…

Is this a bug or do i miss something?

Screenshot_20260424_101320_Brave
Screenshot_20260424_101320_Brave1080×2340 166 KB

Screenshot_20260424_101311_Brave
Screenshot_20260424_101311_Brave1080×2340 201 KB

Screenshot_20260424_101520_Brave
Screenshot_20260424_101520_Brave1080×2340 92.9 KB

33

@Alpaka That looked very wrong indeed!

We have tried to iterate on the sub-component parsing we added recently and it should be much better for your scenario going forward.

We really appreciate the feedback here. Let us know if everything looks better in your end and if it works like you would expect it to?

34

Hello,

  1. Are there specific sensors you use that aren’t showing up?

My Bryton Gardia is not showing up in the device list

BR

Sasch

35

Hi Sascha,

Thanks for reaching out! I checked your uploaded FIT files directly and found the root cause: your Hammerhead Karoo does not write radar device data into FIT files. Velo-Volt reads battery info from device_info records inside each FIT. After all, your Karoo, Favero, SRAM eTap, and HRMs all appear correctly, but the Gardia never shows up because the Karoo simply never records it.

This is a limitation in Karoo’s FIT export, not something we can work around on our end.

What you can consider doing depending on how you have set up the radar:

  1. File a feature request with Hammerhead: Opening an issue there asking them to include radar/tail-light sensors (ANT+ type bike_radar) in FIT device_info exports is the most direct path. Garmin already does this for Varia on Edge devices, so there’s precedent along side a number of other vendors.
  2. Check the kxradar project: There’s an open-source Karoo radar extension at GitHub - itxsvv/kxradar: Radar Enhancement for Hammerhead Karoo · GitHub . The maintainers there have the deepest knowledge of how Karoo talks to radar devices and may be able to shed more light — or even add FIT device_info writing as a feature.

Once Hammerhead exports radar device info in FIT files, your Gardia will appear in Velo-Volt automatically, no changes needed on our side hopefully.

Sorry we can’t do more right now, the fix needs to come from Hammerhead or the kxradar community!

36

Hi @Velo_Volts I am experiencing login problems via Garmin. Message „Failed to start Garmin login".