Assist Microphone - wake word detected only once

Configuration Voice Assistant
1

Hi,

I’m trying to use Creative Sound Blaster AXX SBX 8 with Assist Microphone addon. When I start the addon wakeword is properly detected, assistant responds with configured voice, but then wakeword is not detected anymore. I need to restart Assist Microphone addon to make it work again. Here are the logs:

s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service assist_microphone: starting
s6-rc: info: service assist_microphone successfully started
s6-rc: info: service discovery: starting
DEBUG:root:Namespace(mic_uri=None, mic_command='arecord -r 16000 -c 1 -f S16_LE -t raw', mic_command_rate=16000, mic_command_width=2, mic_command_channels=1, mic_command_samples_per_chunk=1024, mic_volume_multiplier=1.0, mic_noise_suppression=0, mic_auto_gain=0, snd_uri=None, snd_command='aplay -r 16000 -c 1 -f S16_LE -t raw', snd_command_rate=16000, snd_command_width=2, snd_command_channels=1, snd_volume_multiplier=1.0, wake_uri=None, wake_word_name=[], wake_command=None, wake_command_rate=16000, wake_command_width=2, wake_command_channels=1, vad=False, vad_threshold=0.5, vad_trigger_level=1, vad_buffer_seconds=2, vad_wake_word_timeout=5.0, event_uri=None, startup_command=None, detect_command=None, detection_command=None, transcript_command=None, stt_start_command=None, stt_stop_command=None, synthesize_command=None, tts_start_command=None, tts_stop_command=None, streaming_start_command=None, streaming_stop_command=None, error_command=None, awake_wav='/usr/src/sounds/awake.wav', done_wav='/usr/src/sounds/done.wav', uri='tcp://0.0.0.0:10700', name='assist microphone', area=None, no_zeroconf=True, zeroconf_name=None, zeroconf_host=None, debug=True)
INFO:root:Ready
DEBUG:root:Connecting to mic service: ['arecord', '-r', '16000', '-c', '1', '-f', 'S16_LE', '-t', 'raw']
DEBUG:root:Connecting to snd service: ['aplay', '-r', '16000', '-c', '1', '-f', 'S16_LE', '-t', 'raw']
INFO:root:Connected to services
DEBUG:root:Connected to mic service
Recording raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
[16:39:50] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
DEBUG:root:Server set: 250287718150361
INFO:root:Streaming audio
DEBUG:root:Wake word detected
DEBUG:root:Connected to snd service
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
DEBUG:root:Event(type='transcript', data={'text': ' Wyłącz światło w pokoju.'}, payload=None)
INFO:root:Streaming audio
DEBUG:root:Connected to snd service
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono
DEBUG:root:Event(type='synthesize', data={'text': 'Zrobione', 'voice': {'name': 'pl_PL-gosia-medium'}}, payload=None)
DEBUG:root:Connected to snd service
Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 16000 Hz, Mono

It looks like it does not restart audio stream to openWakeWord. Any suggestions?

1 Like
2

I am having the same issue with the 2024.2 and 2024.2.1 versions. Killing and restarting the Assist Microphone allows it to work one additional time. I rolled back to the latest January version of core and I am back in operation.

1 Like
3

Unfortunately i have the same issue with v2024.2.1 and I just started to use the Assist Microphone. No idea if it worked properly before. Should this bug be reported then?

4

I have the same problem on the latest version! My microphone is razer seiren mini usb, wake word is recognized for the first time, but after that it is no longer recognized…
When I restart the assist microphone, the problem is solved and it stops again after the first wake word! :slight_smile:

5

hi,
exact same behaviour here with latest 2024.02 and tonor tm20 USB mic
any hints ?
cheeerz from vienna

6

im getting the same thing… very frustrating because this is the first time i set up a local mic, though im happy im not the only one, have you figured out a solution?

7

Same thing. Restarting the Add On (which is not fast) is required after each trigger. It’s soooo close :sob::sob::sob:

Github thread: Assist Microphone - wake word detected only once · Issue #3464 · home-assistant/addons · GitHub

8

Yea i actually created this automation which has been working but like you said isnt fast and got to wait a bit, but its honestly not to bad lol

alias: Reset Voice Assistant
description: “”
trigger:

  • type: turned_on
    platform: device
    device_id: (your assist mic)
    entity_id: (your assist mic)
    domain: binary_sensor
  • type: turned_off
    platform: device
    device_id: (your assist mic)
    entity_id: (your assist mic)
    domain: binary_sensor
    condition:
    action:
  • delay:
    hours: 0
    minutes: 0
    seconds: 15
    milliseconds: 0
  • service: hassio.addon_restart
    metadata: {}
    data:
    addon: core_assist_microphone
    mode: single
9

That automation does not work, I tried something like this:

alias: Reset Voice Assistant
description: ""
trigger:
  - type: turned_on
    platform: device
    device_id: (your assist mic)
    entity_id: (your assist mic)
    domain: binary_sensor
    for:
      hours: 0
      minutes: 0
      seconds: 15
condition: []
action:
  - service: hassio.addon_restart
    data:
      addon: core_assist_microphone
mode: single

But restarting the addon does not seem to bring my M5 ATOM ECHO back to life :frowning:

10

The problem was in piper, not the M5 ATOM ECHO, although it also gets stuck from time to time, it’s not in every call, and disabling does not fix that, need to unplug and plug it again :disappointed: