Just registered to let you know that I believe this is an issue with how SDS (the server interfacing w/ the IDE extension and the watch’s protocols ?) is spawned by the Suuntoplus Editor.
I’m facing the exact same issue, only on a macbook w/ an M4 Pro chip instead of an M3 Max one.
Running the following command starts SDS, which after a few seconds picks up the watch and starts the pairing process.
SDS_MACOS_BLE_SCAN=1 ~/.vscode/extensions/suunto.suuntoplus-editor-1.42.0/node_modules/@suunto-internal/sds-as/macos/SDSApplicationServer.bin 9801
As a workaround, I tweaked my local version of Suuntoplus Editor to prevent it from starting SDS (via a coding agent, which worked surprisingly well from the first try), and I’m starting it manually in a terminal.
The relevant file is
~/.vscode/extensions/suunto.suuntoplus-editor-1.42.0/node_modules/@suunto-internal/sds-as/dist/sds.js
The watch is then displayed in VSC, and could be loaded with my app without any issue.
[image: 1774720045117-0695f3ac-b672-40ca-87a4-3b948013860b-image.png]
I hope that this info will let you debug and patch the Suuntoplus Editor
As a side note, I was quite happy to see this editor being available free of charge and without any signup process
