Closed AnderssonPeter closed 1 year ago
Reverse proxies are not supported, especially for Wear OS (there's no web browser on there).
@jpelgrom Somewhat confused why would a reverse proxy be a problem? (It just forwards the request to another server or process)? Also it's fairly common to have a reverse proxy infront of you services otherwise you could only have one service per ip/port? edit: but just to be sure I will try without a reverse proxy!
Sorry, I should have clarified reverse proxies with an authentication layer and looked at the logs before responding.
There appears to be an SSL issue:
03-29 16:37:07.249 5102 5102 E PhoneSettingsListener: Unable to login to Home Assistant
03-29 16:37:07.249 5102 5102 E PhoneSettingsListener: javax.net.ssl.SSLHandshakeException: Handshake failed
(...)
03-29 16:37:07.249 5102 5102 E PhoneSettingsListener: Caused by: javax.net.ssl.SSLProtocolException: SSL handshake aborted: ssl=0xa9571988: Failure in SSL library, usually a protocol error
03-29 16:37:07.249 5102 5102 E PhoneSettingsListener: error:1000042e:SSL routines:OPENSSL_internal:TLSV1_ALERT_PROTOCOL_VERSION (external/boringssl/src/ssl/tls_record.cc:592 0x9675cf08:0x00000001)
Your watch appears to use Android 9 so it may not support the latest versions. I'm assuming for your requirements you intended to refer to TLS 1.3, which is only supported on Android 10+.
@jpelgrom Thanks enabling TLS 1.2 did the job, I only enabled the following suites. 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
@jpelgrom It would be nice if the wear os or android app would display a error when this happens, as its right now nothing happens leaving you somewhat in the dark.
I agree error handling could be improved, I do intend to work on it (some other improvements had to be made first).
Edit: first improvements in #3450
I agree error handling could be improved, I do intend to work on it (some other improvements had to be made first).
👍 Thanks for a great project and the help identifying the issue
Home Assistant Android app version(s):
Android version(s): Phone: 13 WearOS: 2.41 Device model(s): Phone: Pixel 6 Pro WearOS: TicWatch Pro 3 Ultra GPS
Home Assistant version: 2023.3
Last working Home Assistant release (if known): I have never had this working
Description of problem, include YAML if issue is related to notifications: When I start the home assistant app on my watch I get 2 options
When I select the one my phone uses, it tells me to connect on my phone. Here I enter my credentials, then it shows a connect watch to Wear OS screen where I can assign a id and has a continue button. I click continue and it throws me back to the "Settings for Wear-devices" screen. When I wake my watch again it's still at the screen i was at when i first started the Home Assistant app on it.
Companion App Logs:
Logs collected from Wear OS using adb logcat:
Logs from Android phone (Collected using the button in app, its not the exact pair try but gave same result)
Additional information:
I'm 99% sure that my watch was using wifi as I was collecting logs from it using adb over wifi while trying to connect.
Setup: Debian GNU/Linux 11 Docker version 23.0.2, build 569dd73 Docker Compose version v2.17.2
Seems like more than me have this problem found the following threads: https://community.home-assistant.io/t/cannot-log-in-from-home-assistant-wear-os-app/477273/13