I have been using the WearOS companion app on a Galaxy Watch 4 for a while now. I recently upgraded to the Galaxy Watch 5. I went to set up HA on the new watch and to my surprise it kept telling me it couldn’t load any entities. I opened the “Companion App → Wear OS Settings” settings on my Android phone, and it loads endlessly with the title “Manage device Galaxy Watch 4”.
I have tried to disable the device, delete enties associated with the Watch 4, but with no luck. I also tried clearing the cache and data for the Android app, as well as deleting and reinstalling both the Android app and the WearOS app. I have tried manually logging in on the watch, as well as using the “sign in on phone” feature. While the new Galaxy Watch 5 will appear as a device in HA, it doesnt seem to receive any entity data, and i can’t change any settings on the watch after registering it with HA.
A couple more install attempts on the watch, and deleting the old Watch 4 device from the “Mobile App” integration, I was able to get the watch to work for about 6 hours, but then it lost connection and couldn’t seem to load again. All the while, even when it was working, and listed in the “Mobile App” integration as “Galaxy Watch 5”, the WearOS settings on my phone still listed it by the old watch’s name (Galaxy Watch 4 (6FSM)).
Given how clearing cache and data, and reinstalling the app hasn’t gotten rid of the reference to the old Galaxy Watch 4, it must be grabbing that info from HA, right? I can’t seem to find the place to clear this data so I can properly pair the new Watch 5.
So, what ended up working for me was removing the Galaxy Watch 4 from my Galaxy Wearable (or “Wear”) app. It was inactive, but still listed as a device in that app. The minute I removed it from Wear, it no longer was listed in my HA companion app and everything started working fine on the Galaxy Watch 5.
This solution surprises me, as I wouldn’t have expected any communication between the HA companion app and the Galaxy Wear app (or some background data sink). As such, take this solution with a grain of salt.
It’s not surprising considering how much Samsung likes to deviate from standard Android developer documentation. The app relies on data provided by the API and if they do something non-standard the app will reflect that.
Seems like this is still an issue. I’ve had two watches in my Galaxy Wear app and wasn’t able to pair my new Watch5 Pro with the app. It always returned to the instance selection screen. It only worked after I removed the old GearFit2 from Galaxy Wear. I’d consider this a bug.
I am still having this problem when keeping my Galaxy Watch4 while adding a new Watch7.
Is this an issue in Home Assistant app? (maybe it only looks for first Wear OS device and doesn’t support selecting from a list) or is this caused by an issue in how the Galaxy Wear App reports available devices?
I don’t want to delete my Watch4 because I still use it whenever my watch might get damaged (working in hazardous enviroments).