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

The wyoming-v1 branch #63

Open
Shulyaka opened this issue Feb 16, 2024 · 4 comments
Open

The wyoming-v1 branch #63

Shulyaka opened this issue Feb 16, 2024 · 4 comments

Comments

@Shulyaka
Copy link

Hi @synesthesiam . Is the master branch maintained? What remains from the wyoming-v1 branch to be merged to master? Do you need any help with the project?

@KeithSBB
Copy link

see:
[wyoming-satellite]{https://github.com/rhasspy/wyoming-satellite/tree/master}

@synesthesiam
Copy link
Contributor

I do need help, but I haven't even had enough time to come up with a solid plan 🙃

Since developing Rhasspy v3, more emphasis has been put on Wyoming servers (usually via tcp). I would like to rework things so that external connections are the default (with program to program connections handled via stdio:// URIs).

With the Info messages, the main UI needs to be updated. I really wanted some mechanism for installing services, but it looks like Docker is probably going to be it.

Lastly, satellites now have their own Info section and set of messages. The Rhasspy server doesn't support any of this stuff yet 🫤

@KeithSBB
Copy link

@synesthesiam I feel sorry for you as you are obviously spread way too thin across many projects. As an outsider, I find it very difficult to understand which projects are key or what the software architecture is intended to be. The lack of comments in the code also makes that difficult for me.
However, I'm extremely grateful that you wrote wyoming-satellite as I now once again have a functioning remote HA voice assistant. Keep up the great work

@synesthesiam
Copy link
Contributor

@synesthesiam I feel sorry for you as you are obviously spread way too thin across many projects. As an outsider, I find it very difficult to understand which projects are key or what the software architecture is intended to be. The lack of comments in the code also makes that difficult for me.

It's frustrating to see issues and pull requests pile up, and know I'll likely never have the time to get to them. The "march of progress" from Python alone is enough to make it impossible to keep up. Code that was working just over a year ago is now broken because everyone in the world has to rebuild their dependencies every 6 months for the next Python version bump. And then a new Debian version comes out. And then a new PyTorch. And so on.

I don't have a grand vision for Rhasspy these days since the open source voice space is moving faster and faster. At this point, I think the best I can do is just wrap things with Docker and make them Wyoming compatible. And even then they will be broken and out of date in 3 months 🙃

However, I'm extremely grateful that you wrote wyoming-satellite as I now once again have a functioning remote HA voice assistant. Keep up the great work

Thank you, much appreciated!

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

3 participants