Closed AnnoyingTechnology closed 1 month ago
interesting your server returned a 404 error when attempting to register the device. Have you setup the Wear OS app before? Anything you can tell us about your networking setup?
404 errors are not ones the app can solve but usually indicate something on the server side.
09-04 19:38:07.330 5182 5182 D SettingsWearViewModel: Successfully sent auth to wear
So the phone was able to authenticate however it seems it got rejected by the watch.
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: Watch was unable to register: retrofit2.HttpException: HTTP 404
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: at retrofit2.KotlinExtensions$await$2$2.onResponse(KotlinExtensions.kt:53)
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:161)
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:529)
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
09-04 19:38:08.604 5182 5182 E SettingsWearViewModel: at java.lang.Thread.run(Thread.java:1012)
Yeah, the phone has absolutely zero issue. It works very well and always has.
My network setup is fairly straightforward, HA in a LXC, Nginx as a reverse proxy in another LXC, ModSec, Suricata, Pfsense (split-DNS).
This is from my local network, with the phone on wifi.
The watch is brand new, purchased only for HA. A few days ago I tried a WatchOS of a colleague it logged-in to my HA instance just fine (this was from a different network).
edit: I can also access my HA instance fine from any network (1 year of hindsight)
if you bypass your own proxy setup does it register as expected? i suspect somewhere in that setup something is getting rejected. By default Wear OS does its own proxy magic from phone to watch so your network setup may not see things properly as a result of that proxying that apps cant avoid.
the thing is if the server returns a 404 error we cant fix that as its happening on the server side.
bypassing the proxy is honestly very painful. I would have to obtain a certificate, alter the DNS resolution, etc.
I'm not familiar with that WatchOS proxy magic, but maybe if you tell me more about it, or refer me to some documentation I would be able to diagnose the issue myself
I'm quite baffled by a 404. 403 and packets dropped I could pinpoint to WAF or IDPS. But I can't make sense of what could produce a 404.
its really just the first sentence from: https://developer.android.com/training/wearables/data/network-communication#network-access
When a watch has a Bluetooth connection to a phone, the watch's network traffic is generally proxied through the phone.
Have you made sure to properly configure the proxy and network to ensure the APIs are always accessible?
this page may provide some more tips for your own setup: https://companion.home-assistant.io/docs/troubleshooting/networking#addendum-reverse-proxy-via-nginx
I am not entirely sure where exactly the 404 is coming but the app makes a request and we get a response and in this case the response is not expected.
I may be on something, I hide services from Google. The Pixel presents itself as "Pixel 7 Pro", the watch presents itself as "Google Pixel Watch 2". Pretty sure it's on my side that I ban the word Google. Going to check this out
Ok, very sorry. That was it.
Home Assistant Android app version(s): 2024.7.3-full
Android version(s): 13
Device model(s): Pixel 7 Pro Pixel Watch 2
Home Assistant version: 2024.4.3 20240404.2
Last working Home Assistant release (if known): none
Description of problem, include YAML if issue is related to notifications: Cannot login using Pixel Watch / WearOS
Error Could not register watch on the Android side Error Watch was unable to register in the logs
Companion App Logs:
Screenshot or video of problem:
Additional information: HTTP logs
seems to be a problematic 404 on
/auth/token