Skip to content
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

Assist microphone does not work with USB conference device #3881

Open
bithajcsar opened this issue Jan 3, 2025 · 2 comments
Open

Assist microphone does not work with USB conference device #3881

bithajcsar opened this issue Jan 3, 2025 · 2 comments

Comments

@bithajcsar
Copy link

bithajcsar commented Jan 3, 2025

Describe the issue you are experiencing

Although everything seems to be set up correctly, the speakerphone does not react to the wake word. The Wyoming device log also not showing any activity.

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which add-on are you reporting an issue with?

Whisper

What is the version of the add-on?

Assist Microphone 1.2.0; Whisper 2.4.0

Steps to reproduce the issue

1.Intall "Assist Microphone" add-on
2.Plug in the speakerphone (Y11 - Chinese one proved to work with other systems)
3.Set up the discovered Assist device
...

System Health information

System Information

version core-2025.1.0
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.1
os_name Linux
os_version 6.6.62-haos-raspi
arch aarch64
timezone Europe/Budapest
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.1
Stage running
Available Repositories 1550
Downloaded Repositories 23
Home Assistant Cloud
logged_in true
subscription_expiration 2025. február 25. 01:00
relayer_connected true
relayer_region eu-central-1
remote_enabled false
remote_connected false
alexa_enabled false
google_enabled false
cloud_ice_servers_enabled true
remote_server eu-central-1-16.ui.nabu.casa
certificate_status ready
instance_id fa508cf941c24a45a7f83e8dcc876b53
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 14.1
update_channel stable
supervisor_version supervisor-2024.12.3
agent_version 1.6.0
docker_version 27.2.0
disk_total 116.7 GB
disk_used 25.0 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization
board rpi4-64
supervisor_api ok
version_api ok
installed_addons Samba share (12.3.2), Studio Code Server (5.18.0), Terminal & SSH (9.16.0), Grafana (10.2.2), InfluxDB (5.0.1), Let's Encrypt (5.2.10), Mosquitto broker (6.4.1), Piper (1.5.2), openWakeWord (1.10.0), ESPHome Device Builder (2024.12.2), Whisper (2.4.0), go2rtc (1.9.8), Assist Microphone (1.2.0)
Dashboards
dashboards 3
resources 13
views 21
mode storage
Recorder
oldest_recorder_run 2024. december 20. 20:47
current_recorder_run 2025. január 3. 21:15
estimated_db_size 5108.99 MiB
database_engine sqlite
database_version 3.47.1
Sonoff
version 3.8.1 (ffa7e22)
cloud_online 3 / 3
local_online 0 / 0
Spotify
api_endpoint_reachable ok
Xiaomi Miot Auto
component_version 1.0.8
can_reach_server ok
can_reach_spec ok
logged_accounts 1
total_devices 13

Anything in the Supervisor logs that might be useful for us?

No response

Anything in the add-on logs that might be useful for us?

Log messages in the log of the "Assist Microphone" add-on


WARNING:root:Did not receive ping response within timeout
DEBUG:root:Server disconnected
INFO:root:Disconnected from server
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='wyoming event handler' coro=<AsyncEventHandler.run() done, defined at /usr/local/lib/python3.11/dist-packages/wyoming/server.py:31> exception=ConnectionResetError(104, 'Connection reset by peer')>
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/dist-packages/wyoming/server.py", line 37, in run
    event = await async_read_event(self.reader)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/wyoming/event.py", line 79, in async_read_event
    json_line = await reader.readline()
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/streams.py", line 545, in readline
    line = await self.readuntil(sep)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/asyncio/streams.py", line 637, in readuntil
    await self._wait_for_data('readuntil')
  File "/usr/lib/python3.11/asyncio/streams.py", line 522, in _wait_for_data
    await self._waiter
  File "/usr/lib/python3.11/asyncio/selector_events.py", line 995, in _read_ready__data_received
    data = self._sock.recv(self.max_size)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionResetError: [Errno 104] Connection reset by peer
