#Pixel watch dns issues

1 messages · Page 1 of 1 (latest)

flint tangle
#

Hi,
This might not the right place as the issue is more related to the os but I thought I would try as other might have experienced similar things.

I recently bought a pixel watch 3 and now I have some issues connecting to the hass server.
For some reason I cannot connect when I have Bluetooth active but have to rely on WiFi or LTE.
I checked the logs and they point to that the domain name can't be resolved.
If I disable Bluetooth, it works but when I turn it back on the connection drops again.

Any idea why this might be? It seems that the Bluetooth connection seems to be preferred but for some reason that seems to use another dns server than the phone uses (that is also connected to the same WiFi).

split tinsel
#

hello unfortunately thats a known issue for some user setups

#

there is some history in that, most users found enabling NAT loopback on their router fixes the issue

#

wear OS will proxy over its data via bluetooth and the app has no control over that, for the app it expects to work on all network connections