Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: WIS HTTP 530 #160

Open
profucius opened this issue Dec 2, 2024 · 14 comments
Open

Error: WIS HTTP 530 #160

profucius opened this issue Dec 2, 2024 · 14 comments

Comments

@profucius
Copy link

Hello, a few days ago I started getting this new error on my ESP BOX devices when trying to speak a command. The device recognizes the "Alexa" call, but then immediately says WIS HTTP 630 on the screen. It does not process any audio.

Has something changed?

@hamishcunningham
Copy link

I saw someone else commenting that the Tovera server is down, so if you're using that one that could be the reason

@profucius
Copy link
Author

profucius commented Dec 2, 2024

Yes I think that may be what's happening. I tried visiting https://infer.tovera.io/api/willow and it says

Error 1033 Ray ID: 8ebd5c2afa1853db • 2024-12-02 18:25:31 UTC Argo Tunnel error

I wonder if @kristiankielhofner is aware of this outage

@oywino
Copy link

oywino commented Dec 2, 2024

I have recently been getting the same error message, but I'm not aware that I'm using anything named a "Tovera Server" (?)
Please explain how I can check this/be sure (or eliminate this possibility).

@profucius
Copy link
Author

profucius commented Dec 2, 2024

I have recently been getting the same error message, but I'm not aware that I'm using anything named a "Tovera Server" (?)
Please explain how I can check this/be sure (or eliminate this possibility).

Tovera server is the Willow Inference Server (WIS) that the dev is hosting. If you are not hosting your own WIS to interpret voice data, then you're using the Tovera server by default.

You can check which server you're using in your Willow Application Server (WAS) under settings.

@oywino
Copy link

oywino commented Dec 4, 2024

You can check which server you're using in your Willow Application Server (WAS) under settings.

It says: https://infer.tovera.io/api/willow?force_language=no

Do you know if we can expect a fix anytime soon?

@profucius
Copy link
Author

Do you know if we can expect a fix anytime soon?

My thought is no. If you look at the dev history on both WAS and WIS, they've both been quite nearly abandoned. I suspect the developer has moved onto other projects. They may not even use this project in their own home, otherwise they would have noticed it being down already.

The good news is there are other options. I haven't had the time yet to invest into this yet. You can either install your own WIS server locally and replace the URL in your settings, which would fix your voice recognition. Or you can drop Willow altogether and switch to a built-in HASS voice solution like the Wyoming Protocol. I'm leaning toward the latter myself, although it is more time investment and possibly won't work with our current hardware (or it may). If you're only interested in getting your current system running again, then install your own WIS, but that would require an always-on PC with at least a GTX level graphics card.

Just FYI from my research so far. I may post an update here later once I've made my choice and spent the time to move on it.

@nikito
Copy link
Contributor

nikito commented Dec 4, 2024

If you check discord, myself and a few others also run the HA solution with local Wyoming Protocol servers that are GPU accelerated, using the same hardware (ESP Box and ESP Box 3 that Willow also uses), so it is possible if you wish to do so. :)

@profucius
Copy link
Author

If you check discord

Which discord would that be? I don't see a link to it anywhere in the repo readme.

@nikito
Copy link
Contributor

nikito commented Dec 4, 2024

https://heywillow.io/get-involved/

@profucius
Copy link
Author

profucius commented Dec 4, 2024

https://heywillow.io/get-involved/

Thanks, taking a look in there now. I'm a bit disoriented to discord, could you share a direct link to the discussion you mentioned, using Wyoming Protocol with the ESP Box? I'd really like to join into that discussion and/or read about how you all did it, so that I can try doing it too. Thank you

@nikito
Copy link
Contributor

nikito commented Dec 4, 2024

There's not really a specific discussion i don't think, it's just been brought up several times. There's some tutorials online about how to achieve it i think. HA discord or forums might also mention how.

@profucius
Copy link
Author

profucius commented Dec 4, 2024

Thanks, I opened a thread over there for further discussion. For anyone else interested, it's here.

I'll leave this ticket open for now, since the original issue is still ongoing, and I want the dev to have a chance to see if (if they're at all interested in fixing it, or perhaps this ticket can be a place that the dev officially tells us they're not going to fix it)

Update: I am now thinking that this new project is ideal, regardless of the Willow project's future, because it is actively developed software that has more features coming in the future.

@profucius
Copy link
Author

#161 Very sad news...

@JayPearlman
Copy link

A few weeks ago I started working on a replacement endpoint due to the 530 error. It's awful that Kristian is no longer with us as he created so many wonderful things. I'm sharing the link to my code in this thread in hopes that it can keep the usage of the Willow project active. My code to use a Cloudflare Worker endpoint instead of WIS: https://github.com/JayPearlman/WIS-CF-Worker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants