Open GVDub opened 2 months ago
Looks like the wyoming-openwakeword service is failing to start. Can you run the ExecStart
command by itself in a terminal and see what it says?
This is what I get when I just use StartExec=filepath to wyoming-openwakeword then run systemctl status wyoming-wakeword.service:
wyoming-openwakeword.service - Wyoming openWakeWord Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2024-09-04 12:17:34 PDT; 1h 0min ago Duration: 6ms Process: 697 ExecStart=/home/gvdub/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400 (code=exited, status=203/EXEC) Main PID: 697 (code=exited, status=203/EXEC) CPU: 3ms
Sep 04 12:17:34 PiSatellite systemd[1]: wyoming-openwakeword.service: Scheduled restart job, restart counter is at 5. Sep 04 12:17:34 PiSatellite systemd[1]: Stopped wyoming-openwakeword.service - Wyoming openWakeWord. Sep 04 12:17:34 PiSatellite systemd[1]: wyoming-openwakeword.service: Start request repeated too quickly. Sep 04 12:17:34 PiSatellite systemd[1]: wyoming-openwakeword.service: Failed with result 'exit-code'. Sep 04 12:17:34 PiSatellite systemd[1]: Failed to start wyoming-openwakeword.service - Wyoming openWakeWord.
I had the same issue, deleted the wyoming-openwakeword directory and ran the tutorial again from the step where you git clone wyoming-openwakeword. Both services run now. BTW I forgot to install the Wyoming openwakeword AddOn in HomeAssistant when I tried first. Just mentioning it, because it was the only difference between the two install attempts, no idea if it had any influence on the install or reinstall.
This is what I get when I just use StartExec=filepath to wyoming-openwakeword then run systemctl status wyoming-wakeword.service:
wyoming-openwakeword.service - Wyoming openWakeWord Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2024-09-04 12:17:34 PDT; 1h 0min ago Duration: 6ms Process: 697 ExecStart=/home/gvdub/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400 (code=exited, status=203/EXEC) Main PID: 697 (code=exited, status=203/EXEC) CPU: 3ms
Sep 04 12:17:34 PiSatellite systemd[1]: wyoming-openwakeword.service: Scheduled restart job, restart counter is at 5. Sep 04 12:17:34 PiSatellite systemd[1]: Stopped wyoming-openwakeword.service - Wyoming openWakeWord. Sep 04 12:17:34 PiSatellite systemd[1]: wyoming-openwakeword.service: Start request repeated too quickly. Sep 04 12:17:34 PiSatellite systemd[1]: wyoming-openwakeword.service: Failed with result 'exit-code'. Sep 04 12:17:34 PiSatellite systemd[1]: Failed to start wyoming-openwakeword.service - Wyoming openWakeWord.
Please share your full openwakeword configuration from the .service, like when you edit it.
RPi Zero 2 W with Seeed Respeaker 2mic hat, followed the tutorial as closely as I could, and keep getting this error (bolded below). Any suggestions for how to fix? :
wyoming-satellite.service - Wyoming Satellite Loaded: loaded (/etc/systemd/system/wyoming-satellite.service; enabled; preset: enabled) Active: active (running) since Wed 2024-09-04 08:29:39 PDT; 3min 33s ago Main PID: 709 (python3) Tasks: 4 (limit: 174) CPU: 7.739s CGroup: /system.slice/wyoming-satellite.service ├─709 python3 /home/gvdub/wyoming-satellite/script/run --name "my satellite" --uri tcp://0.0.0.0:10700 --mic-command "arecord -D plughw:CARD=seeed2micvoicec,DEV=0 -r 16000 > ├─710 /home/gvdub/wyoming-satellite/.venv/bin/python3 -m wyoming_satellite --name "my satellite" --uri tcp://0.0.0.0:10700 --mic-command "arecord -D plughw:CARD=seeed2micvo> └─712 arecord -D plughw:CARD=seeed2micvoicec,DEV=0 -r 16000 -c 1 -f S16_LE -t raw
Sep 04 08:33:10 PiSatellite run[710]: sock = await self._connect_sock( Sep 04 08:33:10 PiSatellite run[710]: ^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 04 08:33:10 PiSatellite run[710]: File "/usr/lib/python3.11/asyncio/base_events.py", line 973, in _connect_sock Sep 04 08:33:10 PiSatellite run[710]: await self.sock_connect(sock, address) Sep 04 08:33:10 PiSatellite run[710]: File "/usr/lib/python3.11/asyncio/selector_events.py", line 634, in sock_connect Sep 04 08:33:10 PiSatellite run[710]: return await fut Sep 04 08:33:10 PiSatellite run[710]: ^^^^^^^^^ Sep 04 08:33:10 PiSatellite run[710]: File "/usr/lib/python3.11/asyncio/selector_events.py", line 674, in _sock_connect_cb Sep 04 08:33:10 PiSatellite run[710]: raise OSError(err, f'Connect call failed {address}') Sep 04 08:33:10 PiSatellite run[710]: ConnectionRefusedError: [Errno 111] Connect call failed ('127.0.0.1', 10400)
× wyoming-openwakeword.service - Wyoming openWakeWord Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Wed 2024-09-04 08:29:39 PDT; 3min 33s ago Duration: 11ms Process: 705 ExecStart=/home/gvdub/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400 (code=exited, status=203/EXEC) Main PID: 705 (code=exited, status=203/EXEC) CPU: 3ms
Sep 04 08:29:39 PiSatellite systemd[1]: wyoming-openwakeword.service: Scheduled restart job, restart counter is at 5. Sep 04 08:29:39 PiSatellite systemd[1]: Stopped wyoming-openwakeword.service - Wyoming openWakeWord. Sep 04 08:29:39 PiSatellite systemd[1]: wyoming-openwakeword.service: Start request repeated too quickly. Sep 04 08:29:39 PiSatellite systemd[1]: wyoming-openwakeword.service: Failed with result 'exit-code'. Sep 04 08:29:39 PiSatellite systemd[1]: Failed to start wyoming-openwakeword.service - Wyoming openWakeWord.
● 2mic_leds.service - 2Mic LEDs Loaded: loaded (/etc/systemd/system/2mic_leds.service; disabled; preset: enabled) Active: active (running) since Wed 2024-09-04 08:29:32 PDT; 3min 39s ago Main PID: 392 (python3) Tasks: 4 (limit: 174) CPU: 1.548s CGroup: /system.slice/2mic_leds.service └─392 /home/gvdub/wyoming-satellite/examples/.venv/bin/python3 2mic_service.py --uri tcp://0.0.0.0:10500
Sep 04 08:29:32 PiSatellite systemd[1]: Started 2mic_leds.service - 2Mic LEDs. Sep 04 08:29:36 PiSatellite python3[392]: INFO:root:Ready