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.56k stars 96 forks source link

WILLOW: failed to read HTTP POST response #79

Open shahraizq opened 1 year ago

shahraizq commented 1 year ago

Im getting this error "E (17:30:07.558) WILLOW: failed to read HTTP POST response" after i have flashed it and connected it. any one faced any similar issue and know how to resolve this?

shahraizq commented 1 year ago

Fixed wrong api key was entered.

kristiankielhofner commented 1 year ago

We can actually address this by attempting to connect to the API at build and verifying the credentials configured. Leaving open to document and track that.

pthimon commented 1 year ago

I had the same 401 error when using homeassistant 2023.3.1. I upgraded to 2023.5.3 and restarted willow and I think meant that willow switched to using websockets, and then the requests were authenticated ok.

(If anyone else has to upgrade honeassistant, make sure you upgrade to 2023.4.6 first, as there seems to be a database migration bug if going straight from 2023.3.1 to 2023.5.3)

stintel commented 1 year ago

The 401 was totally my bad: 9ceb5d617da79c9b00d7c34b91879c4b882e9c3a.

stintel commented 1 year ago

With WAS, we're doing a basic connectivity check to the endpoint URL. We will move endpoint support from Willow to WAS in the future, and when we do that we will add authentication to this connectivity check.