Openwakeword installation failing on RPi Zero 2 64bit with Respeaker 2 Mic hat #157

c-sattler · 2024-04-19T13:05:43Z

I have Wyoming satellite successfully installed on one RPi Zero2 running 64bit lite RPi OS with Respeaker 2 Mic hat, but when following the same tutorial to install it on a second set it is now failing while running the script to get the tflite-runtime-nightly.

cd ~/wyoming-openwakeword
script/setup
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pip in ./.venv/lib/python3.9/site-packages (24.0)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: setuptools in ./.venv/lib/python3.9/site-packages (69.5.1)
Requirement already satisfied: wheel in ./.venv/lib/python3.9/site-packages (0.43.0)
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ProtocolError('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))': /simple/wheel/
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
ERROR: Could not find a version that satisfies the requirement tflite-runtime-nightly (from versions: none)
ERROR: No matching distribution found for tflite-runtime-nightly
Traceback (most recent call last):
File "/home/bedroomsatellite/wyoming-openwakeword/script/setup", line 26, in
subprocess.check_call(pip + ["install", "-r", str(_PROGRAM_DIR / "requirements.txt")])
File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/bedroomsatellite/wyoming-openwakeword/.venv/bin/python3', '-m', 'pip', 'install', '-r', '/home/bedroomsatellite/wyoming-openwakeword/requirements.txt']' returned non-zero exit status 1.

It's not finding tflite-runtime-nightly is the provided indexes.
I've tried this on both 4/18/24 and 4/19/24 in case there was an issue with the nightly rebuild of tflite-runtime-nightly, failed both days.

Mabe75 · 2024-04-19T13:17:43Z

Same here! My first install 3 days ago went fine. Today I got the same error as mentioned above.

CrystalCake · 2024-04-19T14:10:33Z

same probleme here.
Newly setup pi zero 2 64bit OS installed.

Dza-byte · 2024-04-19T14:40:53Z

me as well
pi 3b and 4 mic hat.

indoorwolf · 2024-04-19T20:31:30Z

i have the same problem with a zero 2 w 64bit lite

kdutton1964 · 2024-04-20T04:33:36Z

In openwakeword requirements.txt I changed...

tflite-runtime-nightly
wyoming==1.5.3

to

tflite-runtime
wyoming==1.5.3

*deleting -nightly part
This worked for me, I also performed a successful install few days ago. Went back to do fresh install and it failed.

don86nl · 2024-04-22T19:16:57Z

In openwakeword requirements.txt I changed... tflite-runtime-nightly wyoming==1.5.3

to

tflite-runtime wyoming==1.5.3 deleting -nightly

This worked for me, I also performed a successful install few days ago. Went back to do fresh install and it failed.

Thanks @kdutton1964 , this worked for me. To others who blindly copied the lines like me, including 'deleting -nightly' 😂, the lines in the file should be:

tflite-runtime
wyoming==1.5.3

c-sattler · 2024-04-22T22:05:25Z

Deleting the "-nightly" from the tflite release name also worked for me. Sent from Mailspring ***@***.***/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=cmVwbHkrQUVFTjJZV1lTSFc1QldTM0YzNFZKNE9FR0tNTUJFVkJOSEhJTVNLS1BZQHJlcGx5LmdpdGh1Yi5jb20%3D), the best free email app for work

…

On Apr 22 2024, at 2:17 pm, don86nl ***@***.***> wrote: > In openwakeword requirements.txt I changed... tflite-runtime-nightly wyoming==1.5.3 > to > tflite-runtime wyoming==1.5.3 deleting -nightly > This worked for me, I also performed a successful install few days ago. Went back to do fresh install and it failed. Thanks @kdutton1964 ***@***.***/1?redirect=https%3A%2F%2Fgithub.com%2Fkdutton1964&recipient=cmVwbHkrQUVFTjJZV1lTSFc1QldTM0YzNFZKNE9FR0tNTUJFVkJOSEhJTVNLS1BZQHJlcGx5LmdpdGh1Yi5jb20%3D) , this worked for me. To others who blindly copied the lines like me, including 'deleting -nightly' 😂, the lines in the file should be: tflite-runtime wyoming==1.5.3 — Reply to this email directly, view it on GitHub ***@***.***/2?redirect=https%3A%2F%2Fgithub.com%2Frhasspy%2Fwyoming-satellite%2Fissues%2F157%23issuecomment-2070722266&recipient=cmVwbHkrQUVFTjJZV1lTSFc1QldTM0YzNFZKNE9FR0tNTUJFVkJOSEhJTVNLS1BZQHJlcGx5LmdpdGh1Yi5jb20%3D), or unsubscribe ***@***.***/3?redirect=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEEN2YRFYYC3FHTY4NHD5YLY6VO4BAVCNFSM6AAAAABGPE5DCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZQG4ZDEMRWGY&recipient=cmVwbHkrQUVFTjJZV1lTSFc1QldTM0YzNFZKNE9FR0tNTUJFVkJOSEhJTVNLS1BZQHJlcGx5LmdpdGh1Yi5jb20%3D). You are receiving this because you authored the thread.

j5bart · 2024-04-29T12:35:58Z

Had the same issue, opened a PR in wyoming-openwakword project to hopefully have above resolved going forward.

jeremyfa55 · 2024-05-08T07:51:57Z

Hello,

I did the modification, but i still got the error :

 script/setup
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pip in ./.venv/lib/python3.11/site-packages (24.0)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: setuptools in ./.venv/lib/python3.11/site-packages (69.5.1)
Requirement already satisfied: wheel in ./.venv/lib/python3.11/site-packages (0.43.0)
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
ERROR: Could not find a version that satisfies the requirement tflite-runtime (from versions: none)
ERROR: No matching distribution found for tflite-runtime
Traceback (most recent call last):
  File "/home/jeremy/wyoming-openwakeword/script/setup", line 26, in <module>
    subprocess.check_call(pip + ["install", "-r", str(_PROGRAM_DIR / "requirements.txt")])
  File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/jeremy/wyoming-openwakeword/.venv/bin/python3', '-m', 'pip', 'install', '-r', '/home/jeremy/wyoming-openwakeword/requirements.txt']' returned non-zero exit status 1.

tannisroot · 2024-05-10T20:56:03Z

It seems that this is caused by tflite-runtime dropping support for Bullseye, as the package requires a newer glibc version.

niet16 · 2024-05-17T05:53:01Z

I am experiencing the same error. I couldn't get the open wakeword service to function properly after the adjustment proposed earlier.

strusic · 2024-05-19T08:51:33Z

I have same issue. After deleting -nightly part I ran script and it installs but when I prompt
sudo systemctl status wyoming-satellite.service wyoming-openwakeword.service
I have wyoming-satellite.service as active but wyoming-openwakeword.service is inactive (dead)

EDIT:
Okay so I managed to do this. I manually start service by:
sudo systemctl enable --now wyoming-openwakeword.service
and now both are working even after reboot

tannisroot · 2024-05-22T06:04:39Z

I've found that the non-nightly version seems to occasionally crash.
This can probably be workarounded with a change to the service to restart it when it dies, but I think a proper solution here is to switch to bookworm based Pi OS for which there is a wheel for -nightly.
I've been running my satellite on non-legacy Pi OS Lite and it works fine, just needed to install the respeaker driver for the 6.6 branch.

boehmr77 · 2024-05-28T00:04:53Z

I've found that the non-nightly version seems to occasionally crash. This can probably be workarounded with a change to the service to restart it when it dies, but I think a proper solution here is to switch to bookworm based Pi OS for which there is a wheel for -nightly. I've been running my satellite on non-legacy Pi OS Lite and it works fine, just needed to install the respeaker driver for the 6.6 branch.

Can you explain a bit more in detail how you installed the repseaker driver for the 6.6 branch? I'm having the same problem, but don't quite understand. Thanks.

tannisroot · 2024-05-28T17:54:02Z

I've found that the non-nightly version seems to occasionally crash. This can probably be workarounded with a change to the service to restart it when it dies, but I think a proper solution here is to switch to bookworm based Pi OS for which there is a wheel for -nightly. I've been running my satellite on non-legacy Pi OS Lite and it works fine, just needed to install the respeaker driver for the 6.6 branch.

Can you explain a bit more in detail how you installed the repseaker driver for the 6.6 branch? I'm having the same problem, but don't quite understand. Thanks.

Well first you need to have a Pi OS version (latest non-legacy) that ships with 6.6 kernel, and then you just follow the guide for 2mic as before. I PR-ed a change (which is merged) to the driver installation script that allows to install the driver on any supported kernel, so it should select the branch for 6.6 automatically without any intervention. Just make sure the local repo is up-to-date (so git pull origin master).
I should note that I only tested it with 2-Mic and not with 4 Mic board.

tannisroot · 2024-05-28T18:00:16Z

I've found that the non-nightly version seems to occasionally crash. This can probably be workarounded with a change to the service to restart it when it dies, but I think a proper solution here is to switch to bookworm based Pi OS for which there is a wheel for -nightly. I've been running my satellite on non-legacy Pi OS Lite and it works fine, just needed to install the respeaker driver for the 6.6 branch.

Can you explain a bit more in detail how you installed the repseaker driver for the 6.6 branch? I'm having the same problem, but don't quite understand. Thanks.

In case you need further help I would be happy to assist in Home Assistant discord server in #voice_assistants channel, my @ nickname is the same as here but the pfp is an owl figurine

boehmr77 · 2024-05-28T18:06:55Z

Thanks, I finally got everything running this morning. I used the Sker65 fork of rhasspy with your latest commit from last week. I think the real issue is cloning from the wyoming-openwakeword repository. Currently is you're using the Pi OS 64 Legacy Lite it has an issue with the tflite-nightly in the requirements.txt. Removing the nightly and re-running the script seemed to work this time. Although now I'm not able to get the LED service to work. Journal shows it's running but the Pi Hat LEDs don't work.

tannisroot · 2024-05-28T18:11:42Z

Thanks, I finally got everything running this morning. I used the Sker65 fork of rhasspy with your latest commit from last week. I think the real issue is cloning from the wyoming-openwakeword repository. Currently is you're using the Pi OS 64 Legacy Lite it has an issue with the tflite-nightly in the requirements.txt. Removing the nightly and re-running the script seemed to work this time. Although now I'm not able to get the LED service to work. Journal shows it's running but the Pi Hat LEDs don't work.

FYI I had bad luck with the non-nightly version of tflite, the openwakeword service would just crash after some time and not restart, bookworm non-legacy Pi OS Lite is so far a lot more stable for me.

tonyis49 · 2024-06-19T14:32:58Z

Hi all,
I am also having the same problem installing the openwakeword. I removed the -nightly from the requirements.txt as suggested and al least the install completed successfully. however I now have the following error:
AttributeError: _ARRAY_API not found
Jun 19 16:27:16 jarvis2 run[471]: ERROR:root:Unexpected error in wake word thread (hey_jarvis_v0.1)
Jun 19 16:27:16 jarvis2 run[471]: ImportError: numpy.core.multiarray failed to import
Jun 19 16:27:16 jarvis2 run[471]: The above exception was the direct cause of the following exception:
Jun 19 16:27:16 jarvis2 run[471]: Traceback (most recent call last):
Jun 19 16:27:16 jarvis2 run[471]: File "/home/tony/wyoming-openwakeword/wyoming_openwakeword/openwakeword.py", line 248, in ww_proc
Jun 19 16:27:16 jarvis2 run[471]: ww_model = tflite.Interpreter(model_path=str(ww_model_path), num_threads=1)
Jun 19 16:27:16 jarvis2 run[471]: File "/home/tony/wyoming-openwakeword/.venv/lib/python3.9/site-packages/tflite_runtime/interpreter.py", line 464, in init
Jun 19 16:27:16 jarvis2 run[471]: self._interpreter = _interpreter_wrapper.CreateWrapperFromFile(
Jun 19 16:27:16 jarvis2 run[471]: SystemError: <built-in method CreateWrapperFromFile of PyCapsule object at 0x7f963389c0> returned a result with an error set

any help would be be gratefully appreciated

Shpyda · 2024-06-20T13:48:16Z

I've found that the non-nightly version seems to occasionally crash. This can probably be workarounded with a change to the service to restart it when it dies, but I think a proper solution here is to switch to bookworm based Pi OS for which there is a wheel for -nightly. I've been running my satellite on non-legacy Pi OS Lite and it works fine, just needed to install the respeaker driver for the 6.6 branch.

I switched to Bookworm and followed the tutorial but am continuously getting the following error for the OpenWakeWord service. How were you able to get around this?:

ImportError: numpy.core.multiarray failed to import
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/pi/wyoming-openwakeword/wyoming_openwakeword/openwakeword.py", line 248, in ww_proc
ww_model = tflite.Interpreter(model_path=str(ww_model_path), num_threads=1)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/pi/wyoming-openwakeword/.venv/lib/python3.11/site-packages/tflite_runtime/interpreter.py", line 473, in init
self._interpreter = _interpreter_wrapper.CreateWrapperFromFile(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SystemError: <built-in method CreateWrapperFromFile of PyCapsule object at 0x7f92fdadf0> returned a result with an exception set
A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.0.0 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.
Traceback (most recent call last): File "/usr/lib/python3.11/threading.py", line 995, in _bootstrap
self._bootstrap_inner()
File "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
self.run()
File "/usr/lib/python3.11/threading.py", line 975, in run
self._target(*self._args, **self._kwargs)
File "/home/pi/wyoming-openwakeword/wyoming_openwakeword/openwakeword.py", line 248, in ww_proc
ww_model = tflite.Interpreter(model_path=str(ww_model_path), num_threads=1)
File "/home/pi/wyoming-openwakeword/.venv/lib/python3.11/site-packages/tflite_runtime/interpreter.py", line 473, in init
self._interpreter = _interpreter_wrapper.CreateWrapperFromFile(
AttributeError: _ARRAY_API not found
ERROR:root:Unexpected error in wake word thread (hey_jarvis_v0.1)

P4uLT · 2024-06-20T22:46:41Z

Hi.

I managed to get it to start

Fix is here : DeepLabCut/DeepLabCut#2624 (comment)

I ran this command .venv/bin/pip3 install "numpy<2"


● wyoming-openwakeword.service - Wyoming openWakeWord
     Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; disabled; vendor preset: enabled)
     Active: active (running) since Thu 2024-06-20 22:45:12 UTC; 2s ago
   Main PID: 2318 (python3)
      Tasks: 7 (limit: 191)
        CPU: 2.059s
     CGroup: /system.slice/wyoming-openwakeword.service
             ├─2318 python3 /home/pi/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400
             └─2321 /home/p4ult/wyoming-openwakeword/.venv/bin/python3 -m wyoming_openwakeword --uri tcp://127.0.0.1:10400

Jun 20 22:45:12 jarvis systemd[1]: Started Wyoming openWakeWord.
Jun 20 22:45:14 jarvis run[2321]: INFO:root:Ready

Scrazzled · 2024-06-22T22:19:24Z

Hi.

I managed to get it to start

Fix is here : DeepLabCut/DeepLabCut#2624 (comment)

I ran this command .venv/bin/pip3 install "numpy<2"


● wyoming-openwakeword.service - Wyoming openWakeWord
     Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; disabled; vendor preset: enabled)
     Active: active (running) since Thu 2024-06-20 22:45:12 UTC; 2s ago
   Main PID: 2318 (python3)
      Tasks: 7 (limit: 191)
        CPU: 2.059s
     CGroup: /system.slice/wyoming-openwakeword.service
             ├─2318 python3 /home/pi/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400
             └─2321 /home/p4ult/wyoming-openwakeword/.venv/bin/python3 -m wyoming_openwakeword --uri tcp://127.0.0.1:10400

Jun 20 22:45:12 jarvis systemd[1]: Started Wyoming openWakeWord.
Jun 20 22:45:14 jarvis run[2321]: INFO:root:Ready

I did the same and it didn't resolve the error for me.

dazemc · 2024-06-23T15:44:54Z

I did the same and it didn't resolve the error for me.

It depends on which distro you are on. There is no nightly build compatible on bullseye so you will need to remove it, with bookworm it's just numpy, requirements.txt for bullseye should be;

tflite-runtime
wyoming==1.5.3
numpy<2

Scrazzled · 2024-06-23T19:34:24Z

It depends on which distro you are on. There is no nightly build compatible on bullseye so you will need to remove it, with bookworm it's just numpy, requirements.txt for bullseye should be;

tflite-runtime wyoming==1.5.3 numpy<2

Thanks, I'll try again later when I've replaced my hat... mine stopped communicating with the Pi so I wiped the sd and started working on a different project. I'm unsure what caused the hardware failure.

owingst · 2024-06-23T19:52:03Z

@dazemc

Still no luck with wyoming-openwakeword. Running on Raspberry Pi zero 2 W. I installed Raspberry Pi OS (Legacy, 64 bit) Lite. Successfully installed numpy-2.0.0 tflite-runtime-2.13.0.

If the issue is Numpy, do I need to down grade to 1.19.5 or so? I noticed you mentioned Numpy<2....

wyoming-satellite runs with no issues.

pi@pi0:~ $ hostnamectl
Static hostname: pi0
Icon name: computer
Machine ID: a24ead6923d842aebe9a6586904f1157
Boot ID: 3c918fe125e24df5baa7443d98d1f582
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
Architecture: arm64

wyoming-openwakeword.service - Wyoming openWakeWord
Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; disabled; vendor preset: enabled)
Active: active (running) since Sun 2024-06-23 14:39:12 CDT; 21s ago
Main PID: 1107 (python3)
Tasks: 5 (limit: 191)
CPU: 2.698s
CGroup: /system.slice/wyoming-openwakeword.service
├─1107 python3 /home/pi/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400
└─1109 /home/pi/wyoming-openwakeword/.venv/bin/python3 -m wyoming_openwakeword --uri tcp://127.0.0.1:10400

Jun 23 14:39:15 pi0 run[1109]: AttributeError: _ARRAY_API not found
Jun 23 14:39:15 pi0 run[1109]: ERROR:root:Unexpected error in wake word thread (alexa_v0.1)
Jun 23 14:39:15 pi0 run[1109]: ImportError: numpy.core.multiarray failed to import
Jun 23 14:39:15 pi0 run[1109]: The above exception was the direct cause of the following exception:
Jun 23 14:39:15 pi0 run[1109]: Traceback (most recent call last):
Jun 23 14:39:15 pi0 run[1109]: File "/home/pi/wyoming-openwakeword/wyoming_openwakeword/openwakeword.py", line 248, in ww_proc
Jun 23 14:39:15 pi0 run[1109]: ww_model = tflite.Interpreter(model_path=str(ww_model_path), num_threads=1)
Jun 23 14:39:15 pi0 run[1109]: File "/home/pi/wyoming-openwakeword/.venv/lib/python3.9/site-packages/tflite_runtime/interpreter.py", line 464, in init
Jun 23 14:39:15 pi0 run[1109]: self._interpreter = _interpreter_wrapper.CreateWrapperFromFile(
Jun 23 14:39:15 pi0 run[1109]: SystemError: <built-in method CreateWrapperFromFile of PyCapsule object at 0x7f901a3270> returned a result with an error set

tannisroot · 2024-06-23T19:58:11Z

Still no luck with wyoming-openwakeword. Running on Raspberry Pi zero 2 W. I installed Raspberry Pi OS (Legacy, 64 bit) Lite. Successfully installed numpy-2.0.0 tflite-runtime-2.13.0.

If the issue is Numpy, do I need to down grade to 1.19.5 or so? I noticed you mentioned Numpy<2....

numpy<2 means the version needs to be less than/older than 2, so 2.0.0 won't work.
Also, you won't get good experience under bullseye (tflite-runtime 2.13 is prone to crashing, there is a reason the project was installing the nightly), bookworm is recommended. If you are using the respeaker hat, a branch with some additional changes to workaround a driver installation issue is needed, see #170 (comment)

owingst · 2024-06-23T20:22:35Z

I wasn't aware that Bookworm was supported on raspberry pi Zero 2 W. I will give it a shot. Thanks!

qJake · 2024-06-23T23:31:33Z

Hi.

I managed to get it to start

Fix is here : DeepLabCut/DeepLabCut#2624 (comment)

I ran this command .venv/bin/pip3 install "numpy<2"


● wyoming-openwakeword.service - Wyoming openWakeWord
     Loaded: loaded (/etc/systemd/system/wyoming-openwakeword.service; disabled; vendor preset: enabled)
     Active: active (running) since Thu 2024-06-20 22:45:12 UTC; 2s ago
   Main PID: 2318 (python3)
      Tasks: 7 (limit: 191)
        CPU: 2.059s
     CGroup: /system.slice/wyoming-openwakeword.service
             ├─2318 python3 /home/pi/wyoming-openwakeword/script/run --uri tcp://127.0.0.1:10400
             └─2321 /home/p4ult/wyoming-openwakeword/.venv/bin/python3 -m wyoming_openwakeword --uri tcp://127.0.0.1:10400

Jun 20 22:45:12 jarvis systemd[1]: Started Wyoming openWakeWord.
Jun 20 22:45:14 jarvis run[2321]: INFO:root:Ready

This worked for me, running on an RPi 4 with:

Linux hostname 6.6.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux

Thanks!

synesthesiam · 2024-06-26T18:37:06Z

The wyoming-openwakeword repo has been updated to fix some dependency issues for now. Ultimately, I would like to switch to using the main openWakeWord project directly.

j5bart mentioned this issue Apr 29, 2024

Depend on tflite-runtime instead of tflite-runtime-nightly rhasspy/wyoming-openwakeword#20

Merged

tannisroot mentioned this issue May 22, 2024

Change docs to suggest bookworm based Pi OS #167

Merged

tannisroot mentioned this issue Jun 22, 2024

Specify numpy version to be older than 2 rhasspy/wyoming-openwakeword#25

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Openwakeword installation failing on RPi Zero 2 64bit with Respeaker 2 Mic hat #157

Openwakeword installation failing on RPi Zero 2 64bit with Respeaker 2 Mic hat #157

c-sattler commented Apr 19, 2024

Mabe75 commented Apr 19, 2024

CrystalCake commented Apr 19, 2024

Dza-byte commented Apr 19, 2024

indoorwolf commented Apr 19, 2024

kdutton1964 commented Apr 20, 2024 •

edited

Loading

don86nl commented Apr 22, 2024

c-sattler commented Apr 22, 2024 via email

j5bart commented Apr 29, 2024

jeremyfa55 commented May 8, 2024 •

edited

Loading

tannisroot commented May 10, 2024

niet16 commented May 17, 2024

strusic commented May 19, 2024 •

edited

Loading

tannisroot commented May 22, 2024

boehmr77 commented May 28, 2024

tannisroot commented May 28, 2024 •

edited

Loading

tannisroot commented May 28, 2024

boehmr77 commented May 28, 2024

tannisroot commented May 28, 2024 •

edited

Loading

tonyis49 commented Jun 19, 2024

Shpyda commented Jun 20, 2024

P4uLT commented Jun 20, 2024 •

edited

Loading

Scrazzled commented Jun 22, 2024

dazemc commented Jun 23, 2024

Scrazzled commented Jun 23, 2024

owingst commented Jun 23, 2024

tannisroot commented Jun 23, 2024

owingst commented Jun 23, 2024

qJake commented Jun 23, 2024

synesthesiam commented Jun 26, 2024

Openwakeword installation failing on RPi Zero 2 64bit with Respeaker 2 Mic hat #157

Openwakeword installation failing on RPi Zero 2 64bit with Respeaker 2 Mic hat #157

Comments

c-sattler commented Apr 19, 2024

Mabe75 commented Apr 19, 2024

CrystalCake commented Apr 19, 2024

Dza-byte commented Apr 19, 2024

indoorwolf commented Apr 19, 2024

kdutton1964 commented Apr 20, 2024 • edited Loading

don86nl commented Apr 22, 2024

c-sattler commented Apr 22, 2024 via email

j5bart commented Apr 29, 2024

jeremyfa55 commented May 8, 2024 • edited Loading

tannisroot commented May 10, 2024

niet16 commented May 17, 2024

strusic commented May 19, 2024 • edited Loading

tannisroot commented May 22, 2024

boehmr77 commented May 28, 2024

tannisroot commented May 28, 2024 • edited Loading

tannisroot commented May 28, 2024

boehmr77 commented May 28, 2024

tannisroot commented May 28, 2024 • edited Loading

tonyis49 commented Jun 19, 2024

Shpyda commented Jun 20, 2024

P4uLT commented Jun 20, 2024 • edited Loading

Scrazzled commented Jun 22, 2024

dazemc commented Jun 23, 2024

Scrazzled commented Jun 23, 2024

owingst commented Jun 23, 2024

tannisroot commented Jun 23, 2024

owingst commented Jun 23, 2024

qJake commented Jun 23, 2024

synesthesiam commented Jun 26, 2024

kdutton1964 commented Apr 20, 2024 •

edited

Loading

jeremyfa55 commented May 8, 2024 •

edited

Loading

strusic commented May 19, 2024 •

edited

Loading

tannisroot commented May 28, 2024 •

edited

Loading

tannisroot commented May 28, 2024 •

edited

Loading

P4uLT commented Jun 20, 2024 •

edited

Loading