Read the statement by Michael Teeuw here.
MMM-AssistantMk2 problems when using electron-rebuild
-
@mrega
Dear buddy,
After some research, I’ve found something. a few days ago,grpcwas updated, but proper binaries are not provided yet. That’s why rebuild-from-source doesn’t work.Here is an urgent but experimental fix.
I cannot give a guarantee to work, but think there is worthy of trying.first,
cd node_modules rm -rf grpc cd .. npm install @grpc/grpc-jsI wish
grpcrelease proper target binaries ASAP. -
Hi @Sean
I have the same problem trying to build from scratch. It fails at grpc, I tried your solution but is the samegyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/node-gyp/lib/build.js:262:23) gyp ERR! stack at ChildProcess.emit (events.js:180:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12) gyp ERR! System Linux 4.14.62-v7+ gyp ERR! command "/usr/bin/node" "/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/.bin/node-gyp" "rebuild" "--target=2.0.0" "--arch=arm" "--dist-url=https://atom.io/download/electron" "--build-from-source" "--module_name=grpc_node" "--module_path=/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_binary/electron-v2.0-linux-arm-glibc" "--host=https://node-precompiled-binaries.grpc.io/" "--remote_path={name}/v1.14.1" "--package_name=electron-v2.0-linux-arm-glibc.tar.gz" gyp ERR! cwd /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc gyp ERR! node -v v9.11.2 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok -
@yep_dd
Here is the answer fromgrpc-nodecommunity
https://github.com/grpc/grpc-node/issues/507#issuecomment-414465022
So, wait for a while… It’s not the fault of my module… T_T
-
@sean said in MMM-AssistantMk2 problems when using electron-rebuild:
rm -rf grpc
Hi @Sean,
cool that helps. You you just advice for some of the not so advanced npm and node users how to downgrade?
Thank you so much,
Stephan
-
@yep_dd
Currently, I’m not in front of my device, so I write this without test.npm install [package]@[version]That is a usual form.
Thus,
cd ~/MagicMirror/modules/MMM-AssistantMk2 rm -rf ./node_modules/grpc npm install grpc@1.13would work, I think.
-
if anybody needs a working raspie3b+ image with hotword/notification/assistant installed drop a pm
:-)
-
@Sean
works like a charm, thank you -
@Sean
off topic: is there a way to set the audio output (Device / Program) routing like “record” for the mic?
-
This post is deleted! -
@yep_dd
I didn’t make it configurable much. But you can modify ‘node_helper.js’ by yourselfvar speaker = new Speaker({
channels: 1,
sampleRate: cfgInstance.conversation.audio.sampleRateOut,
});You can add here ‘device:”hw:1,0”,”. I’ll fix them to be configurable next update.
-
@Sean
cool, works, thank you so much. Would you know where youtube audio is configured? Because that still uses the standard.
-
@yep_dd I don’t know about that, sorry. :| I think you should adjust your mixer (alsa? or pulse?)
-
@Sean
correct, works. Modified /usr/share/alsa/alsa.conf for the default sound card and added a “record” for MMM-Hotkey so it wouldn’t use that as default: working just fine.Just stuttering, the audio output as well as video. Let’s see why… when audio is played through the 3.5mm jack it works fine.
-
@Sean
what is your CPU usage when playing youtube videos and using the google assistent? I am using OpenGL for rendering… but videos and audio via HDMiIseems to stutter
-
-
@dvbit Frankly I use mainly Asus Tinker Board. I couldn’t satisfied with performance of RPI3,
anyway, usually, with BT speaker, RPI3 has good enough sound. For video, I think non-HD youtube video can be played enough. -
@sean yes I saw your posts and realized it. Also had a look and thought about getting an asus but finally went for raspb3 for gpio support (at least in my readings it was saying it was suboptimal…)
I might give an AEON with atom (that I have) a ride if more power is needed.PS: I went through the google sdk to understand current capabilities (especially in my language) and saw the output limitations you mentionned.
I could not find a list of supported features compared to smartphone assitant. do you have any pointer? tx -
@dvbit For screenOutput? At this moment, Nothing. It is experimental stage. Screenoutput is too tight binded with specific hw. By example, original search results of video is not playable. It is assumed to activate app on smartTv. I had to parse static html output to catch youtube Video Id.
-
I switched back to headphone jack output and it is the same. Video and sound stutters.
-
@Sean
Tinker Board looks promising… will take me a while to set up and I am working the next couple of days, let’s see :).
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login