search

toverainc / willow

Open source, local, and self-hosted Amazon Echo/Google Home competitive Voice Assistant alternative
https://heywillow.io/
Apache License 2.0
2.6k stars 96 forks source link

Latest updates - constant GET /api/websocket HTTP/1.1 errors #150

Closed bert269 closed 1 year ago

bert269 commented 1 year ago

Hi

Updated this morning from the latest Github build and receive these errors - constantly: E (00:19:37.080) TRANSPORT_WS: Error read response for Upgrade header GET /api/websocket HTTP/1.1 Connection: Upgrade Host: 192.168.1.233:8123 User-Agent: ESP32 Websocket Client Upgrade: websocket Sec-WebSocket-Version: 13 Sec-WebSocket-Key: SQB//biJbHbqZUjGQygOhg==

E (00:19:37.095) WEBSOCKET_CLIENT: Error transport connect I (00:19:37.103) WILLOW: WS event ID: 2 E (00:19:57.107) esp-tls: [sock=54] select() timeout E (00:19:57.109) TRANSPORT_BASE: Failed to open a new connection: 32774 E (00:19:57.110) TRANSPORT_WS: Error connecting to host 192.168.1.233:8123 E (00:19:57.118) WEBSOCKET_CLIENT: Error transport connect I (00:19:57.124) WILLOW: WS event ID: 2 E (00:20:17.131) esp-tls: [sock=54] select() timeout E (00:20:17.133) TRANSPORT_BASE: Failed to open a new connection: 32774 E (00:20:17.134) TRANSPORT_WS: Error connecting to host 192.168.1.233:8123 E (00:20:17.142) WEBSOCKET_CLIENT: Error transport connect I (00:20:17.148) WILLOW: WS event ID: 2 E (00:20:37.154) esp-tls: [sock=54] select() timeout E (00:20:37.156) TRANSPORT_BASE: Failed to open a new connection: 32774 E (00:20:37.157) TRANSPORT_WS: Error connecting to host 192.168.1.233:8123 E (00:20:37.165) WEBSOCKET_CLIENT: Error transport connect I (00:20:37.171) WILLOW: WS event ID: 2 E (00:20:57.179) esp-tls: [sock=54] select() timeout E (00:20:57.180) TRANSPORT_BASE: Failed to open a new connection: 32774 E (00:20:57.181) TRANSPORT_WS: Error connecting to host 192.168.1.233:8123 E (00:20:57.189) WEBSOCKET_CLIENT: Error transport connect

Device seems to respond ok, so mainly informational ? This is the Home Assassinate instance - no problems on that side.

kristiankielhofner commented 1 year ago

Our suspicion is your websocket connection to HA is getting terminated/reset.

Is there a firewall or anything like it between Willow and HA? Can you try a long-running ping to the IP of your Willow device to see if there are any drops?

bert269 commented 1 year ago

I do have a piHole setup as an add-blocker/DNS on my network - that's it.

By 'willow device' I assume you mean the Ubuntu box I am using to do the Willow software installations onto the ESP-Box, right? Will do and report back.

bert269 commented 1 year ago

Update: by the time I receive this post for a ping request - the ESP-Box has stopped the dropping of connections and continue as normal. I restarted it and it did not happen again. I will keep an eye on it and as soon as it happens again, quit the monitor and run the ping.

kristiankielhofner commented 1 year ago

Do you consider this issue resolved at this point?

bert269 commented 1 year ago

I have not seen it happen again after reflashing onto two ESP boxes(one a lite).

kristiankielhofner commented 1 year ago

Fantastic - thanks for working through this with us!