First, I am new to Home Assistant, having just spun it up on a Hyper-V VM on my PC today. That part went surprisingly smoothly. I had no problem adding/controlling devices from my PC.
After this, I installed the HA app on my Galaxy S22 Ultra phone (Android 14). After a slight hiccup (changed my VM virtual switch to External), I had no problem controlling devices from my phone.
Next, I tried my Pixel Watch 2 (Wear OS 5). I installed the HA app on my watch. After a fair amount of difficulty between the watch and phone apps, I got logged into HA on the watch. The watch shows up no problem and I can see things like its battery life on my PC.
Then, I tried to use the Assist tile. This where things broke down completely. For a long time, I was unable to get the tile to connect to the HA server.at all.
Based on other posts, as an experiment, I disabled Bluetooth. Suddenly everything worked fine (ish). However, this is not a good long-term fix, since Bluetooth is sort of important for other reasons.
Is there a long-term fix? Is a bug-fix for the Wear OS Assist tile in-progress with the Home Assistant team?
Or, is there something I need to change? If so, please explain it like I am exceptionally stupid. Because, at the moment, I feel a bit that way
I’m not sure I understand why this is a problem. WIFI is enabled on my watch. It works fine. It even works when controlling devices via my HA server (providing Bluetooth is disabled). Finally, it seems to work (even when Bluetooth is enabled) to communicate things like battery life.
While not particularly relevant, the Bluetooth communication between my watch and phone also works fine as does the WIFI communication between my phone and the HA server.
I’d greatly appreciate any advice on things I have not tried yet.