@LitchiMonster said: Unfortunately the original was made in Finland and the replacement watch made in China. Oh well, it works now. So maybe this turns from unfortunately into fortunately

@sartoric No, no protector, suunto has the best saphire glass And always clean. Maybe it’s a hardware fault as @tieutieu and @isazi mentioned. Well, glad to know that it still working as before on some watches because the timing it changes on mine, sure looks like it was being deprecated. Thank you all for the clarification.

@Adrian.S Just guessing, that the room on the left is reserved for some other symbol. Like the storm warning or similar. Until we know the answer I would not call it poorly designed.

@isazi Thank you very much

@DieLa choose your exercise > exercise options > target > ascent

I think I’ve worked it out - it was a typo! Please try the latest build. It meant that terminal velocity was ignored when going downhill without a sensor - resulting in those high power readings. Let me know, as I cannot test this for a couple of weeks now.

@Mads-Hintz-Madsen yes, I am

@Dimitrios-Kanellopoulos thanks for your answer. But I’m not sure if I understand well. You are doing that before every run?

@Memascii Try to logout and login again. It is clearing more than just cache, and will redownload all from cloud and sync watch if any activities was not.

@alberto.munoz said: Does the current Open SuuntoPlus SDK allow communication with external BLE devices Yes, it does

@David-Palacios-Arroyo if you check the stages power meter in your connectivity menu, does it maybe provide also HR?

@Ale9924 the watch already alerts you if you move during a pause

It seems that this update has fixed the bug. The OHR sensor has remained active for 24 hours without switching off.

Same here. Since installing v. 2.53.42, I have a much shorter battery life than before, especially when the battery SoC is below 40%. You can then watch the battery deplete at about 1% per hour. Even with only sporadic usage in activities, I’m down to 4 days max. until I need to recharge. Before v. 2.53.42, I got more than a week of battery life easily. Looks like a bug in the firmware to me.

This night the watch got an update so there is a little hope. The problem occurred after an update end of 2025 perhaps it will be solved now. I will test it next week and when I am back from Holiday Manno02

@nmiguelrf just for curiosity, what is usecase for this feature? You do hikes/runs across multiple timezones?