Wear OS issues | Home Assistant | Page 1

lofty plover Oct 16, 2022, 5:27 PM

#

All right, so I've actually got a couple different things that I'm trying to set up and it's still being weird. I'm not sure if the watch is being buggy, the watch app on my phone is being buggy, or if the home assistant app is being buggy...

#

First, is that based on my understanding of the documentation here, in the watches app on my phone I should be able to set up the tile

#

But there is no settings option when I activate the home assistant tile.

modest sand Oct 16, 2022, 5:29 PM

#

lofty plover But there is no settings option when I activate the home assistant tile.

you hae to configure it in the watch app

#

template tile needs to be set on the phone app

#

the docs actually mention this 🙂

lofty plover Oct 16, 2022, 5:30 PM

#

Oh, so by watch app it means the home assistant app on the watch?

modest sand Oct 16, 2022, 5:30 PM

#

correct 🙂

lofty plover Oct 16, 2022, 5:31 PM

#

Got it, I thought it meant the watch app for my phone. As in the one where I go to activate that tile. All right, Well there is still a bit of a problem then, because.. (working on getting a screenshot now)

modest sand Oct 16, 2022, 5:31 PM

#

yea i cna see that confusion because the Pixel Watch app is just called "Watch"

lofty plover Oct 16, 2022, 5:32 PM

#

Screenshot from watch.

#

So when I open the home assistant app right now, the only thing that shows up is that favorites folder, it's normally opened but I collapsed it for the purposes of the screenshot, and the very bottom section just shows a loading circle.

#

I'm guessing what's supposed to load down there is some extra parts that would allow me to configure the home assistant tile?

modest sand Oct 16, 2022, 5:33 PM

#

is it just stuck on loading?

lofty plover Oct 16, 2022, 5:33 PM

#

Yeah, it just loads for forever.

modest sand Oct 16, 2022, 5:33 PM

#

should take a few seconds to load your areas and domains

#

ok theres probably some logcat error happening there

lofty plover Oct 16, 2022, 5:33 PM

#

Screenshot from watch.

#

Eventually it does load like this, yeah

modest sand Oct 16, 2022, 5:33 PM

#

is there a setting chip below that?

lofty plover Oct 16, 2022, 5:33 PM

#

No, to there's not

modest sand Oct 16, 2022, 5:34 PM

#

ok, is the watch on bt or wifi?

lofty plover Oct 16, 2022, 5:34 PM

#

Let me check

#

If it helps make a difference, this is also the LTE version of the watch

modest sand Oct 16, 2022, 5:34 PM

#

no theres some issue with BT connection for some users where the proxying that Wear OS does is not accepted by routers

#

NAT loopback helps solve that

#

we woudl need to look at the logcat error to see if its that issue or not

#

but usually if you are on BT and hop on Wifi and hte issue gets resolved thats an indicator to the proxy error

lofty plover Oct 16, 2022, 5:36 PM

#

I can't tell if the Wi-Fi settings on the watch is just taking a second to load and recognize that it's connected, or if it's not connected until I actually open up the Wi-Fi settings.

modest sand Oct 16, 2022, 5:36 PM

#

takes a second to connect

#

wifi only gets enabled wehn its needed/requestd or on the charge

lofty plover Oct 16, 2022, 5:38 PM

#

That makes sense, because as soon as I open the Wi-Fi menu in the watch it connects, so it's probably getting its data through Bluetooth when that error is happening.

You've mentioned logcat a couple times, is that something I should send to the dev team to help resolve? If so, is there a noob friendly way of doing that?

modest sand Oct 16, 2022, 5:39 PM

#

no noob friendly way, youll need to connect the watch to a PC to get the lgos

#

now that hte watch is on wifi does the app load?

lofty plover Oct 16, 2022, 5:40 PM

#

I think the watch disconnects from Wi-Fi as soon as I close the Wi-Fi menu, I can try to put it on the charger to see if that makes a difference. I'll have to update later about that

modest sand Oct 16, 2022, 5:41 PM

#

so to get logcat youll need to follow https://developer.android.com/training/wearables/get-started/debugging

#

if you use android studio it will make getting the logs easier from there

#

you can also just check to see if your router supports NAT loopback too

#

I have seen a few users report that turning it on fixes that connection error (assumign thats the error you are hitting)

lofty plover Oct 16, 2022, 5:43 PM

#

All right, I'll try that, I'll see what I can figure out. I know that this watch doesn't appear to have any way to plug it into the computer, so it looks like I'll have to do the Wi-Fi option.

modest sand Oct 16, 2022, 5:43 PM

#

yea has to be wifi

#

what version of the watch app are you on?

lofty plover Oct 16, 2022, 5:47 PM

#

This is the Pixel watch LTE version,

Home Assistant Version on the watch
Beta-2762-93844FFE

Home Assistant Version on my phone
version beta-2762-93844ffe-full

I'm on Wear OS 3.5

#

Bug report from watch.

📎 wearable-bugreport-r11-RWD9.220429.053.G1-2022-10-16-13-40-36.zip

#

I don't know if this will be useful, but the watch app did allow me to take a bug report there.

modest sand Oct 16, 2022, 5:54 PM

#

looks like a connection error

#

10-16 13:40:14.817 10085 20196 24114 E WebSocketRepository: Websocket: onFailure 10-16 13:40:14.817 10085 20196 24114 E WebSocketRepository: java.io.InterruptedIOException: timeout

#

do you have a proxy or anything enabled?

#

yea so this does not seem to be the BT/Wifi error I mentioned prevoiusly

#

this is a timeout error meaning the app sent a request and did not get a response back in time

lofty plover Oct 16, 2022, 6:36 PM

#

modest sand do you have a proxy or anything enabled?

Nope, All just out of box standard settings. I use home assistant cloud for external, And I have the home assistant app configured to use a local address for what I'm on my home Wi-Fi.

#

If it helps, I also use a nest Wi-Fi router. I did check the settings there, I didn't see anything related to NAT loopback. There was something related to NAT but there wasn't anything I could change, and nothing that said loopback anywhere

#

Not sure if this is relevant, but I do use the http://homeassistant.local:8123 for the internal connection URL, as opposed to an IP address or something.

I use my regular nabu casa link for my standard address.

modest sand Oct 16, 2022, 6:38 PM

#

The timeout error is not something the app can solve.

#

The app gets the external URL from the phone if you used that

#

The wear app doesn't do any URL switching like the phone so it needs to use the external URL

#

Maybe try clearing data and ensuring that URL is used/selected if you don't remember what you used originally?

lofty plover Oct 16, 2022, 6:45 PM

#

Let me make sure my nabu casa url is working then, I almost never use it so that's one thing I've not tested yet. I almost exclusively use the internal URL since I'm basicly always home when I want to interact with HA

#

oh, yeah trying to use my nabucasa url also times out on my desktop. That's probably the issue.

#

It says in the HA Cloud section that it's working, but I'm going to try flipping that off and back on, seeing if that fixes it.

#

Ah, so that seems to be the problem, something is wrong with my nabu casa link, I guess I should ask for help in #cloud-archived instead then? Cause even at my desktop the nabu casa URL keeps timing out

#Wear OS issues