rhasspy/rhasspy3

The `wyoming-v1` branch

Shulyaka opened this issue · 4 comments

Shulyaka commented

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?

synesthesiam commented

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 commented

@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

  • ❤️1
synesthesiam commented

@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!

  • 👍4