@Stavrogin Personally I find this to be one of the big issues with Suunto, a watch that I am otherwise quite happy with. My understanding is that ”guides” are developed by partners from templates provided by Suunto. So if you want a change to the guide you have to talk to TP. Further the interval structure is embedded in the guide and downloaded as a package to the watch, but this structure is not available to other apps or data screens. Suunto has an API for upload of guides and FIT files, you can find documentation online. But this API is only open to partners like TP. Technically I think there are a number of things that should be done… Decouple the training structure from the guides Make the structure available through the Suunto os to othet apps and data screens Allow upload of FIT workout files directly via the Suunto app Wether Suunto will ever do this is probably more of a business decision.

I have a Polar H9 (beside the strap is the same as a H10, just cheaper) which consumed batteries like creasy, but with the latest firmware update is fixed. I also have a Polar OH1+, which is an optical sensor you wear on your upper arm (or attach it to your swimming goggles). It’s an older model, but the sensor is the same as the new verity sense, just cheaper (although the verity sense has some extra functions, you might or might not need). Overall, optical sensors on watches never worked for me, but the OH1+ works pretty good. It is rechargeable, which I think is a advantage. Most of the time I find it slightly more comfortable than a chest strap, although, since your arm moves while running, there might be some need for readjusting the position

@Calando said: @LapaS Correct, for a guarantee-replaced device you get no new guarantee (just the remaining time - 1y guarantee, if you get a replacement after 8 months, the replacement will have 4 months of guarantee). Try another HR strap - two of my colleagues are using the Polar H10 and never faced any problems (they have Polar and Garmin watches). My H10 also still works perfectly with my Race 2 (see above). Another advantage of the H10 - replacement straps are more than 30% cheaper than the Suunto ones. In the meantime, I am unfortunately pretty much convinced that @sindavide was correct in his post above. I asked Suunto about warranty and since my original sensor was bought under a year ago they said warranty should cover the replacement device. So the device is now going to Suunto repair. Anyway my wife had a Polar H10 sensor lying around that had not been used for a while. I bought a new strap for that. At first the sensor was not connecting to anything (phone, watch) but then I saw a discussion on H10 issues where someone suggested putting a small piece of cardboard under the battery (clearly the battery was not touching the connectors). After this connection worked perfectly. Also tested one workout with H10 & Suunto Vertical. Connection worked perfectly throughout the whole session. It would still be good to have also the Suunto sensor working since I need that for workouts where I can’t use a watch.

hopefully this will be a reality soon… but not yet [image: 1782467674537-739efdbe-8b08-4504-8717-38476581da9c-image.jpeg] [image: 1782467689878-f349fa4a-a8c2-4b65-9a5f-60e3cc137046-image.jpeg]

@duffman19 as someone who works with motors all the time, this is kinda difficult to stay away from magnets.

@off242 doesn’t seem to go away anytime soon. I keep forgetting to disable notifications during cycling and it’s a struggle…

The problem is still viral Silence from the support This still fucks me up

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.