Read the statement by Michael Teeuw here.
The latest Install Guide (MM w/ Google Assistant)
-
@Ayos53 said in The latest Install Guide (MM w/ Google Assistant):
I havent folder node module.
its node_modules (note the trailing s)…
it will be there if you ran npm install in the MMM-Hotword folder as required by the install instructions (the install.sh script does this)
-
Sorry it’s me again.
I have a problem when i launch magicmiror, he crashed.
The log file :0 info it worked if it ends with ok 1 warn npm npm does not support Node.js v10.15.2 2 warn npm You should probably upgrade to a newer version of node as we 3 warn npm can't make any promises that npm will work with this version. 4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. 5 warn npm You can find the latest version at https://nodejs.org/ 6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 7 info using npm@5.8.0 8 info using node@v10.15.2 9 verbose run-script [ 'prestart', 'start', 'poststart' ] 10 info lifecycle magicmirror@2.9.0~prestart: magicmirror@2.9.0 11 info lifecycle magicmirror@2.9.0~start: magicmirror@2.9.0 12 verbose lifecycle magicmirror@2.9.0~start: unsafe-perm in lifecycle true 13 verbose lifecycle magicmirror@2.9.0~start: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games 14 verbose lifecycle magicmirror@2.9.0~start: CWD: /home/pi/MagicMirror 15 silly lifecycle magicmirror@2.9.0~start: Args: [ '-c', 'sh run-start.sh' ] 16 info lifecycle magicmirror@2.9.0~start: Failed to exec start script 17 verbose stack Error: magicmirror@2.9.0 start: `sh run-start.sh` 17 verbose stack spawn ENOENT 17 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18) 17 verbose stack at ChildProcess.emit (events.js:189:13) 17 verbose stack at maybeClose (internal/child_process.js:970:16) 17 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 18 verbose pkgid magicmirror@2.9.0 19 verbose cwd /home/pi/MagicMirror 20 verbose Linux 4.19.75-v7l+ 21 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 22 verbose node v10.15.2 23 verbose npm v5.8.0 24 error file sh 25 error code ELIFECYCLE 26 error errno ENOENT 27 error syscall spawn 28 error magicmirror@2.9.0 start: `sh run-start.sh` 28 error spawn ENOENT 29 error Failed at the magicmirror@2.9.0 start script. 29 error This is probably not a problem with npm. There is likely additional logging output above. 30 verbose exit [ 1, true ]
If someone have an idea ?
-
@Ayos53 said in The latest Install Guide (MM w/ Google Assistant):
/home/pi/MagicMirror
seems a file is missing, please do
ls /home/pi/MagicMirror/run-start.sh
you should see this result
pi@raspberrypi:~ $ ls /home/pi/MagicMirror/run-start.sh /home/pi/MagicMirror/run-start.sh
it is part of the git clone distribution and never changed
-
@sdetweil
i dols /home/pi/MagicMirror/run-start.sh
and yes i have this result
pi@raspberrypi:~ $ ls /home/pi/MagicMirror/run-start.sh /home/pi/MagicMirror/run-start.sh
but always crash after 1 seconde
i see this :
> magicmirror@2.9.0 start /home/pi/MagicMirror > sh run-start.sh Starting MagicMirror: v2.9.0 Loading config ... Loading module helpers ... No helper found for module: alert. Initializing new module helper ... Module helper loaded: updatenotification No helper found for module: clock. No helper found for module: currentweather. No helper found for module: weatherforecast. Initializing new module helper ... Module helper loaded: newsfeed Initializing new module helper ... Module helper loaded: MMM-NetworkConnection Initializing new module helper ... Module helper loaded: MMM-Hotword Initializing new module helper ... Module helper loaded: MMM-AssistantMk2 All module helpers loaded. Starting server on port 8080 ... Server started ... Connecting socket for: updatenotification Connecting socket for: newsfeed Starting module: newsfeed Connecting socket for: MMM-NetworkConnection MMM-NetworkConnection helper started ... Connecting socket for: MMM-Hotword [HOTWORD] MMM-Hotword starts Connecting socket for: MMM-AssistantMk2 Sockets connected & modules started ... Launching application. Create new news fetcher for url: https://www.francetvinfo.fr/titres.rss - Interval: 300000 [AMK2] Recipe is loaded: hide_and_show_all_modules.js [AMK2] Recipe is loaded: reboot.js [AMK2] Recipe is loaded: screen_onoff.js [AMK2] Recipe is loaded: shutdown.js [HOTWORD] No model to load [AMK2] Temporal storage directory is clearing. [AMK2] assistant ready /home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js: symbol lookup error: /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_binary/electron-v3.0-linux-arm-glibc/grpc_node.node: undefined symbol: __atomic_store_8 npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! magicmirror@2.9.0 start: `sh run-start.sh` npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the magicmirror@2.9.0 start 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/2019-12-04T14_51_36_364Z-debug.log
-
@Ayos53 said in The latest Install Guide (MM w/ Google Assistant):
home/pi/MagicMirror/node_modules/electron/dist/electron js/electron.js: symbol lookup error: /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_binary/electron-v3.0-linux-arm-glibc/grpc_node.node: undefined symbol: __atomic_store_8
that is the error
this is a known problem, one of the services the module depends on has a bug,
@Sean will need to give the answer, as I don’t see a specific set of steps to resolve it
the ‘fix’ is to downgrade the grpc module to version 1.23 (from 1.24 u are on now)
-
the ‘fix’ is to downgrade the grpc module to version 1.23 (from 1.24 u are on now)
ok no problem but, i don’t know how do this
-
@Ayos53 me either… there are a number of steps, but I don’t know them all
thats why we need @Sean help -
@Ayos53
read this
https://github.com/eouia/MMM-AssistantMk2/tree/master#some-more-troubleshootingfirst part of “some more troubleshooting”
-
@sdetweil
Its ok now i follow this post :
https://github.com/eouia/MMM-AssistantMk2/issues/231Now the mirror start without error.
I have a new problem : the assistant not respond when i say “jarvis”
but if i click on the logo, it’s ok.
Problem with Hotword ? -
Hello ! I have a problem with this topic haha I install all in my magic mirror, but I don’t have a icon google assistant on my screen…
Everythings is ok until step 7. I test with the command “node auth_and_test.js” and it’s okay. I don’t understand why I don’t have icon google on my screen…
Can you help me please? how can I check ?
Sorry for my english, I’m french :Pmodule: "MMM-Hotword", config: { record: { recordProgram : "arecord", device : "plughw:1" }, autostart:true, onDetected: { notification: (payload) => { return "ASSISTANT_ACTIVATE" }, payload: (payload) => { return { profile: payload.hotword } } }, }, }, { module: "MMM-AssistantMk2", position: "bottom_bar", config: { deviceLocation: { coordinates: { // set the latitude and longitude of the device to get localized information like weather or time. (ref. mygeoposition.com) latitude: 45.5662672, // -90.0 - +90.0 longitude: 5.9203636, // -180.0 - +180.0 }, }, record: { recordProgram : "arecord", device : "plughw:1", }, notifications: { ASSISTANT_ACTIVATED: "HOTWORD_PAUSE", ASSISTANT_DEACTIVATED: "HOTWORD_RESUME", }, useWelcomeMessage: "brief today", profiles: { "default" : { lang: "en-US" } }, } },