I was having the same issue. Hopefully, this should help.
According to the WiFi help on my Galaxy 5 Pro, WiFi is disabled when Bluetooth is connected.
Once I disabled Bluetooth, I was able to connect to Home Assistant from my watch.
Once I was connected, I re-enabled Bluetooth, and I was still able to connect.
EDIT: (15 minutes later) I was wrong. Re-enabling Bluetooth breaks the connection. If I need to control anything, I need to disable Bluetooth.
I looked further at my help and see that the watch will start using WiFi when needed. I am guessing there is a bug where the watch isn’t trying to use WiFi - or at least not fast enough.
I think that problem is with DNS servers over Bluetooth connection. If watch connects using Wi-Fi then it works, if it’s connected via Bluetooth and phone is on local network (local DNS forwarding to local IP /https-certificate workaround) then it’s not working. And if I disconnect phone from Wi-Fi and watch is connected to phone via Bluetooth then it’s again working. So it’s only not working when watch is connected to phone using Bluetooth and phone is on local network and using local DNS that forwards to local IP. That got me to suspect on watch is not using correct DNS.
I had this issue but in my case I had configured my reverse proxy to only allow TLS 1.3, but Wear OS 2 does not seem to support TLS 1.3 yet, after relaxing the restriction to TLS 1.2 it works as expected.
I only enabled to tighten 1.2 some what TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305, TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
Yep, works for me on Galaxy Watch 5 Pro, with and without WIFI. It finds my setup, can connect then it directs me to continue on phone where I can assign my favorites.
I’m using SSL secured with letsencrypt cert, with port forwarding for port 443 to the hass box on my router.
Basically the same issue here. Tried enabling Wi-Fi and still got the same issue, but didn’t disable bluetooth on the watch.
On the Wear device settings page there is an old “Manage device Galaxy Watch5 (…)”, tapping it does nothing.
I try initiating a login, either via “Login Wear OS device” on the phone or opening the watch app and tapping my homeassistant.local instance and continuing on phone. After entering the device name I get a “Could not register watch” toast and end up back on the Wear device settings screen. And the “Manage device …” is the same as before, not the new device name I entered.
I have a HA instance that is only accessible from the local network, running SSL under a domain hassio.mydomain.com that is resolved by the DNS present in the network (but not in the public Internet). I could not get the Wear OS app to connect to the instance unless I forced WiFi on the watch - with Bluetooth on it connected without an issue. The moment it got routed via the BT connection - no luck.
I’ve decided to run a small experiment - I’ve added an A record in the public DNS to resolve hassio.mydomain.com to my local IP address e.g. 192.168.1.10 (you don’t need to tell me that this is an anti-pattern) and to my surprise it worked. This means that when the watch tries to access the network over the BT link, it ignores the DNS settings of the network the phone is connected to and uses something hard-coded. Which is a privacy-invading anti-pattern, but there is little we can do about this.
Just as @ng175 mentioned, if your device has any setting related to “Private DNS” disable it - it will prevent your network’s DNS setup from working.
Which device? (Sounds like a weird question)
Phone, Watch, HA app on phone, HA app on watch, HA itself, Pihole, DNS on router. I did try looking but cant seem to find it, and dont know which device to do a deep dive…
