#Weak word not working
restive skiff
Ok it is constantly repeating the following in the logs
[17:07:02][D][voice_assistant:529]: Event Type: 9
[17:07:19][D][voice_assistant:529]: Event Type: 0
[17:07:19][D][voice_assistant:529]: Event Type: 2
[17:07:19][D][voice_assistant:619]: Assist Pipeline ended
[17:07:19][D][voice_assistant:422]: State changed from STREAMING_MICROPHONE to WAIT_FOR_VAD
[17:07:19][D][voice_assistant:428]: Desired state set to WAITING_FOR_VAD
[17:07:19][D][voice_assistant:176]: Waiting for speech...
[17:07:19][D][voice_assistant:422]: State changed from WAIT_FOR_VAD to WAITING_FOR_VAD
[17:07:19][D][voice_assistant:189]: VAD detected speech
[17:07:19][D][voice_assistant:422]: State changed from WAITING_FOR_VAD to START_PIPELINE
[17:07:19][D][voice_assistant:428]: Desired state set to STREAMING_MICROPHONE
[17:07:19][D][voice_assistant:206]: Requesting start...
[17:07:19][D][voice_assistant:422]: State changed from START_PIPELINE to STARTING_PIPELINE
[17:07:19][D][light:036]: 'M5Stack Atom Echo Mars' Setting:
[17:07:19][D][light:051]: Brightness: 60%
[17:07:19][D][light:059]: Red: 100%, Green: 89%, Blue: 71%
when it doesn't work
keen pivot
ok ... and if you keep watching the logs, when it fails ... do the logs also stop scrolling ? and if so what are the last few lines?
restive skiff
Ok I'm seeing this one
[17:04:14][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:14][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:14][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
[17:04:15][D][voice_assistant:357]: Speaker buffer full, trying again next loop
hmmm no thats also not the reasong I will fiddle a bit with the wakeword and logs and will try to find a reproducable error
keen pivot
did you say command in quick succession?
ive done quite a bit of testing with these. and issuing about 4 commands one after the other leads to the buffer full spamming of logs. if you leave more of a gap between command this doesnt occur 🤷♂️
restive skiff
Hmm no. I've only done one command (light on/off) and wait untill the blue light is gone.
And after that I try "OK Nabu" again
And the wakeword starts failing after recognizing it succesfully two times
The normal "command" gets recognized correctly 99% of the time.
(Ok I must admit that I have to learn the commands since I'm normally a Google Assistant user and this can handle mostly everything you throw at it :-))
keen pivot
this will get there , one day! lol but in it's infancy, there is also an HA issue that causes the pipeline to stop and then commands no longer are acted up on and the device in effect stops listening. this may be related in your case.
i believe this is fixed and will be released in the next update. what are you using for your tts
restive skiff
Homeassistant Cloud in both directions 🙂
So TTS and STT
And openwakeword as a normal Addon in my HA instance
In the Openwakeword logs I can see this repeating
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1452915376037909
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1452915376037909
DEBUG:wyoming_openwakeword.handler:Client connected: 1452947461167884
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1452947461167884
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1452947461167884
DEBUG:wyoming_openwakeword.handler:Client connected: 1452979544187599
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1452979544187599
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1452979544187599
DEBUG:wyoming_openwakeword.handler:Client connected: 1452992591971081
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1452992591971081
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1452992591971081
DEBUG:wyoming_openwakeword.handler:Client connected: 1453011625696208
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1453011625696208
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1453011625696208
DEBUG:wyoming_openwakeword.handler:Client connected: 1453043729538877
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1453043729538877
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1453043729538877
DEBUG:wyoming_openwakeword.handler:Client connected: 1453075798343966
DEBUG:wyoming_openwakeword.handler:Sent info to client: 1453075798343966
DEBUG:wyoming_openwakeword.handler:Client disconnected: 1453075798343966
HA Cloud is usually the one that just works ! dang! I would look into the HA side of things as in esscence the echo appears to be ok ... the speaker buffer thing can also be caused by the stream coning from HA
inner sparrow
I have the same issue on my echo;s. have to presss the button on it or turn the wake word on/off in the lovelace of the device.
There is also this thread on github: https://github.com/esphome/issues/issues/5038