Open TarheelGrad1998 opened 11 months ago
If the error occurs on the watch then the logs from the phone app will not be correct here. Unfortunately the only way to get logs from the watch is using logcat.
Ok, any clues on how to do that?
Easiest solution is to hook up watch to android studio and grab logs that way.
https://developer.android.com/training/wearables/get-started/debugging#wifi-debugging
For Assist "Oops, an error has occurred" this could also have happened on the server, check the run history in Settings > Voice assistants > [your assistant] > Debug (in the overflow menu).
For Assist "Oops, an error has occurred" this could also have happened on the server, check the run history in Settings > Voice assistants > [your assistant] > Debug (in the overflow menu).
I did just have it happen again, but checking there did not have a recent/related entry.
Easiest solution is to hook up watch to android studio and grab logs that way.
https://developer.android.com/training/wearables/get-started/debugging#wifi-debugging
Easy, my behind. Frustrating. I installed the Android Studio and bumbled my way through the steps, but adb keeps giving me "Failed to connect to IP:port". Rebooted the watch, still no luck. Maybe I'm doing something wrong, no idea. I'm not even a dev anymore much less an Android dev. I'm giving up for now.
So much for Assist replacing Alexa.
did you make sure to pair the device to adb before attempting to connect?
No. How do I do that?
No. How do I do that?
On the same screen where you got the port select pair device. run adb pair 192.x.x:xxxx
using the IP and port in the pair screen then when prompted enter the pairing code found on teh same screen, then run the connect command
Thanks. That worked, and I was able to pull about 12MB of logcat logs.
However, correct me if I'm mistaken, but I assume you'd want a log of around when an error happened? Further, based on research it appears the timestamps from logcat are in the device's time? The logs I was able to pull are all timestamped from 1:30 p.m. - 3:30 p.m. today, and I last got an "Ooops" around noon, so it wouldn't cover any events in question.
I'm guessing it's only keeping about 2 hours of logs, so I'd need to have it happen and then pull the logcat within that 2 hours?
As another point of reference, I'm experiencing this on a Samsung Galaxy fold 4 with a Samsung watch 6 LTE.
Sorry for the delay. Needed the right combination of the issue to occur plus time to pull the logs. I am getting "Assist couldn't reach Home Assistant..." this morning, and here is the logcat output: logcat.txt
Did you guys get everything you need on this? If not, let me know, it still happens every couple of days.
the only error I see in the logs is listed below however the log line above it seems to indicate this error might be related to our complication and not assist.
12-07 09:03:11.341 31987 8482 E WebSocketRepository: Websocket: onFailure
12-07 09:03:11.341 31987 8482 E WebSocketRepository: java.net.SocketException: Software caused connection abort
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.net.SocketInputStream.socketRead0(Native Method)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.net.SocketInputStream.socketRead(SocketInputStream.java:118)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.net.SocketInputStream.read(SocketInputStream.java:173)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.net.SocketInputStream.read(SocketInputStream.java:143)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.readFromSocket(ConscryptEngineSocket.java:945)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.processDataFromSocket(ConscryptEngineSocket.java:909)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.readUntilDataAvailable(ConscryptEngineSocket.java:824)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at com.android.org.conscrypt.ConscryptEngineSocket$SSLInputStream.read(ConscryptEngineSocket.java:797)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okio.InputStreamSource.read(JvmOkio.kt:94)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okio.AsyncTimeout$source$1.read(AsyncTimeout.kt:125)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okio.RealBufferedSource.request(RealBufferedSource.kt:206)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okio.RealBufferedSource.require(RealBufferedSource.kt:199)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okio.RealBufferedSource.readByte(RealBufferedSource.kt:209)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.kt:119)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.kt:102)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.kt:293)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okhttp3.internal.ws.RealWebSocket$connect$1.onResponse(RealWebSocket.kt:195)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
12-07 09:03:11.341 31987 8482 E WebSocketRepository: at java.lang.Thread.run(Thread.java:1012)
I do see a few of to confirm my suscipion
12-07 09:03:44.810 31987 31987 E EntityStateDataSourceService: Unable to get entity state for sensor.kennedy_humidity: Job was cancelled
maybe @jpelgrom see's something I dont?
maybe @jpelgrom see's something I dont?
Unfortunately not. The "Assist couldn't reach Home Assistant, check your connection" message should only show up if it fails the initial load and "Oops, an error has occured" only if the mic is unexpectedly unavailable, but 1) that should be recoverable by closing and reopening, 2) I would at least expect to see getting the config in the log/a more specific websocket failure than connection closed for a complication update and 3) the server Assist logs should also show something for the second message.
Thanks for checking. I'll get another example or two, maybe that will help. My instinct says it's something about the watch switching between phone and wifi, as it usually seems to happen the first time I entered a new room. FWIW.
Home Assistant Android app version(s): 2023.10.2-full Android version(s): 13 (Wear OS 4.0) Device model(s): Moto Razr+ (Samsung Watch 4) Home Assistant version: 2023.10.1 Last working Home Assistant release (if known):
Description of problem, include YAML if issue is related to notifications: When trying to use Assist on Wear OS, I frequently encounter one of these two errors: Oops, an error has occurred Assist has had trouble connecting to Home Assistant
Companion App Logs:
Screenshot or video of problem:
Additional information: My watch is not consistently connected to my phone, but is usually either that or on my home wifi. My intuition says that switchover of the connection might be related. However, Assist has worked both connected to my phone and wifi. Also when this happens, I can go into the HA Wear OS app and access HA, so the app itself is connected but somehow I cannot use Assist. When I get the "Assist is unable to connect" message, I've only been able to restore access by rebooting the watch.