Constant connectivity problem

Correct, sdboverbt gave me an error when I tried to establish a BT connection, I understand it won’t work with Active2’s current FW.
So I went and setup GWS to an older Windows 10 laptop I got and ran into the exact same issue: GWS was not able to find my Active2 although they are both in the same WiFi network, debugging is on and pinging the Active2 works fine.
I tried to find what causes the connection problem but made no significant progress… after a lot of reboots, restarts and retries I gave up.
Well, almost… tried one more time and after rebooting the Active2, for whatever reason decided to check connections in the settings, WiFi was on but for some reason not connected. Something strange happened then - I had to enter the WiFi password again since the field was blank.
All of a sudden the Active2 was found in GWS, the pop up was visible and acknowledged and the Active2 listed as device. Wow! Unfortunately, when I tried the “run on device” command, GWS hung up after a while.
The funniest thing about this is that the Active2 has now even been recognized in my Windows 11 environment, but there still seems to be a problem. A few hours ago, when I tried again, it gives me that “no compatible device” error again .
EDIT: Tried again a couple of minutes ago and now selecting “run on device” and pressing the + button plus entering the IP in the box worked (which didn’t do the trick before). Hope it’s now working for me.

Thank you very much for your help and advice! Very much appreciated!

Hi Muecker,

I never had the issue but one of our team had to wait a couple minutes after the watch said it was connected for the sdb to connect for running on the watch.

I believe if it updates to Windows 11 you still need to create a new Distributor Certificate just like a new computer.

Ron
Samsung Developer Relations

Hi Ron,
exactly! After establishing the connection to GWS on the Windows 11 laptop, I had to apply for a new Distributor Certificate.