It shouldn’t be necessary if you have WiFi always on but try turning off Bluetooth.
Reset the watch by holding the power button off and open device manager it should show there. If it doesn’t there is a setting on your watch. If it shows but won’t connect there is an issue with your computer maybe a firewall.
Ron
Hello, I am getting the same issue and had frustratingly trying all of these steps to get my watch to connect to my PC through wifi. the excruciating sequential Bluetooth, wifi, debug, and developer modes, keeping away from other blue tooth signals, lowering my firewalls, restarting, and reboot.
Well, now that I’ve said my piece on this, Any other updates on this matter?
Actually, now I am stuck on device unauthorized. Please check the confirmation dialog on your device.
How I did this was connect PC and watch to mobile hotspot on my phone, connected the wifis, ensured bluetooth off, debug mode on, and developer mode on, then immediately reboot, and immediately after reboot and confirming wifi connection re-establishment, I slammed sdb connect “my port” and now I got to this golden state.
What would be next steps for authorizing? I am not getting a notification on my watch or phone
Using a Tizen Distributor or Author certificate or having one in the profile along with Samsung Certificates will give you the unauthorized Device error.
Did you install the Samsung Certificate extension? If not you need to do that and enable the extension. Do that in the Package manager extensions.
Then create a new profile and use the Samsung Author Certificate and "Samsung Tizen Distributor Certificate. If you still have issues read all the listed sections on this page.
I hope this helps if not
Came here for the same problem, but what worked for me at the end is running device manager as admin…
Thanks, I’ll remember this for others. I imagine if the original install was Admin you will need to do this.
Ron
Samsung Developer Program
Important Note!
If you set developer mode’s IP Address in RTL (Right To Left) device language (Arabic, Hebrew, etc.) it saves the IP address backwards from end to beginning (1.0.0.10 instead of 10.0.0.1).
What you should do is:
I had the same problem and the solution was going into setting in package manager, open de SDK extension tab and activate the samsung wearables and certificates directories. then I went back to package manager to download them.
Hope that works for you.
I connected my device (Samsung Wath 3) in Remote Device Manager and via sdb, but after pressing the close button on Remote Device Manager the Tizen Device Manager did not show my device in the list of connected devices, so I have no way to get watch DUID. The Bluetooth and remote connection feature on the watch is off, developer mode enabled, Debug over Wifi also enabled and the PC was already authorized by the watch. Device Manager is run by the Administrator. I’m stuck… 
Any idea what to do next?
It is probably you did not accept the RSA Encryption key. If you don’t do that in a timely manner it doesn’t ask again. Try holding down the Power button for about 15 seconds until it says rebooting Also restart your computer. After it restarts make sure Developer Mode is on WiFi is on and your computer is connected via WiFi not an ethernet cable (although sometimes that works too).
I’ve had this problem before myself Once I failed to turn on Debugging or accepting the RSA key issue I kept trying and finally go it.
Ron
Samsung Developer Relations
Thank’s for your response!
Unfortunately, I’m sure that I allowed Debugging without problem, I can freely access my watch through the sdb, but for some reason, the device is still not displayed in the list in Device Manager.
I have my defender turned off while trying.
I already rebooted pc and watch several times and tried ordinary Wifi and mobile Hotspot.
I also tried ./sdb forward tcp:26102 tcp:5555 but it doesn’t seem to work.
I think Device Manager is aware of my device after turning on the connection to it in Remote Device Manager but for some reason cannot connect or display it.
I found the following lines in Device Manager logs, showing the name of my device “SM-R860” ( when I connected my device with IP and port I inserted another name - “_SM-R860”):
[2022.4.13 16:20:40.663][INFO][Main.initializeLogger] Start Device Manager!!
[2022.4.13 16:20:40.677][INFO][Main.obtainLockFile] The First Device Manager Running
[2022.4.13 16:20:44.263][SEVERE][DeviceChangedListener.onConnected] Failed to sdb connection by SdbCommandRejectedException: org.tizen.sdblib.exception.SdbCommandRejectedException: closed
[2022.4.13 16:20:44.265][FINE][FXMLLogViewController$5$1.run] Create Device Info: SM-R860
[2022.4.13 16:20:44.376][FINE][FXMLDeviceTableViewController$5$1.run] Create Device Info: SM-R860
When pressing the scanning button I can see the logs pointing that the connection refused:
[2022.4.13 16:24:42.578][INFO][RemoteDeviceScanWorkerController.findReachableIP] Failed to connect: 192.168.2.233
java.net.ConnectException: Connection refused: connect
java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
java.net.Socket.connect(Socket.java:607)
Is there anything else I can do to connect my device?
device-manager Try add by ip.log (1.4 KB)
device-manager Try scan logs.log (651.9 KB)
device-managerOpenDeviceManagerWhileWathConnectedbysdb.log (543 Bytes)
You need to have Developer Options enabled on the Watch as well, you probably do but make sure.
You have to accept an RSA encryption key to transfer the encoded data. If you didn’t do that it is refused and that seems to be the error you are getting.
Observe your watch and when you try to connect an RSA Acceptance screen will show you need to allow this. If you don’t then it believes that it is a security breech and may not ask again unless you reboot your watch (hold down power button until it says rebooting). After you accept it once it doesn’t pop up again for that computer connection (unless it is updated).
If you never see the RSA Encryption acceptance you probably denied it at some time by accident. do this>
In the C:\users\USERNAME\ is a hidden folder .tizen in it are two files sdbkey and sdbkey.pub rename them and relaunch Tizen Studio and Device manager. And try to connect again.
Ron
Samsung Developer Relations
I changed my laptop and i had this error when i tried to connect my TV with my new laptop.
I did the following and it worked
It is better to just generate a new Distributor Certificate. This is only needed to load the app on a watch, it is not used any other time. With Tizen Studio you can create a list of the device IP’s you don’t need to change or remove the old one.
Ron
Samsung Developer Relations
Did you ever figure out what the issue was with getting your device to show up in the Device Manager list? I have the exact same issue, can connect with sdb, but not through Device Manager. I cannot get the DUID, which think is what is preventing me from installing applications on the watch through sdb, since my certificate does not have a DUID listed. Thank you-
There is probably a command line command to get the DUID and you can enter it manually but I don’t know it and don’t know where to get that information any more.
If you are connected you should be able to just generate the Author and Distributor certificates. Be sure to generate Samsung certificates and not Tizen certificates as they will not be able to install on Samsung Watches if you do.
There was an old trick where Tizen Developer would use Galaxy Watch Studio to connect to the watch and get the DUID
If you do try that you can download it here I recommend you download the previous 2.0 release if you ever plan to use GWS. The newer version has several flaws.
Hope something helps, If not let us know
Ron
Samsung Developer Relations
Hello Ron,
Thank you for your response! The Galaxy Watch Studio option did not work for me, versions before 2.0 do not run on my machine (imac, OS: Ventura). They also did not run on the previous OS as well. Also, I’m not sure that going to Watch Studio will solve my problem.
My main problem is getting a connection between my Galaxy 5 watch and the Tizen Studio Device Manager program via the Tizen Stuido GUI - the Device Manager program will just not see my watch, while I am able to connect and verify a connection via command line sdb. When using sdb, I can verify that my device is connected with “sdb devices”, but I cannot push my .tpk package to my watch via “sdb install file.tpk” because I end up with a write error:
./sdb install /Users/####/workspace/test/Debug/org.example.test_v2-1.0.0-arm.tpk
WARNING: Your data are to be sent over an unencrypted connection and could be read by others.
pushed org.example.test_v2-1.0.0-arm.tpk 0% 0KB 0KB/pushed org.example.test_v2-1.0.0-arm.tpk 77% 4544KB 4469KB/pushed org.example.test_v2-1.0.0-arm.tpk 100% 5828KB 4469KB/s
error: failed to close ‘/system/bin/sh: /usr/bin/pkgcmd: inaccessible or not found/tmp/org.example.test_v2-1.0.0-arm.tpk’: secure_mkdirs failed: Read-only file system
Looks like a write permissions error. This is why I called out the lack of a DUID in my certificate.
Any ideas?
Oh on a Mac you have to use the Tizen Studio sdb app as the one that ships with the last 3 Galaxy Watch Studio don’t work on Mac. but that isn’t the issue.
My main problem is getting a connection between my Galaxy 5 watch and the Tizen Studio Device
This is slap your forehead time. 
Galaxy Watch 5 is Wear OS operating system Not Tizen OS. You have to use ADB to connect and Android Studio to build your Wear OS App.
Ron
Very helpful advice Ron, I moved over to Android Studio and connected with my watch immediately. I read a post somewhere when I started to develop my app that suggested TizenStudio, that was bad advice.
Now I’m in a situation where I cannot access my PPG sensor (PPGBatch Sensor, Type: 69668). Do you know if I need the “Privileged SDK” for that? I hope not, because it sounds like they are not giving it out for many people. Thanks again!
That is because you don’t need it. With Wear OS you use Wear OS Health Services and Health connect which is the hub.
There are some blog tutorials created in 2022 that should help you get started.
For Wear Health Services see the Android Documentation
Here are some links to help you
Health Connect
Health Services
Health Platform API
Hope that helps you get started. I don’t know which sensors are in the newer Galaxy Watches but I’m pretty sure they have PPG sensors no matter if they are Samsung or Google Pixel of Fit watches
Ron
Samsung Developer Relations