@Brad_Olwin As I said in my original post this wasn’t the issue. This issue fixed itself and I am now able to see zonesense data on the watch and in the app, and I am not sure but believe one of the 2 following things fixed it: HRM 200 version updated to 5.40 Looking at the HRM 200 manual (Manual) I realized the device have 2 connection types: secure and open. Secure is when the device blinks green twice and open when it blinks green three times. I am not sure what was the connection type when I originally tried to make it work, but when trying again after opening this thread I made sure to use the open connection state. My hypothesis is that one of the two fixed my issue. Leaving this for future reference and future google searches, as when I searched this I didn’t find anything related.

Nice to see that now, since everything is aligned for more than 4 weeks, the differences in CTL/ATL/TSB between TP and Suunto are descreasing. And also the TSB finally is more often less than 0 en sometimes less then -10, meaning i am productive… :-)… I am getting more used to this TP appraoch with TSS. I train frequently which is also important. I posted this question few months ago. For me it was a learning curve. I am happy with my Suunto. I like the interface of the Suunto app (more than the Garmin Connect app) and maybe in the future there will also be a webapp with routeplanner included (private project currently). This topic can be closed.

Reported the issue

I also noticed that the temperature bar values aren’t updated until you unlock the watch

It seems that this problem has been resolved, at least with Race2. I don’t know if it was Suunto or Strava, but as of this season, the number of runs is showing correctly.