hi, I am facing this same. If you have found any solution please let me know

@sdetweil Okay, would gladly like to tell that this did get the errors but it worked even with them. I didn’t knew until now that its fine to get those errors as no one mentions them anywhere in the scripts. Now the one thing is that the alexa only listens once and then stops listening to hotword. My mic is working and I have checked that. Speakers are working, I read somewhere about the electron and Chrome issue not sure if that would be the reason. But if that is then I will try, if that doesn’t work ill ask.

Thank you for the help and support

@sdetweil how should I run the script? I tried the bash c but that didnt worked so did everything from script manually.
I will run the script exactly as you say and then will show you result if thats ok. also please let me know in which directory should I run the script.

@sdetweil now I really dont know what else I have to follow, you can see each and every step I did, I literally copy pasted all the commands as they are. in the same order and directories, I havent included the first few steps mentioned as they get executed every time. I have posted every step which has got errors.

@sdetweil yes I tried, but snowboy not getting installed. here is the errors

if that would be helpful for you to understand what is actually happening. sorry for the file being very long and tiring.

@gelaw no it didn’t. still trying to figure somehow to install Snowboy. just the npm install method is not executing properly. I need the help of dev if I could. but looks like he hasn’t touched his post for a while.

@Bugsounet with your automated process it got installed within modules of magic mirror.

@sdetweil So, what I was trying to do is update my eeprom as I was getting the error at boot. and so I did the bootloader factory reset as the steps mentioned

If your Raspberry Pi 4 will not boot, it is possible that the SPI EEPROM has become corrupted. To check, remove the SD card, disconnect the device from power, then reconnect it. If the green LED does not flash, this indicates that the EEPROM has become corrupted.

Raspberry Pi Imager provides an easy way to fix this problem, by automatically preparing an SD card that will reprogram your Raspberry Pi 4’s EEPROM:

Find an SD card that is empty, or does not contain any data you want to keep; it will be completely erased of all data during this process.
Download Raspberry Pi Imager for your operating system from the list near the top of this page.
Click “CHOOSE OS” and select “Misc utility images” then “Pi 4 EEPROM boot recovery”.
Insert an SD card, click “CHOOSE SD CARD”, select the card you have inserted, then click “WRITE”.
Once the SD card is ready, insert it into your Raspberry Pi 4 then connect the Raspberry Pi to power.
Once complete, the green LED will blink rapidly in a steady pattern. Disconnect the device from power. Now you can remove the recovery SD card, insert your usual SD card, and resume using your Raspberry Pi.

that fixed the issue with eeprom not being corrupted.

But later checking the current eeprom I noticed, for some reason the default bootloader I have in Raspberry Pi’s eeprom has been set as such for every new boot I had to short the Global_EN with ground to boot the Pi.

Even that being done it did not boot the new sd card’s no matter what. (So my guess right here is its cause of the makeshift power adaptor I am using which is converting 12v dc to 5v dc)
At this point I’m starting to hate these newer RPI4’s already.

Edit- so there was actually some issue with my SD cards not being flashed properly, now I have enabled the USB boot with the latest eeprom, and the PI boots normally. will get a good sd card reader.

@sdetweil sorry to say, but nope it does not work on mine. the same snowboy installation error.

@sdetweil yes thats the one.
Also I just checked there are few parameters in that config that I have slightly different than default. Even after flashing the default recovery.img it did not get changed. So I will do it manually and check if it works.

@sdetweil I tried the boot recovery mentioned in the link, but no luck with that. Still gets stuck in boot and with a red light. no green light. should I try to get a replacement for my device?

Also now I am facing this problem where, no matter what I do, RPI4 does not take any other sd card boot image and boot that particular system.
For instance, My 32gb with working MM and RPI OS 32bit, boot up without any problem.
But then, I tried booting with a older build of RPI OS, Ubuntu(https://ubuntu.com/download/raspberry-pi) 32bit for Pi4.

Both tried on different sd cards with 8gb/32gb and also reformatting it several times and everything.

I feel just so exhausted doing all this and thinking of returning my RPI4 if it has so may issues.

@Bugsounet said in MMM Awesome Alexa installing snowboy.:

@Ameyalgudkar:
I see in the error log it’s an x64 build…
so best way is reinstall OS with 32bits version

I am indeed running the 32bit Raspberry Pi OS latest from the official downloads, and not any beta versions.
I don’t know why the installer is running it in x64.

@sdetweil If you could make a copy of your image file or if you have it saved on your disk maybe?
could you upload it to google cloud or something?

@sdetweil

there.
and if there’s a way to run it on 4.19 then how do I downgrade?

@sdetweil I believe I’m on 5.4.51 kernel but not sure if that’s the one. and don’t know if 32/64 bit.

@sdetweil yes those steps.
The one I am referring to is 4th to last.

@sdetweil I did follow all the steps, and now I am getting stuck at this npm install step for installing dependencies. namely “snowboy” which is required for the hotword recognition.

I’m having the following issue/error after running this command “npm install” trying to install snowboy.
If anyone has found solutions to this error, please please PLEASE let me know.

node-pre-gyp ERR! stack at ChildProcess. (/home/pi/MagicMirror/node_modules/snowboy/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack at ChildProcess.emit (events.js:198:13)
node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:982:16)
node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Linux 5.4.51-v7l+
node-pre-gyp ERR! command “/usr/bin/node” “/home/pi/MagicMirror/node_modules/snowboy/node_modules/.bin/node-pre-gyp” “install” “–fallback-to-build”
node-pre-gyp ERR! cwd /home/pi/MagicMirror/node_modules/snowboy
node-pre-gyp ERR! node -v v10.22.0
node-pre-gyp ERR! node-pre-gyp -v v0.12.0
node-pre-gyp ERR! not ok
Failed to execute ‘/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/MagicMirror/node_modules/snowboy/lib/node/binding/Release/node-v64-linux-arm/snowboy.node --module_name=snowboy --module_path=/home/pi/MagicMirror/node_modules/snowboy/lib/node/binding/Release/node-v64-linux-arm --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64’ (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! snowboy@1.3.1 install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the snowboy@1.3.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/pi/.npm/_logs/2020-09-11T13_22_25_913Z-debug.log

@sdetweil well, thank you for the time I appreciate it. and hope you find a solution in future for this.