Wear OS - "Could not connect"

Dumonster · February 1, 2022, 6:14pm

I’ve installed the app on my Wear OS watch (Ticwatch Pro 3 GPS).

The instance is detected. However, when trying to connect, I get the message “Could not connect”.

I looked around and some people suggested trying via Wifi but that didn’t work either. I believe it’s some sort of bug.

dshokouhi · February 1, 2022, 6:22pm

a few users have issues logging into the app…can you try logging in with the phone to see if that works?

Make sure you are running the latest beta version of the app too.

github.com/home-assistant/android

Wear OS: Can't connect to Home Assistant instance over Bluetooth

opened 06:59PM - 02 Nov 21 UTC

Wombosvideo

bug Wear OS

**Home Assistant Android version:** WearOS version `beta-1626-edc4142` Phone v…ersion `beta-1626-edc4142-full` **Android version:** WearOS 2.33 Android 11 **Phone model:** OnePlus 7 Pro **Home Assistant version:** core-2021.11.2 **Last working Home Assistant release (if known):** None. **Description of problem:** Wear OS can't find my Home Assistant instance. It neither shows up in the list nor lets me manually connect. Works fine on WiFi (with disabled Bluetooth) or with the phone and other devices in my network. **Traceback (if applicable, to get the logs you may refer to: https://companion.home-assistant.io/docs/troubleshooting/faqs/#android-crash-logs):** *unavailable* **Screenshot of problem:** *unavailable - there is a sad cloud icon with the message "Could not connect" but it vanished too fast to screenshot* **Additional information** No public instance, i.e. no Nabu Casa Not using a VPN - neither phone nor watch After a successful log in over WiFi and switching back to Bluetooth, the list of buttons is empty and it just shows the titles. Update for version `beta-1626-edc4142`: After a successful log in over WiFi and switching back to Bluetooth, there is a title "Loading" and a primary button "Please wait while we load your entities" but nothing ever happens.

github.com/home-assistant/android

Wear OS app not connecting in any way

opened 09:23PM - 25 Jan 22 UTC

doppiaemme

bug Wear OS

**Home Assistant Android version:** 2022.1.1 **Android version:** **Phone… model:** **Home Assistant version:** 2021.12.10 **Last working Home Assistant release (if known):** **Description of problem:** Can't connect, always getting "Cloud not connected" message Ticwatch Pro 3 Ultra, WearOS app is installed on an iOS device not Android. Typed the URL manually. I understand the BT VS WiFi connection. Other apps work both in BT proxied mode and Wifi direct connection. I have tried first with BT on, then with BT OFF and Wifi only. nothing changes. Tried both the external URL and the internal URL to HA, no difference. The URL work from a browser on the watch and it CAN reach the UI Am I missing something obvious? **Traceback (if applicable, to get the logs you may refer to: https://companion.home-assistant.io/docs/troubleshooting/faqs/#android-crash-logs):** ``` ``` **Screenshot of problem:** **Additional information:**

wuench · February 12, 2022, 8:09pm

I have the same issue. Can’t connect. Beta, no beta. I am running a public certificate, android 11 on moto z4 has no issues. Ticwatch Pro 3 can’t connect. Been trying to get this to work for months, every release I hope something has changed.

I am using 2 factor, it prompts for all my inputs then just goes back to the Login Wear OS Device screen on the phone. Watch app shows the instance but says Could not Connect.

The whole “make sure you are running the latest beta” thing seems like too much complexity, it doesn’t download right away when you switch. If we had any real control over which version we were running at any time via Google Play it would make sense but we can’t. You shouldn’t advertise this in the release if it requires the beta to work.

EDIT: sorry I am on android 10 not 11

dshokouhi · February 12, 2022, 8:10pm

Try turning off Bluetooth on the watch and connect, does it work?

wuench · February 12, 2022, 8:13pm

Bluetooth is on the phone sees the watch… Do you think it is related to 2 factor, there seems to be a pattern in the reports of people not working that they are using 2 factor.

Just tried to uninstall the app on watch. Phone app detected it was missing but if I click the Install App on Wear Device I get an error “Play Store Request Failed Wear Device May Not Support Play Store” The android watch version is android 9, maybe that’s a clue?

dshokouhi · February 12, 2022, 8:41pm

I meant to turn off Bluetooth so you can connect using WiFi

Can you check Companion App logs to see what the failure there was?

wuench · February 12, 2022, 9:57pm

