... so I did these steps in addition to rebooting my machine, watch, phone as well as pulling the juice on my router ... (I posted in this posting around page 2 or page 3).
it worked on my iPhone X (14.0.1) and watch S3 (7.0.1) and Catalina 10.5.7. HEAY!!
worked fine for several weeks. HEAY!!
I then updated my watch to from S3 to S6 (7.0.1) ... unpaired my S3 (sold it for $180 ... not bad), re-paired my S6. My Catalina had UNLOCK boxes for both my S3 and S6. I tried cleaning up my S3 ear-marks within Catalina (followed the steps).
I couldn't get arid of the S3 checkmark box on Catalina. irritating but not a show stopped.
then suddenly, one morning, it was gone as well as I'm not able to select the general CHECK box. kept receiving "UNABLE TO COMMUNICATE ..."
hum ... so ... I'll just reconfigure my S6 for unlock right?
nope ... I followed these steps ALL DAY ... I couldn't get Catalina to COMMUNICATE with the watch ... I tried everything probably 20-25 times. reboots ... everything ...
finally I gave up and went to bed.
woke up the next morning.
first attempt failed ... 2nd attempt worked.
WHAT'S GOING ON APPLE?
is this a back-end services with back-end data that's getting hosed?
I reviewed the console LOG and saw some errors concerning failed attempts to communicate. But I did nothing this morning to address the UNLOCK feature. I DID NOTHING TO FIX THIS ... IT JUST FIXED ITSELF????
I'm in IT ... this is non-sensical
FYI: I seen console logs of my OLD WATCH NAME ... not sure why they are *glued* to Catalina