Solved Upgrading GA from v3 to v4 with a Raspberry pi 4b
-
Turns out a simple delete or cut-move will do it.
Following the wiki i git cloned inside modules directory the google assistant , it installed normally
but at the end i can see this :MMM-GoogleAssistant is now installed ! npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN notsup Unsupported engine for find-up@6.3.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: find-up@6.3.0 npm WARN notsup Unsupported engine for locate-path@7.1.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: locate-path@7.1.0 npm WARN notsup Unsupported engine for path-exists@5.0.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: path-exists@5.0.0 npm WARN notsup Unsupported engine for p-locate@6.0.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: p-locate@6.0.0 npm WARN notsup Unsupported engine for p-limit@4.0.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: p-limit@4.0.0 added 119 packages from 148 contributors and audited 119 packages in 39.132s 15 packages are looking for funding run `npm fund` for details found 0 vulnerabilities
What is happening here? should i change my npm version so that those can be installed ? or i do not understand exactly .
-
cd ~/MagicMirror/modules/MMM-GoogleAssistant rm -rf package-lock.json node_modules git checkout -f prod git reset --hard HEAD git pull npm install
-
Bugs for the win as usual xD
still though at the end of the installation i can see those and i am not sure if i need to change npm version to v14.13.1 and up in order to install them . is that correct? -
Hi, Just follow wiki rules
-
I think i am checking the current wiki right now and it doesn’t say anything anywhere about those warns at the end of the installation.
pi@raspberrypi:~/MagicMirror/modules/MMM-GoogleAssistant $ npm install > MMM-GoogleAssistant@4.0.3 preinstall /home/pi/MagicMirror/modules/MMM-GoogleAssistant > installer/preinstall.sh Welcome to MMM-GoogleAssistant v4.0.3 No root checking... Checking MMM-GoogleAssistant: pi/pi Checking MagicMirror: pi/pi Checking OS... OS Detected: linux-gnueabihf (raspbian 11 armv7l) Installing all npm libraries... > @bugsounet/secure-ga-v4@1.0.1 preinstall /home/pi/MagicMirror/modules/MMM-GoogleAssistant/node_modules/@bugsounet/secure-ga-v4 > node secure.js [SECURE] Check MMM-GoogleAssistant digital footprint... [SECURE] Ok, Good choice! [SECURE] Let's continue installing... > protobufjs@6.11.2 postinstall /home/pi/MagicMirror/modules/MMM-GoogleAssistant/node_modules/protobufjs > node scripts/postinstall > MMM-GoogleAssistant@4.0.3 postinstall /home/pi/MagicMirror/modules/MMM-GoogleAssistant > installer/postinstall.sh Minify Main code Process File: ../node_helper.js Process File: ../components/assistant.js Process File: ../components/response.js Process File: ../components/screenParser.js Process File: ../MMM-GoogleAssistant.js Done Support is now moved in a dedicated Server: https://forum.bugsounet.fr @bugsounet MMM-GoogleAssistant is now installed ! npm notice created a lockfile as package-lock.json. You should commit this file. npm WARN notsup Unsupported engine for find-up@6.3.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: find-up@6.3.0 npm WARN notsup Unsupported engine for locate-path@7.1.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: locate-path@7.1.0 npm WARN notsup Unsupported engine for path-exists@5.0.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: path-exists@5.0.0 npm WARN notsup Unsupported engine for p-locate@6.0.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: p-locate@6.0.0 npm WARN notsup Unsupported engine for p-limit@4.0.0: wanted: {"node":"^12.20.0 || ^14.13.1 || >=16.0.0"} (current: {"node":"14.0.0","npm":"6.14.15"}) npm WARN notsup Not compatible with your version of node/npm: p-limit@4.0.0 added 119 packages from 148 contributors and audited 119 packages in 14.982s 15 packages are looking for funding run `npm fund` for details found 0 vulnerabilities
those at the end say not compatible with your version of node/npm but i have installed node 14 and npm 6.14.15 as the modules wanted before. What should i do ?
-
find-up@6.3.0
locate-path@7.1.0
path-exists@5.0.0
p-locate@6.0.0
p-limit@4.0.0
i have a warning at the end about all these i think they are not properly installed? or upgraded to the last vesion not sure but something is wrong here -
just install a correct the correct node version
needed ^14.13.1 --> minimal node v14.13.1
and you have:current: {"node":"14.0.0" ...
It’s writed, just read
-
i am still quite a noob at linux but i am learning and i am not sure sometimes which is the best path.
Thank you very much though i bet they are so many people at my level or lower out there that they will for
sure find a lot of help in this post. Its because you already are a programming god and we are still learning to code , especially with node xD -
So for the rest of the starting coders i personally have installed and use the : Node version Manager
and i opened a terminal
nvm install v16.0.0
and then because v16 comes with another npm you will also have to type :
npm install -g npm@6.14.15
then
npm install and everything is smooth.
Which node version works bett with the new v4 Google Assistant 14.13.1 or 16.0.0 or someone else ? -
Humm…
maybe the wiki is useless ?
should I delete it ?
or maybe an writer access is needed ? do you want to rewrite it ?Or make as you want (If you prefer ignore all my suggest)
and try to do better:
see you in ~50 days (if you have this uptime)
-
The wiki is perfect as i go on and yeah i shouldnt write so much i just thought that someone else would also benefit from my point of view plus i would also learn more.
-
Continuing with the wiki i installed the GATEWAY which is the new program to communicate with the other google assistant modules.
In EXT-Detector which is the new hot word detector i can see that i have 3 npm warnings that i am not sure how to fix ,pi@raspberrypi:~/MagicMirror/modules/EXT-Detector $ npm install > EXT-Detector@1.0.1 preinstall /home/pi/MagicMirror/modules/EXT-Detector > installer/preinstall.sh Welcome to EXT-Detector "1.0.1", Checking OS... OS Detected: linux-gnueabihf (raspbian 11 armv7l) Checking all dependencies... All Dependencies needed are installed ! Installing all npm libraries... npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. > @bugsounet/snowboy@2.2.5 install /home/pi/MagicMirror/modules/EXT-Detector/node_modules/@bugsounet/snowboy > bash scripts/installer.sh
i tryed Npm install uuid@7.0.3 but i got 2 red vanurabilities at the end so with my next command npm audit fix i could see that it just rolled back.
Can someone please help me understand what must i do in order to have no npm warnings? -
i also tryed inside the magic mirror / node_modules
npm i
but nothing. Which for the life of me i forgot what the command even do xD -
It order to do?
humm nothingWhy this warn ?
Just because i force to use some library and I don’t want to full recode some big part of codeA warn is not an error
It’s just because I force somethingIt’s like windows…
Warn: windows 11 is out ! -> i don’t want to use it… so i use windows 10 -
ok then and thank you for the explanation it will really help in the future : )
-
This migration is planned… but I prefer to code some new EXT before !
-
I found the config.js part of GATEWAY a little bit sort xD
{
module: ‘Gateway’
},i hope in the future you will create more options for the users over time as we test it.
-
just because … there is no config actually !
why ?
This module have no display
Why configuring something ? to display 2 EXT at same time (sample youtube and spotify ?)
self Rules is betterin all case: V1.1 is under-coding
I code this version for lazy guy (like me!!!)
This version will allow to configure and install with a html page (with computer, phone, tablet,…) all EXT plugins
Naturally, this “web link” will be protected with an username and password ! -
Ouaou sounds really awesome and insanely easy just don’t forget to leave us , the users some space to personalize .
-
it’s planned… don’t worry !
and after an auto-update (EXT-UpdateNotification) … you will have an auto-installer !