Thanks bluetooth off does work if I input my internal address on the watch itself. External is going through HAProxy w/ SSL offload so there appears to be an issue on my end there.

If I re-enable bluetooth the phone app can manage the watch but the watch can’t communicate with HA again, can’t load entities, etc.

dshokouhi · February 12, 2022, 10:03pm

so this is a known issue only impacting some users but not all, if you refer to this thread you can see several different workarounds and fixes users have discovered

github.com/home-assistant/android

Wear OS: Can't connect to Home Assistant instance over Bluetooth

opened 06:59PM - 02 Nov 21 UTC

Wombosvideo

bug Wear OS

**Home Assistant Android version:** WearOS version `beta-1626-edc4142` Phone v…ersion `beta-1626-edc4142-full` **Android version:** WearOS 2.33 Android 11 **Phone model:** OnePlus 7 Pro **Home Assistant version:** core-2021.11.2 **Last working Home Assistant release (if known):** None. **Description of problem:** Wear OS can't find my Home Assistant instance. It neither shows up in the list nor lets me manually connect. Works fine on WiFi (with disabled Bluetooth) or with the phone and other devices in my network. **Traceback (if applicable, to get the logs you may refer to: https://companion.home-assistant.io/docs/troubleshooting/faqs/#android-crash-logs):** *unavailable* **Screenshot of problem:** *unavailable - there is a sad cloud icon with the message "Could not connect" but it vanished too fast to screenshot* **Additional information** No public instance, i.e. no Nabu Casa Not using a VPN - neither phone nor watch After a successful log in over WiFi and switching back to Bluetooth, the list of buttons is empty and it just shows the titles. Update for version `beta-1626-edc4142`: After a successful log in over WiFi and switching back to Bluetooth, there is a title "Loading" and a primary button "Please wait while we load your entities" but nothing ever happens.

wuench · February 12, 2022, 11:09pm

I have read through that several times. Nothing has worked for me with bluetooth on yet.

At least I have a working case now so I can take some network captures and compare working to not working. I will update that thread if I find any more work arounds.

Thank you for your help.

wuench · February 13, 2022, 8:13pm

Turns out that this was a result of not sending the full certificate chain on my HAProxy setup. Let’s Encrypt recent changed their intermediate certificate and I guess the Ticwatch Pro doesn’t have that new cert in its cert store as valid. By sending the full cert chain the watch was able to accept the certificate.

dshokouhi · February 13, 2022, 8:32pm

can you please mention this in the issue, maybe it will help the next person

alexandrechoske · February 18, 2022, 2:32am

Hi Guys, I have my TicWatch E3 connected to HA using WearOs, working fine, but I wanted to make some notify on the watch and I got this error message:

But the app on watch does not have so much configs, is there a way?

dshokouhi · February 18, 2022, 2:33am

notifications do not work on Wear OS at the moment

alexandrechoske · February 18, 2022, 2:35am

ok got it, should be a nice implementation btw, to see some notifications with sensor data on mobile would be awesome!

thanks for the fast reply!

emilef · March 18, 2022, 6:16pm

Can you please tell me how did you resolve this? Thanks a lot!

wuench · March 18, 2022, 7:15pm

I use pfsense to serve my HAProxy and the pfsense ACME plugin to pull the cert. The acme plugin was already building the full chain cert I just needed to edit the acme code to put that in pfsense’s certificate store.

The full chain cert is putting the endpoint, internmediate and root certs all in one text file.

theCrow · March 23, 2022, 1:16pm

I had this problem with Galaxy Watch4 and it was caused by the firewall app on my phone (AfWall) blocking Galaxy Wearable app’s access to LAN.

mgrenier25 · July 25, 2022, 4:01am

I’m having a similar issue with a Ticwatch pro S

Model : WF12096
Android 9 / June 1rst 2020 security update
Wear os version : 2.37

Companion app is working fine on phone, when I try to connect to HA instance from the watch I get the sad emoji saying something went wrong, I tried with both Bluetooth on and off.

Any ideas?

Valentino_Stillhardt · August 2, 2022, 1:50pm

TicWatch Pro 3 Ultra GPS user here.

WearOS companion app doesn’t load saying “Error loading entities”.

Bummer

DamiaoRocha · November 16, 2022, 6:22pm

I have the same problem. I opened an issue on Github Wear: Error loading entities · Issue #3074 · home-assistant/android · GitHub, but I am not able to deliver the logs the way the developer needs. If you know how to do this and can do it, I would appreciate it.