#if anyone is interested, i just finished
1 messages · Page 1 of 1 (latest)
let me have a look, one moment
I think my issue is that it randomly does not stop listening after it starts tts
ah ok...
no, i am using rhasspy currently.
it worked a LOAD besser initally on the raspberry pi zero 1, but i am not happy with it, as it is deprecated.
I am using the rhasspy wyoming applications
hmmm, i had that once... when using raven, which is the precedessor of openWakeword i think
yes, and i am on the original rhasspy. the one which communicates via Hermes
dockerized.
what are you running now?
thats my docker-compose.yml:
version: "3.5" services: rhasspy: image: rhasspy/rhasspy:2.5.11 container_name: rhasspy restart: unless-stopped group_add: - audio environment: - PUID=1000 - PGID=1000 - TZ=Europe/Vienna volumes: - ./profiles:/profiles - /etc/localtime:/etc/localtime:ro ports: - 12101:12101 devices: - /dev/snd:/dev/snd command: --user-profiles /profiles --profile de
you install docker on pi zero ?
ofc
🙂
as docker has nearly no overhead ... why not
and it makes managing the code so much easier.
sorry for my ignorance, is rhasspy an alternative for openWakeWord?
no, its a completely different system.
rhasspy was there before homeassistant started the year of the voice.
during the year of the voice the developer behind rhasspy kind of switched to homeassistant ? or something similar.
basically homeassistant is now attemptimg to do what rhasspy did before.
that means:
managing the different parts of the system
wakeword, speech recognition, intent handling, etc
rhasspy kind of sits outside of homeassistant and just pushes recognized intents to it.
but there are huge overlaps
for example openwakeword came from Rhasspy raven somehow ? and a bunch of the other parts of the current homeassistant ecosystem previously were rhasspy parts
something like that i think
at least - if i am not mistaken.