Suite à mes soucis (cf.mon autre post du jour), je suis en pleine migration de openzwave vers zwaveJS.
J’ai un capteur d’ouverture Fibaro FGDW-002 qui n’est pas correctement identifié dans le plugin Zwave-JS.
Le modèle est " Unknown product 0xXXXX - 0xXXXX" et par conséquent aucune commande n’est créée. J’ai bien réveillé le module en ouvrant notamment la porte plusieurs fois et le plugin reçoit bien des données mais il ne les identifie visiblement pas.
Quelqu’un a-t-il réussi a intégrer ces modules dans ce plugin ?
Bonjour,
Sur un de mes modules à piles, j’avais du faire un bon reset.
J’avais enlevé la pile et court-circuité avec un fil le + et le - du module quelques secondes pour bien vider l’électronique.
Après il s’était inclus du premier coup, c’était sa dernière chance avant la poubelle. Il était prévenu ça l’avait motivé
Pour le FGR, je viens de l’interviewer, cela n’a rien changé. Cela peut-il venir du mode sécurisé d’inclusion? (je ne sais pas s’ils sont inclus comme cela mais dans le doute. j’ai pourtant modifié la clé comme indiqué dans la doc).
Pour le module sur pile l’interview n’est pas complétée. Sois tu es trop loin du contrôleur sois tu ne l’as pas réveillé correctement.
Pour le FGR223 l’interview est complète. Il n’est pas inclu en sécurisé. Très bizarre. Tu as synchronisé avec Jeedom ?
Dans zwavejsUI (il y a un bouton dédié pour y accéder) il est vu comment ?
Error: Not Found
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/server/app.js:1168:17
at Layer.handle [as handle_request] (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/index.js:328:13)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/index.js:286:9
at Function.process_params (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/index.js:346:12)
at next (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/index.js:280:10)
at session (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express-session/index.js:487:7)
at Layer.handle [as handle_request] (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/index.js:328:13)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/express/lib/router/index.js:286:9
Je tente une réinstallation des dépendances, mon SWAP est de 2048…
EDIT: idem après la réinstallation des dépendances
Je les trouve à quel endroit exactement stp? Histoire de ne pas t’envoyer les mauvaises vu que je n’y connais pas grand chose.
Celles-ci?
Log du plugin zwavejs_packages
Log brut
Rechercher
> + echo '*******************Begin of package installation******************'
> *******************Begin of package installation******************
> + touch /tmp/jeedom_install_in_progress_zwavejs
> + echo 1
> + echo 2
> + sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
> + sudo /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
> + echo 'Pre installation de l'\''installation/mise à jour des dépendances zwavejs'
> Pre installation de l'installation/mise à jour des dépendances zwavejs
> +++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
> ++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
> ++ pwd
> + BASEDIR=/var/www/html/plugins/zwavejs/resources
> + cd /var/www/html/plugins/zwavejs/resources
> + source ../core/config/zwavejs.config.ini
> + echo 'Wanted Version: 9.12.0'
> Wanted Version: 9.12.0
> + rm -R zwave-js-ui
> + git clone --branch v9.12.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
> Cloning into 'zwave-js-ui'...
> Note: switching to '96eeb76b110f27d3ce16cfb4b3992cb8f8dc34d8'.
> You are in 'detached HEAD' state. You can look around, make experimental
> changes and commit them, and you can discard any commits you make in this
> state without impacting any branches by switching back to a branch.
> If you want to create a new branch to retain commits you create, you may
> do so (now or later) by using -c with the switch command. Example:
> git switch -c <new-branch-name>
> Or undo this operation with:
> git switch -
> Turn off this advice by setting config variable advice.detachedHead to false
> + echo 'Pre install finished'
> Pre install finished
> + echo 3
> + php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
> apt: no process found
> apt-get: no process found
> WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 300 packages can be upgraded. Run 'apt list --upgradable' to see them.
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> git is already the newest version (1:2.30.2-1+deb11u2).
> lsb-release is already the newest version (11.1.0+rpi1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
> [Check Version NodeJS actuelle : v18.20.1 : [ OK ]
> [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> git is already the newest version (1:2.30.2-1+deb11u2).
> lsb-release is already the newest version (11.1.0+rpi1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
> [Check Version NodeJS actuelle : v18.20.1 : [ OK ]
> [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> git is already the newest version (1:2.30.2-1+deb11u2).
> lsb-release is already the newest version (11.1.0+rpi1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
> [Check Version NodeJS actuelle : v18.20.1 : [ OK ]
> [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
> --2024-06-21 15:40:51-- https://getcomposer.org/installer
> Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
> Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 58444 (57K) [application/octet-stream]
> Saving to: 'composer-setup.php'
> 0K .......... .......... .......... .......... .......... 87% 2.83M 0s
> 50K ....... 100% 38.7M=0.02s
> 2024-06-21 15:40:51 (3.19 MB/s) - 'composer-setup.php' saved [58444/58444]
> Begin installation of composer
> All settings correct for using Composer
> Downloading...
> Composer (version 2.7.7) successfully installed to: /var/www/html/core/ajax/composer.phar
> Use it: php composer.phar
> End installation of composer
> npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
> npm WARN deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
> added 117 packages, and audited 118 packages in 14s
> 19 packages are looking for funding
> run `npm fund` for details
> found 0 vulnerabilities
> Synchronizing state of mosquitto.service with SysV service script with /lib/systemd/systemd-sysv-install.
> Executing: /lib/systemd/systemd-sysv-install enable mosquitto
> + echo 4
> + sudo killall apt apt-get unattended-upgr
> apt: no process found
> apt-get: no process found
> unattended-upgr: no process found
> + sudo rm /var/lib/apt/lists/lock
> + sudo rm /var/cache/apt/archives/lock
> rm: cannot remove '/var/cache/apt/archives/lock': No such file or directory
> + sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
> + sudo sudo dpkg --configure -a --force-confdef
> + sudo apt update
> WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Building dependency tree...
> Reading state information...
> 300 packages can be upgraded. Run 'apt list --upgradable' to see them.
> + echo 5
> + sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
> + sudo /var/www/html/core/class/../../resources/install_nodejs.sh
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> git is already the newest version (1:2.30.2-1+deb11u2).
> lsb-release is already the newest version (11.1.0+rpi1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
> [Check Version NodeJS actuelle : v18.20.1 : [ OK ]
> [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
> + echo 6
> + sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
> + sudo /var/www/html/core/class/../../resources/install_nodejs.sh
> Hit:1 http://archive.raspberrypi.org/debian buster InRelease
> Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> git is already the newest version (1:2.30.2-1+deb11u2).
> lsb-release is already the newest version (11.1.0+rpi1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
> [Check Version NodeJS actuelle : v18.20.1 : [ OK ]
> [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
> + echo 7
> + sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
> + sudo /var/www/html/core/class/../../resources/install_nodejs.sh
> Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
> Hit:2 http://archive.raspberrypi.org/debian buster InRelease
> Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> git is already the newest version (1:2.30.2-1+deb11u2).
> lsb-release is already the newest version (11.1.0+rpi1).
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> The following packages have unmet dependencies:
> libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
> [Check Version NodeJS actuelle : v18.20.1 : [ OK ]
> [Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
> + echo 8
> + sudo chmod +x /var/www/html/core/class/../../resources/install_composer.sh
> + sudo /var/www/html/core/class/../../resources/install_composer.sh
> Begin installation of composer
> --2024-06-21 15:43:04-- https://getcomposer.org/installer
> Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
> Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 58444 (57K) [application/octet-stream]
> Saving to: 'composer-setup.php'
> 0K .......... .......... .......... .......... .......... 87% 1.83M 0s
> 50K ....... 100% 28.7M=0.03s
> 2024-06-21 15:43:04 (2.07 MB/s) - 'composer-setup.php' saved [58444/58444]
> All settings correct for using Composer
> Downloading...
> Composer (version 2.7.7) successfully installed to: /var/www/html/core/ajax/composer.phar
> Use it: php composer.phar
> End installation of composer
> + echo 9
> + sudo NODE_OPTIONS=--dns-result-order=ipv4first npm install --force -g yarn
> npm WARN using --force Recommended protections disabled.
> changed 1 package in 10s
> + echo 10
> + sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
> + sudo /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
> + echo 'Post installation de l'\''installation/mise à jour des dépendances zwavejs'
> Post installation de l'installation/mise à jour des dépendances zwavejs
> +++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
> ++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
> ++ pwd
> + BASEDIR=/var/www/html/plugins/zwavejs/resources
> + cd /var/www/html/plugins/zwavejs/resources
> + cd zwave-js-ui
> + sudo yarn install
> yarn install v1.22.22
> info No lockfile found.
> warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
> [1/5] Validating package.json...
> [2/5] Resolving packages...
> warning archiver > archiver-utils > glob@8.1.0: Glob versions prior to v9 are no longer supported
> warning archiver > archiver-utils > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
> warning csurf@1.11.0: Please use another csrf package
> warning native-url > querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
> warning vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
> warning @types/extract-zip@2.0.1: This is a stub types definition. extract-zip provides its own type definitions, so you do not need this installed.
> warning c8 > test-exclude > glob@7.2.3: Glob versions prior to v9 are no longer supported
> warning c8 > test-exclude > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
> warning c8 > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
> warning c8 > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
> warning docsify-cli > docsify-server-renderer@4.13.1: docsify-server-renderer 4.x and below is no longer supported while we investigate the future of SSR and SSG for Docsify
> warning eslint > @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
> warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
> warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
> warning mocha > glob@8.1.0: Glob versions prior to v9 are no longer supported
> warning release-it > shelljs > glob@7.2.3: Glob versions prior to v9 are no longer supported
> warning vite-plugin-pwa > workbox-build > glob@7.2.3: Glob versions prior to v9 are no longer supported
> warning vite-plugin-pwa > workbox-build > @surma/rollup-plugin-off-main-thread > magic-string > sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
> [3/5] Fetching packages...
> [4/5] Linking dependencies...
> warning " > vis-data@7.1.9" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
> warning " > vis-data@7.1.9" has unmet peer dependency "vis-util@^5.0.1".
> warning " > vis-network@9.1.9" has unmet peer dependency "@egjs/hammerjs@^2.0.0".
> warning " > vis-network@9.1.9" has unmet peer dependency "component-emitter@^1.3.0".
> warning " > vis-network@9.1.9" has unmet peer dependency "keycharm@^0.2.0 || ^0.3.0 || ^0.4.0".
> warning " > vis-network@9.1.9" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
> warning " > vis-network@9.1.9" has unmet peer dependency "vis-util@^5.0.1".
> warning " > @babel/register@7.24.6" has unmet peer dependency "@babel/core@^7.0.0-0".
> warning " > vite-plugin-pwa@0.16.7" has unmet peer dependency "workbox-build@^7.0.0".
> warning " > vite-plugin-pwa@0.16.7" has unmet peer dependency "workbox-window@^7.0.0".
> [5/5] Building fresh packages...
> success Saved lockfile.
> Done in 339.81s.
> + sudo yarn run build
> yarn run v1.22.22
> $ npm-run-all 'build:*'
> $ tsc
> $ vite build
> vite v4.5.3 building for production...
> transforming...
> <--- Last few GCs --->
> [25919:0x42678e8] 182877 ms: Mark-sweep 218.9 (235.3) -> 216.8 (235.3) MB, 3085.1 / 0.0 ms (average mu = 0.150, current mu = 0.108) allocation failure; scavenge might not succeed
> [25919:0x42678e8] 186214 ms: Mark-sweep 219.1 (235.6) -> 216.9 (235.8) MB, 3027.3 / 0.0 ms (average mu = 0.120, current mu = 0.093) allocation failure; scavenge might not succeed
> <--- JS stacktrace --->
> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
> Aborted
> error Command failed with exit code 134.
> info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
> ERROR: "build:ui" exited with 134.
> error Command failed with exit code 1.
> info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
> + chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md api certs docker docs esbuild-register.js esbuild.js genereteDocs.ts index.html kubernetes kustomization.yaml node_modules nodemon.json package-lock.json package.json package.sh pkg public server server_config.js snippets src store test tsconfig.eslint.json tsconfig.json vite.config.js wallaby.js yarn.lock
> + '[' -e /dev/ttyAMA0 ']'
> + '[' -e /dev/ttymxc0 ']'
> + '[' -e /dev/ttyAMA0 ']'
> ++ grep Revision /proc/cpuinfo
> ++ cut -d: -f2
> ++ tr -d ' '
> + RPI_BOARD_REVISION=a02082
> + [[ a02082 == \a\0\2\0\8\2 ]]
> + systemctl disable hciuart
> Unit /etc/systemd/system/hciuart.service is masked, ignoring.
> ++ grep dtoverlay=pi3-miniuart-bt /boot/config.txt
> + [[ ! -n '' ]]
> + echo 'Raspberry Pi 3 Detected. If you use a Razberry board you must Disable Bluetooth'
> Raspberry Pi 3 Detected. If you use a Razberry board you must Disable Bluetooth
> + echo 'Please add '\''dtoverlay=pi3-miniuart-bt'\'' to the end of the file /boot/config.txt'
> Please add 'dtoverlay=pi3-miniuart-bt' to the end of the file /boot/config.txt
> + echo 'And reboot your Raspberry Pi'
> And reboot your Raspberry Pi
> + echo 'Everything is successfully installed!'
> Everything is successfully installed!
> + echo 11
> + php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
> + echo 12
> + rm /tmp/jeedom_install_in_progress_zwavejs
> + echo '*******************End of package installation******************'
> *******************End of package installation******************
Je vais essayer le lien de l’autre topic, merci beaucoup.
EDIT: c’est celui qui m’a fait augmenter ma taille de swap, j’étais à 1024 jusqu’à cet aprem, j’ai mis 2048.
Je ne comprends pas les logs avec les 300maj, j’ai fait apt update/upgrade cet après-midi pendant mes nombreux tests avant d’écrire !
Je le refais et retente…
Bonsoir, j’ai fait une montée de version, j’ai suivi un tuto (sur ce forum ou un autre j’ai un doute).
j’ai dû faire une bêtise sur mon apt upgrade tout à l’heure car là j’ai le droit à une grosse MAJ et il m’a indiqué qu’il allait supprimer des paquets, j’espère que ça va tout nettoyer!
@Fabrice a mis le doigt sur quelque chose à éviter.
Il vaut mieux installer de zéro un Debian 11, installer Jeedom puis restaurer un backup que de monter de version. C’est une grosse source de problèmes potentiels.
La réinstallation des dépendances à l’air mieux !!!
+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_zwavejs
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
+ echo 'Pre installation de l'\''installation/mise à jour des dépendances zwavejs'
Pre installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ source ../core/config/zwavejs.config.ini
+ echo 'Wanted Version: 9.12.0'
Wanted Version: 9.12.0
+ rm -R zwave-js-ui
+ git clone --branch v9.12.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: switching to '96eeb76b110f27d3ce16cfb4b3992cb8f8dc34d8'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c <new-branch-name>
Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
+ echo 'Pre install finished'
Pre install finished
+ echo 3
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
apt: no process found
apt-get: no process found
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.
[Check Version NodeJS actuelle : v18.20.3 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
E: Unable to correct problems, you have held broken packages.
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
[Check Version NodeJS actuelle : v18.20.3 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
E: Unable to correct problems, you have held broken packages.
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
[Check Version NodeJS actuelle : v18.20.3 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
--2024-06-21 21:03:27-- https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
0K .......... .......... .......... .......... .......... 87% 2.80M 0s
50K ....... 100% 19.6M=0.02s
2024-06-21 21:03:28 (3.14 MB/s) - 'composer-setup.php' saved [58444/58444]
Begin installation of composer
All settings correct for using Composer
Downloading...
Composer (version 2.7.7) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
added 117 packages, and audited 118 packages in 12s
19 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Synchronizing state of mosquitto.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mosquitto
+ echo 4
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
unattended-upgr: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
rm: cannot remove '/var/cache/apt/archives/lock': No such file or directory
+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
+ sudo sudo dpkg --configure -a --force-confdef
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 5
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.
[Check Version NodeJS actuelle : v18.20.3 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
+ echo 6
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.
[Check Version NodeJS actuelle : v18.20.3 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
+ echo 7
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed
E: Unable to correct problems, you have held broken packages.
[Check Version NodeJS actuelle : v18.20.3 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../resources/install_composer.sh
+ sudo /var/www/html/core/class/../../resources/install_composer.sh
Begin installation of composer
--2024-06-21 21:05:17-- https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
0K .......... .......... .......... .......... .......... 87% 2.79M 0s
50K ....... 100% 20.7M=0.02s
2024-06-21 21:05:17 (3.12 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.7) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
+ echo 9
+ sudo NODE_OPTIONS=--dns-result-order=ipv4first npm install --force -g yarn
npm warn using --force Recommended protections disabled.
changed 1 package in 10s
+ echo 10
+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
+ echo 'Post installation de l'\''installation/mise à jour des dépendances zwavejs'
Post installation de l'installation/mise à jour des dépendances zwavejs
+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
++ pwd
+ BASEDIR=/var/www/html/plugins/zwavejs/resources
+ cd /var/www/html/plugins/zwavejs/resources
+ cd zwave-js-ui
+ sudo yarn install
yarn install v1.22.22
info No lockfile found.
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] Validating package.json...
[2/5] Resolving packages...
warning archiver > archiver-utils > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning archiver > archiver-utils > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning csurf@1.11.0: Please use another csrf package
warning native-url > querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
warning vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
warning @types/extract-zip@2.0.1: This is a stub types definition. extract-zip provides its own type definitions, so you do not need this installed.
warning c8 > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning c8 > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning c8 > rimraf > glob > inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
warning c8 > test-exclude > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning docsify-cli > docsify-server-renderer@4.13.1: docsify-server-renderer 4.x and below is no longer supported while we investigate the future of SSR and SSG for Docsify
warning eslint > @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning mocha > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning release-it > shelljs > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vite-plugin-pwa > workbox-build > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vite-plugin-pwa > workbox-build > @rollup/plugin-replace > magic-string > sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > vis-data@7.1.9" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
warning " > vis-data@7.1.9" has unmet peer dependency "vis-util@^5.0.1".
warning " > vis-network@9.1.9" has unmet peer dependency "@egjs/hammerjs@^2.0.0".
warning " > vis-network@9.1.9" has unmet peer dependency "component-emitter@^1.3.0".
warning " > vis-network@9.1.9" has unmet peer dependency "keycharm@^0.2.0 || ^0.3.0 || ^0.4.0".
warning " > vis-network@9.1.9" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
warning " > vis-network@9.1.9" has unmet peer dependency "vis-util@^5.0.1".
warning " > @babel/register@7.24.6" has unmet peer dependency "@babel/core@^7.0.0-0".
warning " > vite-plugin-pwa@0.16.7" has unmet peer dependency "workbox-build@^7.0.0".
warning " > vite-plugin-pwa@0.16.7" has unmet peer dependency "workbox-window@^7.0.0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 376.66s.
+ sudo NODE_OPTIONS=--max_old_space_size=2048 yarn run build
yarn run v1.22.22
$ npm-run-all 'build:*'
$ tsc
$ vite build
vite v4.5.3 building for production...
transforming...
✓ 577 modules transformed.
rendering chunks...
computing gzip size...
dist/registerSW.js 0.14 kB
dist/manifest.webmanifest 0.50 kB
dist/index.html 1.68 kB │ gzip: 0.74 kB
dist/assets/MaterialIcons-Regular-5743ed3d.woff2 125.12 kB
dist/assets/MaterialIcons-Regular-e69d687a.eot 143.45 kB
dist/assets/MaterialIcons-Regular-11ec382a.woff 160.58 kB
dist/assets/MaterialIcons-Regular-29c11fa5.ttf 347.59 kB
dist/assets/DialogHealthCheck-2228ed6c.css 0.04 kB │ gzip: 0.06 kB
dist/assets/DialogGatewayValue-911dd212.css 0.06 kB │ gzip: 0.08 kB
dist/assets/NodeDetails-da00c417.css 0.06 kB │ gzip: 0.08 kB
dist/assets/Settings-81719688.css 0.08 kB │ gzip: 0.10 kB
dist/assets/QrReader-00dee3fb.css 0.09 kB │ gzip: 0.10 kB
dist/assets/NodePanel-c9b9749c.css 0.09 kB │ gzip: 0.10 kB
dist/assets/RichValue-3ea76a33.css 0.13 kB │ gzip: 0.12 kB
dist/assets/Mesh-b27cd214.css 0.26 kB │ gzip: 0.20 kB
dist/assets/ValueId-d2938c42.css 0.31 kB │ gzip: 0.18 kB
dist/assets/ExpandedNode-9f727a42.css 0.39 kB │ gzip: 0.26 kB
dist/assets/index-2a960184.css 0.39 kB │ gzip: 0.14 kB
dist/assets/DialogAdvanced-eaabda04.css 0.45 kB │ gzip: 0.23 kB
dist/assets/Store-6f25927f.css 0.79 kB │ gzip: 0.33 kB
dist/assets/BgRssiChart-3e7d7555.css 1.66 kB │ gzip: 0.71 kB
dist/assets/Login-1826b0a1.css 5.43 kB │ gzip: 1.52 kB
dist/assets/ZwaveGraph-fe07d4ee.css 220.27 kB │ gzip: 31.02 kB
dist/assets/index-fc01ccc5.css 645.37 kB │ gzip: 87.03 kB
dist/assets/items-bfe40980.js 0.26 kB │ gzip: 0.20 kB
dist/assets/ControllerChart-99e7695d.js 0.54 kB │ gzip: 0.34 kB
dist/assets/ColumnFilterBoolean-ba8303ac.js 0.70 kB │ gzip: 0.43 kB
dist/assets/ReinterviewBadge-75e6c516.js 0.77 kB │ gzip: 0.52 kB
dist/assets/BlinkIcon-b97cda1f.js 0.86 kB │ gzip: 0.42 kB
dist/assets/MissingKeysAlert-3f035272.js 1.18 kB │ gzip: 0.56 kB
dist/assets/ColumnFilterDate-fafa90f7.js 1.20 kB │ gzip: 0.57 kB
dist/assets/ColumnFilterString-5c27bd2c.js 1.26 kB │ gzip: 0.63 kB
dist/assets/DialogAdvanced-f34eacd6.js 1.31 kB │ gzip: 0.68 kB
dist/assets/StatisticsArrows-9a714635.js 1.35 kB │ gzip: 0.73 kB
dist/assets/ErrorPage-cc0b5ebe.js 1.56 kB │ gzip: 0.79 kB
dist/assets/ColumnFilterNumber-7381acff.js 1.77 kB │ gzip: 0.75 kB
dist/assets/file-input-24fa61bc.js 1.84 kB │ gzip: 0.86 kB
dist/assets/RichValue-a06892a0.js 2.06 kB │ gzip: 0.87 kB
dist/assets/StatisticsCard-1e9cb575.js 2.56 kB │ gzip: 1.00 kB
dist/assets/Mesh-3f68d601.js 2.87 kB │ gzip: 1.19 kB
dist/assets/DialogSceneValue-2e1f0561.js 3.09 kB │ gzip: 1.19 kB
dist/assets/ColumnFilter-f596e913.js 3.50 kB │ gzip: 1.21 kB
dist/assets/UserCodeTable-a07ee2ba.js 4.04 kB │ gzip: 1.59 kB
dist/assets/Login-ee6568c0.js 4.14 kB │ gzip: 1.64 kB
dist/assets/DialogAssociation-c39a4cc0.js 4.19 kB │ gzip: 1.51 kB
dist/assets/AssociationGroups-af9bbef7.js 4.34 kB │ gzip: 1.57 kB
dist/assets/ListInput-85c3a20f.js 4.39 kB │ gzip: 1.41 kB
dist/assets/mdi-084c837b.js 4.53 kB │ gzip: 1.58 kB
dist/assets/OTAUpdates-b247d973.js 5.13 kB │ gzip: 2.11 kB
dist/assets/Scenes-08e345f9.js 5.72 kB │ gzip: 1.94 kB
dist/assets/prismeditor.esm-e152e7ca.js 7.58 kB │ gzip: 2.70 kB
dist/assets/NodeScheduler-c414c1bc.js 7.86 kB │ gzip: 2.60 kB
dist/assets/HomeAssistant-fc1a7c7d.js 8.24 kB │ gzip: 2.43 kB
dist/assets/DialogGatewayValue-a7c00152.js 8.29 kB │ gzip: 2.51 kB
dist/assets/ControlPanel-74ff08b8.js 9.49 kB │ gzip: 3.47 kB
dist/assets/SmartView-1899ed43.js 9.89 kB │ gzip: 3.24 kB
dist/assets/ValueId-0e8f34fa.js 10.46 kB │ gzip: 2.94 kB
dist/assets/Store-231d6e2b.js 10.86 kB │ gzip: 3.36 kB
dist/assets/NodeDetails-1820e120.js 12.13 kB │ gzip: 3.36 kB
dist/assets/DialogHealthCheck-d28ab667.js 12.39 kB │ gzip: 3.59 kB
dist/assets/SmartStart-f9f35047.js 12.78 kB │ gzip: 3.78 kB
dist/assets/ExpandedNode-743c468a.js 14.94 kB │ gzip: 5.04 kB
dist/assets/NodePanel-fd986df9.js 15.39 kB │ gzip: 4.23 kB
dist/assets/Debug-11bae7d8.js 16.32 kB │ gzip: 4.18 kB
dist/assets/QrReader-d8ca055c.js 20.90 kB │ gzip: 7.30 kB
dist/assets/index-53d16c3c.js 20.98 kB │ gzip: 6.09 kB
dist/assets/qr-scanner-worker.min-5f44a019.js 43.95 kB │ gzip: 10.46 kB
dist/assets/BgRssiChart-a01008ec.js 54.99 kB │ gzip: 24.30 kB
dist/assets/vuedraggable.umd-b2555fab.js 71.04 kB │ gzip: 24.90 kB
dist/assets/Settings-a3fd37e5.js 74.67 kB │ gzip: 18.68 kB
dist/assets/index-3ffbe5b4.js 104.95 kB │ gzip: 43.04 kB
dist/assets/ZwaveGraph-3ad437c8.js 561.14 kB │ gzip: 166.36 kB
dist/assets/index-789e5769.js 1,178.07 kB │ gzip: 324.42 kB
(!) Some chunks are larger than 500 kBs after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
vite v4.5.3 building for production...
transforming...
✓ 65 modules transformed.
rendering chunks...
computing gzip size...
dist/sw.js 43.54 kB │ gzip: 12.25 kB
✓ built in 6.25s
PWA v0.16.7
mode injectManifest
precache 73 entries (3171.07 KiB)
files generated
dist/sw.js
✓ built in 3m 31s
Done in 285.94s.
+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md api certs dist docker docs esbuild-register.js esbuild.js genereteDocs.ts index.html kubernetes kustomization.yaml node_modules nodemon.json package-lock.json package.json package.sh pkg public server server_config.js snippets src store test tsconfig.eslint.json tsconfig.json vite.config.js wallaby.js yarn.lock
+ '[' -e /dev/ttyAMA0 ']'
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=a02082
+ [[ a02082 == \a\0\2\0\8\2 ]]
+ systemctl disable hciuart
Unit /etc/systemd/system/hciuart.service is masked, ignoring.
++ grep dtoverlay=pi3-miniuart-bt /boot/config.txt
+ [[ ! -n '' ]]
+ echo 'Raspberry Pi 3 Detected. If you use a Razberry board you must Disable Bluetooth'
Raspberry Pi 3 Detected. If you use a Razberry board you must Disable Bluetooth
+ echo 'Please add '\''dtoverlay=pi3-miniuart-bt'\'' to the end of the file /boot/config.txt'
Please add 'dtoverlay=pi3-miniuart-bt' to the end of the file /boot/config.txt
+ echo 'And reboot your Raspberry Pi'
And reboot your Raspberry Pi
+ echo 'Everything is successfully installed!'
Everything is successfully installed!
+ echo 11
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
+ echo 12
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************
