Nick Bento

@kristiankielhofner yeah I noticed my devices with debug, even without monitoring, seemed fine all day. As a test I left one on debug build and set another to a non-debug...

Update this morning, left the devices idle all night, one on debug and one with no debug turned on, and they both responded and worked fine this morning. Really not...

> I came from the "main"=-branch, meaning flashing willow from a connected server. No noticible errors / blanks screens. Last week I installed and run WAS on the same server...

This would involve building the willow code as outlined on the willow repo (would have to git pull feature/was branch) and then following the steps on the was repo to...

I don't think there is any particular microphone/speaker we could recommend, as it just depends on what is supported by the ESP-ADF. In our discord we have some users working...

Sounds like corrupt tts cache. You may need to stop wis, the navigate to the nginx directory and do sudo rm -rf cache

It's actually not in the docker container, it would be in the directory you built WIS from. If it's empty it may be because your user doesn't have permission to...

If cache is gone, only other things i have seen cause this are network issues, boxes needing a reboot, or the GPU running out of VRAM. Are you running latest...

If you send a tts request directly to wis in the browser, is it doing the same thing? For instance you could send something like https://wis:19000/api/tts?text=Sorry+I+couldn't+understand+that

So that points to issue being either network the boxes are on, or the boxes themselves. Have you tried rebooting the boxes? I also checked home assistant, and the literal...