Galaxy Watch only working if phone is connected via wifi or vpn

Hi all,

I use a HomaAssistance instance running on a vm in a synology ds920. Among other things, a Nuki lock and a ring interlock is used and connected via mqtt. I use my phone and aGalaxy Watch 4 Bluetooth version which is only connected to the phone via bluetooth.

Everything works as desired, except one issue. I can’t control the lock and ring entities from my watch if I’m not on the WiFi with my phone where the ds920 is also running. I get a toast on my watch saying “The entity has been selected” but nothing happens.

Strangely enough, on the phone I can control the entities without an issue even if its not connected to wifi. If im connected to my wifi then also the watch works.
My current workaround is that my phone is always conneced to my local network via VPN, because in this case also everything works.

Unfortunately, I have no idea what might be the issue or whether it might be a bug.
Does anyone here have an idea why this is or how I could debug it?

Im running everything on the latest update. Just updated today, but the Issue persists.

Wear OS will proxy data through the phones connection. Some user networks dont work well with that. Some users have reported enablign NAT loopback helps. Not much the app can do here.

1 Like