Closed DustyArmstrong closed 9 months ago
The watch is able to connect and interface with HA externally (e.g. 4G), but not from my internal network.
can you enable NAT loopback on your router? this would be the easiest fix.
unfortunately there is not much the app can do here. Wear OS will proxy data from the phone to the watch when using Bluetooth. The watch app will only work with the external URL so anything that needs to be changed needs to be done on your network to get it to work. There is no URL switching with the Wear OS app due to the way Wear OS works.
Yeah I can enable it, I suppose that would technically solve it and just remove my DNS rewrite.
Out of interest, is this then an issue with the watch itself or is it the manner in which the app works? I.e. is this a conscious development decision to have the app proxy data this way or is it just a fundamental aspect of WearOS that can't be avoided?
is this a conscious development decision to have the app proxy data this way or is it just a fundamental aspect of WearOS that can't be avoided?
The latter: that's how networking works on Wear OS
The latter: that's how networking works on Wear OS
Yeah I thought so, I suppose it isn't surprising given WearOS is Google. Hopefully someday we find a way round their restrictions.
Thanks, I'll close this off.
Home Assistant Android app version(s): 2023.12.4 Android version(s): 2023.12.4-full Device model(s): Samsung S22 Galaxy Watch Active 6 Home Assistant version: 2024.1.5 Last working Home Assistant release (if known): N/A Description of problem, include YAML if issue is related to notifications: Just got a device with WearOS, but I'm having issues.
The watch is able to connect and interface with HA externally (e.g. 4G), but not from my internal network. I expect this is due to my setup but have seen others with a similar issue. I am mostly posting this as a bug report in the hopes it might assist development.
My setup is as follows (these are physical networks):
LAN network (HA HERE) -> Pfsense firewall -> WiFi network (watch here)
I use Adguard for DNS internally, whereby I do a DNS rewrite on requests to my HA address to direct my wireless devices to my HA's local IP over on the LAN. This works flawlessy on my phone and other wireless devices, I've had no issues at all there, but the watch doesn't like it. My HA uses a Let's Encrypt certificate for both the internal and external. The Companion App seamlessly transitions between the internal and external IP/DNS, it's great, so was hoping the watch would just connect to the app via bluetooth but I suppose it directly talks to HA? Probably DNS related (it's always DNS)?
Any advice would be greatly appreciated, otherwise yeah just take this as a "I have this problem too". I fully understand my setup is maybe a bit weird having multiple internal networks (LAN/WiFi/IoT), but I just like it that way.
Companion App Logs: I don't know if these will help.
Screenshot or video of problem:
Additional information: