@Stavrogin at least with TrainAsOne I get targets for each step directly on the watch. [image: 1782416387266-img_6927.jpeg] But I cannot look at the planned workout steps before starting the workout if this is what you meant…

@Squirrel Thanks a lot for the clarification! That actually makes much more sense now. I’ll record my CTL, ATL, and TSB values for the next 2–3 days and compare them to see if the numbers match yesterday’s CTL − ATL. Thanks again!

@vinc14 I’m also curious to learn more about suggestions. I have a H10. Garbage, replaced the belt, still garbage. Bought a new H10, even more garbage. Maybe is a me thing. Maybe is my hairy chest (as mentioned in the support page). Maybe is static (as mentioned in the support page, my clothes usually feel full of static). At least 90% of my runs have bad readings (can be low as 50bpm up to 220 bpm) Looking around about the Garmin HRM devices but maybe is time to realise that the proper and best solution is the Coros Armband. Wondering if the Garmin HRM wouldn’t have the same issues as the H10, in case is a “me thing”.

reading because i’m thinking about getting Polar H10

Zirkeltraining have no gps recording?

Hi Michele, First of all, thank you very much for publishing your Bosch Smart System project. It has been extremely helpful while researching the Bosch ecosystem. I’m currently analysing Bosch Smart System support in several open-source projects (OpenTracks, Home Assistant, BikeBridge, etc.) to better understand which data is officially available through Bosch’s Live Data Interface (LDI) and which parts still rely on the older proprietary protocol. After studying the available documentation and source code, only a few questions remain that I hope you might be able to answer from your own experience. Official LDI vs. proprietary Bosch protocol Does your current implementation rely exclusively on the official Bosch LDI, or do you still need any data from the older reverse-engineered Bosch BLE protocol? Motor Power and Assist Mode Are these values available through the official LDI, or are they only obtainable through Bosch’s proprietary protocol? Protocol maturity If someone were starting a new open-source project today, would you recommend building directly on the official LDI, or are there still important reasons to support the older Bosch protocol? Firmware compatibility Have you observed any significant differences in LDI behaviour between different Smart System bikes (for example Bosch SX vs. Performance Line CX), or has the protocol been consistent in your experience? Field reliability Are there any officially documented LDI fields that, in practice, are not consistently transmitted by all bikes or firmware versions? I’m trying to distinguish between what is officially supported, what is universally available in practice, and what still depends on reverse engineering. Thank you again for sharing your work and for any insights you can provide.

@Marcelo-Mönch have you given Suunto App the permission to access the geolocation on your mobile?