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

Multinet and external STT at the same time #205

Open
A6blpka opened this issue Jun 26, 2023 · 1 comment
Open

Multinet and external STT at the same time #205

A6blpka opened this issue Jun 26, 2023 · 1 comment

Comments

@A6blpka
Copy link

A6blpka commented Jun 26, 2023

Maybe you want to look at using two STT variants at the same time.
If an external STT service is unavailable (maintenance, no internet connection, etc.), Willow could try to recognize the command on the local Multinet.
I don't know if Willow has the resources to do these processes in parallel, but you can do them in sequence.

@kristiankielhofner
Copy link
Contributor

As part of #25 we're adding health/status checks for WIS, HA, and others.

The issue with this approach (as you say) is having the model loaded, and with up to date commands that make any sense. Additionally, we would need to be careful in terms of user expectation because multinet fundamentally cannot support many of the commands of WIS so users will be caught off guard when Willow switches back to multinet for whatever reason - commands that used to work likely won't. We could of course provide status on the display but as a far-field device where you either can't see or aren't looking at the display this is of dubious value.

Additionally, we would have to look hard at how feasible this is fundamentally because the ADF framework we use currently initializes and loads multinet on boot depending on configuration. We'd have to really explore how this could work. However, on that note, post initial stable release we want to generate the multinet vocabulary on device dynamically (from WAS) so we could look at this as part of that process.

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

2 participants