-
Notifications
You must be signed in to change notification settings - Fork 470
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
homeassistant-core
wyoming
enabled voice assistant add-ons
#481
homeassistant-core
wyoming
enabled voice assistant add-ons
#481
Conversation
Cool @ms1design ! Okay, I see in your docker-compose you are building everything against CUDA 12.4 which is why it is going after PyTorch 2.3rc, however that isn't really stable yet (I added it mostly for preliminary TRT-LLM work). Right now until I can merge your PR, I will build/upload the wheel for pytorch 2.2 for Python 3.11 and CUDA 12.2. Then when PyTorch 2.3 is actually released (it is currently up to RC12), I will build that. |
Ahhh that makes sense @dusty-nv, dunno why I missed that ;) Let me just rebuild those against I need to spend some time to update my CI/CD env to support latest improvements here :) |
I think it will still make you build pytorch 2.2 for python 3.11 because I don't have that up yet...kicking it off now |
OK, pytorch 2.2 wheel for Python 3.11 and CUDA 12.2 is up: http://jetson.webredirect.org/jp6/cu122/torch/2.2.0 Will look at merging this PR shortly! |
All packages should be in python 3.11. It is the standalone now from desktop, so people that come to jetson, it would be fine to find python3.11 packages |
@johnnynunez I am not changing the default python version away yet for all containers from what is the default on that version of ubuntu (so python 3.10 on ubuntu 22.04), but for the containers that need it they can specify which python they need |
Yes yes, your solution is great |
Nice @dusty-nv, will try that tomorrow 🙌 |
Fixed From the good news I managed to integrate all required containers into working state with Home Assistant in a way that we can configure full Voice Assistant Pipeline in HA running on Jetson: We can choose the languages and models:
There's still quite a lot of TODO's in this PR, but it's ready for initial testing if anyone is interested :) Questions welcome. |
Oh wow, that's amazing you got all the add-ons build, loading, and running! Huge step, thanks @ms1design !! Maybe wyoming-piper needs to specify
In parallel with your efforts, I have been integrating PiperTTS into the NanoLLM agents today. It's sounding good! |
Correct @dusty-nv , when you follow my mention on rhasspy/wyoming-piper#5 you will find the required changes there as a |
Update:
wyoming-piper-gpu.mov |
Update:
Known Issues
|
Update
Known Issues
TODO
|
…core-voice-addons
🥳 🙌 🎉 thanks @ms1design!, trying to build these now - will push to dockerhub if successful. Are there additional procedures needed to document for when others are testing? Or do you basically just need to change |
Hi @dusty-nv, Basically one should take a look on the all Edit: |
OK gotcha - eventually we will have an entire section on Jetson AI Lab with easy-to-follow HomeAssistant tutorials for setting up the AI services, but for now it would be nice to have lower-level notes for ppl on the forums/ect who want to try this. Chugging through the builds now! |
That’s understandable, I’m gonna work on that on upcoming days 🙌 |
Hitting an issue where these containers use Python 3.11, and also use tensorrt (at least the piper one does) - but tensorrt only installs python bindings for the default version of Python (i.e. 3.10). I believe I can get around this by having the tensorrt container build it's bindings from source, but I'm curious how you got around this in your builds? |
I think it fails when you run tests, right? Its not the build that fails |
Yea, the tests...I just disabled that test for now, because I don't believe |
I had the same feeling so tbh I skipped that and later forgot about it completely 🤓 |
@ms1design do you see potential side-effects in your docker-compose setup if I change |
Not tried that. What I tried was setting the entrypoints from docker-compose.yaml file, but I was facing some PID issues. edit: @dusty-nv I had issues when using —init, thats why I explicitly set it to false in docker-compose |
OK, here they are!
|
Hi @dusty-nv,
Pushing this in hope that you could build on your farm the
pytorch
wheels fromwyoming-piper
container (mentioned here) to yourpip
repo.It's also a good starting point to testing all integrations working together over
wyoming
protocol. I don't expect it will work out of the box – I can test it on my devices on the weekend.If anyone wanna to try this, here's the
docker-compose
I'm using for testing: