The latter module opens a tcp socket over the port 34567 for the ip of my rhasspy docker container, which has the EV PULSE_SERVER = 192.168.2.34:34567 which is the IP of my server and the port from the loaded module. I load pulseaudio modules module-native-protocol-tcp auth-ip-acl=127.0.0.1 auth-anonymous=1 and module-native-protocol-tcp port = 34567 auth-ip-acl=172.17.0.2.
#Usb redirector customer module software#
At the Host OS, i use pulseaudio and ledfx (a software to stream audio reactive lightshows to WLED devices) with my USB mics. Rhasspy runs as a docker container, not as Home Assistant addon. Let me explain my setup: Im using Manjaro Linux on my old Hardware (Intel Core I5-8000 with 16GB RAM) running home assistant supervised install. Should I run Rhasspy in an own Container/VM?.Should I ditch USB-Redirect, because there is a better solution to my problem?.Is there an existing Addon, which I just was to stupid to find with the search?.At least for other VMs apart from Home Assistant OS, as there’s no way to deploy the USB-Redirect client onto HassOS through the bash. I got around this by using USB-Redirect ( USB Redirector for Linux - USB over IP - USB over Network - Incentives Pro). This is no HassOS issue, it is a Proxmox (kvm) issue. Problem is, that if I pass thorugh the USB mic to HassOS the VM instantly dies.
I’m using Home Assistant OS inside a Proxmox VM, running on a NUC. So I purchased a cheap USB mic to do the trick, before I’m willing to invest more money on a better one. Currently I’m trying to get rhasspy up and running.įor this I need a microphone. Hi there, I’m quite new to HA and trying to build some neat Smart Home possibilites for my small flat.
0 kommentar(er)
