We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Respeakerd seems to be working, but when I test with a client application I am unable to get any response. This is what I see in my terminal:
pi@raspberrypi:~/respeaker/respeakerd/clients/Python $ sudo service respeakerd status ● respeakerd.service - ReSpeaker Server Loaded: loaded (/lib/systemd/system/respeakerd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-08-23 21:36:35 PDT; 40s ago Main PID: 422 (respeakerd_safe) CGroup: /system.slice/respeakerd.service ├─ 422 /bin/bash /usr/bin/respeakerd_safe └─1047 /usr/bin/respeakerd --source=alsa_input.platform-soc_sound.seeed-8ch Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: snips_sensitivity: 0.5 Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: source: alsa_input.platform-soc_sound.seeed-8ch Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: agc_level: -3 Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: debug: 0 Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: enable_wav_log: 0 Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: ref_channel: 6 Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: fifo_file: /tmp/music.input Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: dynamic_doa: 0 Aug 23 21:36:44 raspberrypi respeakerd_safe[422]: ========================================================== Aug 23 21:36:45 raspberrypi respeakerd_safe[422]: now waiting for client connections ... pi@raspberrypi:~/respeaker/respeakerd/clients/Python $ python demo_respeaker_v2_vep_alexa_with_light.py INFO:respeakerd_client:Start to connect to the socket: /tmp/respeakerd.sock ... INFO:respeakerd_client:Connected to socket DEBUG:hyper.http20.connection:Selected NPN protocol: h2 DEBUG:hyper.http20.connection:recv for stream 0 with set([]) already present INFO:hyper.http20.connection:Received unhandled event <RemoteSettingsChanged changed_settings:{ChangedSetting(setting=SettingCodes.MAX_CONCURRENT_STREAMS, original_value=None, new_value=100), ChangedSetting(setting=SettingCodes.INITIAL_WINDOW_SIZE, original_value=65535, new_value=2147483647), ChangedSetting(setting=SettingCodes._max_header_list_size, original_value=None, new_value=40960)}> INFO:hyper.http20.connection:Received unhandled event <WindowUpdated stream_id:0, delta:2147418112> DEBUG:hyper.http20.connection:recv for stream 1 with set([]) already present INFO:hyper.http20.connection:Received unhandled event <SettingsAcknowledged changed_settings:{ChangedSetting(setting=SettingCodes.ENABLE_PUSH, original_value=1, new_value=0)}> INFO:hyper.http20.connection:Received unhandled event <SettingsAcknowledged changed_settings:{}> DEBUG:hyper.http20.connection:recv for stream 1 with set([]) already present INFO:hyper.http20.connection:Received unhandled event <PriorityUpdated stream_id:1, weight:16, depends_on:0, exclusive:False> INFO:avs.alexa:wait for response DEBUG:hyper.http20.connection:recv for stream 3 with set([1]) already present INFO:hyper.http20.connection:Received unhandled event <PriorityUpdated stream_id:3, weight:16, depends_on:0, exclusive:False> INFO:avs.alexa:status code: 204 ===== on_ready =====
Do you have any tips on how I can troubleshoot this? I am able to verify audio using alexa-audio-check.
The text was updated successfully, but these errors were encountered:
@wmturner Hello, did you found any solution to your problem ? Also get no result...
Sorry, something went wrong.
No branches or pull requests
Respeakerd seems to be working, but when I test with a client application I am unable to get any response. This is what I see in my terminal:
Do you have any tips on how I can troubleshoot this? I am able to verify audio using alexa-audio-check.
The text was updated successfully, but these errors were encountered: