@Bugsounet Sure! When I used the auto installer on my RPi3B+, running Raspbian Stretch (I list all these because maybe it’s OK on Buster, I do not know) the npm install created “node-v64-linux-arm-glibc” in the ~/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_library/ directory
I know this because I’m running MM with PM2, and the PM2 logs clearly stated that the plugin was looking for “electron-v3.0-linux-arm-glibc” at that location and could not find it.
This was a well-documented bug with the v2 install process, and the commands that fixed it were
npm install --save-dev electron-rebuild
These are run from the MMM-AssistantMk2 directory AND the MMM-Hotword directory. Those were easy!
As to the memory issue, I went back just now to check the pm2 logs for errors, and yes, I see these entries:
0|mm | mmap() failed: Cannot allocate memory
0|mm | Failed to create permanent mapping for memfd region with ID = 3774675295
0|mm | Ignoring received block reference with non-registered memfd ID = 3774675295
But I was not sure if they were related to the npm install issue or not. I thought they might be leftover from when the proper grpc files were not there, because, frankly, I know nothing about this stuff.
And thirdly, yes, I did read about the proper config for the v3 version, and everything seems to be fine there. The plugin loads fine, even listens to me, but simply does not process the commands and then kind of locks up. The rest of the mirror runs fine, but the voice command is no longer responsive.
I set up MMM-Buttons to trigger the Assistant as well, and that also works to set off the listener, with exactly the same result - no parsing of the voice command, the eventual “Can’t understand this” dialogue box, and unresponsive until restart.