@Pierre-Matelski If you want the battery to last as long as possible during everyday use (outside of workouts), make these adjustments in the Settings menu: Display > Always-on: Turn this option off. Let the screen wake only when you look at the watch. Display > Brightness: Set it to Auto or reduce it to Low. Connectivity > Media Controls: Turn this off if you don’t usually control music playing on your iPhone from the watch, as it keeps Bluetooth active and uses more battery. Backlight with Button Press: Turn this feature on so the backlight only comes on when you press a button, preventing the display from lighting up by itself at night while you’re in bed.

@SergioB Good morning. Yes, everything is 100% configured, but the location won’t change cities.

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

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]

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

Here is the photo of the other watch I found on eBay. [image: 1782430445459-5681d8dd-d3d3-4f45-9151-e77c3eec8da0-image.jpeg]

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.

@Alex-Glebov +1

@2b2bff said: Offline 2b2bff SILVER MEMBERS about 17 hours ago @Woodster said: Let me know how I can send over diagnostics It is explained in the opening post of the thread? Race S Yes it’s in there ta buddy - sent Suunto account details via chat. For me the freezing issue is very likely a faulty garbage-collection issue with a SuuntoPlus app I wrote leading to RAM pressure, can easily reproduce and send logs over so that a firmware update can isolate any app issues from the actual watch.

@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!

@Robbin053 The hardware is different so if it wasn’t in the list …

Another crazy drain whilst leaving the watch with hr off in the drawer . 40% drop in 2 days . I sent the logs right now in case anyone finds anything interesting

@domucki 1- no need to start an actitivy, but you have to be on the start screen, I’m doing dual recording with my watch and HH just because I want those Suunto badges

@Francesco-Pagano I’ve tried it today on a run with a steep climb and a long descent (too steep for me to run in any case). I may be wrong but my understanding was that ideally you should try to stay in the ‘Hold’ zone regardless of steepness - ie a steady sustainable level of effort. If it goes to ‘Push’ then I think you have let the level of effort drift down (and vice versa - ‘Ease’ probably means you are pushing too hard to sustain for long). I found I could usually stay in the ‘Hold’ position whether running on the less steep sections or walking hard on the unrunnable portions. On the long descent I found by pushing hard I could just about stay there - easing off quickly dropped to ‘Push’ I felt like I’d had a strong run and it encouraged me to keep trying and not drift off admiring the scenery. I suspect this is aimed at race pace sessions up to perhaps middle distance? I don’t think it’s intended for Z2 long runs for example. One thing I don’t understand is the score in the app afterwards - is this the % of the session spent in ‘Hold’?