DEBUG:root:Server set: 6568423413386
INFO:root:Connected to server
INFO:root:Streaming audio
DEBUG:root:Event(type='run-pipeline', data={'start_stage': 'wake', 'end_stage': 'tts', 'restart_on_end': True, 'snd_format': {'rate': 16000, 'width': 2, 'channels': 1}}, payload=None)
DEBUG:root:Ping enabled

Additional information

No response

@bithajcsar
Copy link
Author

[core-ssh ~]$ ha audio info
audio:
application:

  • addon: core_assist_microphone
    index: 5
    mute: false
    name: ALSA plug-in [aplay]
    stream_index: 1
    stream_type: input
    volume: 1
    card:
  • driver: module-alsa-card.c
    index: 0
    name: alsa_card.usb-MV-SILICON_Y11_20220111-00
    profiles:
    • active: false
      description: Analog Stereo Input
      name: input:analog-stereo
    • active: false
      description: Digital Stereo (IEC958) Input
      name: input:iec958-stereo
    • active: false
      description: Analog Stereo Output
      name: output:analog-stereo
    • active: true
      description: Analog Stereo Duplex
      name: output:analog-stereo+input:analog-stereo
    • active: false
      description: Analog Stereo Output + Digital Stereo (IEC958) Input
      name: output:analog-stereo+input:iec958-stereo
    • active: false
      description: Digital Stereo (IEC958) Output
      name: output:iec958-stereo
    • active: false
      description: Digital Stereo (IEC958) Output + Analog Stereo Input
      name: output:iec958-stereo+input:analog-stereo
    • active: false
      description: Digital Stereo Duplex (IEC958)
      name: output:iec958-stereo+input:iec958-stereo
    • active: false
      description: "Off"
      name: "off"
  • driver: module-alsa-card.c
    index: 1
    name: alsa_card.platform-bcm2835_audio
    profiles:
    • active: true
      description: Stereo Output
      name: output:stereo-fallback
    • active: false
      description: "Off"
      name: "off"
      input:
  • applications:
    • addon: core_assist_microphone
      index: 5
      mute: false
      name: ALSA plug-in [aplay]
      stream_index: 1
      stream_type: input
      volume: 1
      card: 0
      default: true
      description: Y11 Analog Stereo
      index: 1
      mute: false
      name: alsa_input.usb-MV-SILICON_Y11_20220111-00.analog-stereo
      volume: 0.541168212890625
      output:
  • applications: []
    card: 0
    default: false
    description: Y11 Analog Stereo
    index: 0
    mute: false
    name: alsa_output.usb-MV-SILICON_Y11_20220111-00.analog-stereo
    volume: 0.541168212890625
  • applications: []
    card: 1
    default: true
    description: Built-in Audio Stereo
    index: 1
    mute: false
    name: alsa_output.platform-bcm2835_audio.stereo-fallback
    volume: 0.857696533203125
    host: 172.30.32.4
    update_available: false
    version: 2023.12.0
    version_latest: 2023.12.0

@bithajcsar
Copy link
Author

It seems that the problem is deeper, in the sound subsystem. The "ha audio log" shows:

s6-rc: info: service s6rc-oneshot-runner: starting
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
cont-init: info: running /etc/cont-init.d/filesystem.sh
cont-init: info: /etc/cont-init.d/filesystem.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service alsa: starting
s6-rc: info: service alsa successfully started
s6-rc: info: service alsa-init: starting
[21:23:36] INFO: Adjust ALSA mixer settings for /dev/snd/controlC0
[21:23:38] INFO: Adjust ALSA mixer settings for /dev/snd/controlC1
s6-rc: info: service alsa-init successfully started
s6-rc: info: service pulseaudio: starting
W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card1: No such file or directory
W: [pulseaudio] module-udev-detect.c: Failed to open /proc/asound/card0: No such file or directory
s6-rc: info: service pulseaudio successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant