Hi, what we meant is wfs is listening on a different port.
E.g adb server is port 5503
But wfs set up maybe 5037.
Your watch when making connection might sent ack or talk back to only port 5503
That why your adb commands works, but wfs does not
Just my guess may not be correct.
Anyway i dont think its wfs per say, could be multiple things at play, as its works for me
I connected my pc → ethernet, watch → wireless
And i do see my watch on the wfs.
Also another guy with same setup managed to make it work after he realised he missed a step.
Only difference in all three cases we are using different watches. Gw6 , gw 5 pro(my) , gw4
But wear os is wear os 4
Note i not saying u missed a step. But showing a example that works. With ethernet using wfs.
Also there can be a case where one application can connect to sometime, but another trying to do the same cant. Its called application firewall.
Example i can have chrome visit www.yyy.com
But edge cannot. Why? Edge got problem? No.
Something is blocking traffic. Untill i unblocked the traffic then my edge can visit www.yyy.com
Just saying
Anyway try uninstalling and reinstalling wfs. Might help.