ZwaveJS fonctionne par intermittence : souci mqtt avec authentication et noeud dead

Plugins Protocole domotique
1

Bonjour,

Pour commencer voici ma config :
raspi 3B+, carte RaZberry Zwave+ branchée sur ports GPIO

Je viens de migrer d’un raspi 2B avec plugin Openzwave, plus moyen de refaire marcher ZwaveJS, la carte SD lâchait, donc j’ai réinstallé un debian 11, le driver Zway de zwave.me puis Jeedom puis j’ai fait la restauration du backup, réinstallé les dépendances plusieurs fois.

image
image1894×857 91.9 KB

Les 3 plugins NOK sont zwave (le legacy ozw), alexa API, et WebOS TV, donc rien à voir je pense avec mon souci.

La config du plugin :

image
image1698×719 93.8 KB

Dure à capturer car la fenêtre saute au bout de 5 secondes :-/ (quand le démon tourne, s’il est arrêté j’ai une chance de la garder)
Log du démon

yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-02 11:09:14.802e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-02 11:09:14.812e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-02 11:09:14.868e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
e[90m2024-09-02 11:09:26.394e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 11:09:26.397e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 11:09:26.398e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
...

e[90m2024-09-02 11:09:26.804e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 11:09:26.805e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 11:09:42.026e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: [Node 061] Interview FAILED: The node is dead
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command

Logs de dépendances, je vois que j’ai des erreurs à la fin… Mais un statut global à OK

+ 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
+ echo 4
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
+ 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 bullseye InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Reading package lists...
Building dependency tree...
Reading state information...
3 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 bullseye InRelease
Hit:3 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Hit:4 https://download.docker.com/linux/debian bullseye InRelease
Hit:5 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).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
[Check Version NodeJS actuelle : v18.20.4 : [  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 bullseye InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
[Check Version NodeJS actuelle : v18.20.4 : [  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 bullseye InRelease
Hit:3 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Hit:4 https://download.docker.com/linux/debian bullseye InRelease
Hit:5 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).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
[Check Version NodeJS actuelle : v18.20.4 : [  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-09-02 10:44:48--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
0K .......... .......... .......... .......... .......... 87% 2.35M 0s
50K .......                                               100% 28.6M=0.02s
2024-09-02 10:44:48 (2.65 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.8) 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 6s
+ 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 add zwavejs --network-timeout 300000
yarn add v1.22.22
warning ../package.json: No license field
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 > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
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
error Error: https://registry.yarnpkg.com/zwavejs: Not found
at params.callback [as _callback] (/usr/lib/node_modules/yarn/lib/cli.js:66680:18)
at self.callback (/usr/lib/node_modules/yarn/lib/cli.js:141410:22)
at Request.emit (node:events:517:28)
at Request.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:142382:10)
at Request.emit (node:events:517:28)
at IncomingMessage.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:142304:12)
at Object.onceWrapper (node:events:631:28)
at IncomingMessage.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
+ sudo yarn add zwave-js-ui --network-timeout 300000
yarn add v1.22.22
warning ../package.json: No license field
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
warning zwave-js-ui > csurf@1.11.0: Please use another csrf package
warning zwave-js-ui > vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > @zwave-js/server@1.38.0" has incorrect peer dependency "zwave-js@^13.2.0".
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.
success Saved 867 new dependencies.
info Direct dependencies
├─ @actions/github@6.0.0
├─ @babel/register@7.24.6
├─ @mdi/js@7.3.67
├─ @release-it/conventional-changelog@7.0.2
├─ @tsconfig/node18@18.2.4
├─ @types/archiver@5.3.4
├─ @types/chai-as-promised@7.1.8
├─ @types/connect-history-api-fallback@1.5.4
├─ @types/csurf@1.11.5
├─ @types/express-rate-limit@5.1.3
├─ @types/express-session@1.17.9
├─ @types/extract-zip@2.0.1
├─ @types/fs-extra@11.0.4
├─ @types/jsonfile@6.1.4
├─ @types/jsonwebtoken@9.0.6
├─ @types/mocha@10.0.7
├─ @types/morgan@1.9.9
├─ @types/multer@1.4.12
├─ @types/node@20.16.3
├─ @types/proxyquire@1.3.31
├─ @types/sinon-chai@3.2.12
├─ @typescript-eslint/eslint-plugin@6.21.0
├─ @typescript-eslint/parser@6.21.0
├─ @vitejs/plugin-vue2@2.3.1
├─ @yao-pkg/pkg@5.12.1
├─ @zwave-js/server@1.38.0
├─ archiver@6.0.2
├─ c8@8.0.1
├─ chai-as-promised@7.1.2
├─ chai@4.5.0
├─ conventional-changelog-cli@4.1.0
├─ croner@7.0.8
├─ cronstrue@2.50.0
├─ docsify-cli@4.4.4
├─ docsify@4.13.1
├─ dotenv@16.4.5
├─ esbuild-register@3.6.0
├─ esbuild@0.19.12
├─ eslint-config-prettier@9.1.0
├─ eslint-plugin-babel@5.3.1
├─ eslint-plugin-import@2.29.1
├─ eslint-plugin-node@11.1.0
├─ eslint-plugin-prettier@5.2.1
... // Je me suis permis de tronquer car trop de caractères dans le post !
├─ write-file-atomic@3.0.3
├─ xml-name-validator@4.0.0
├─ xmlhttprequest-ssl@2.0.0
├─ xtend@4.0.2
├─ yallist@3.1.1
├─ yargonaut@1.1.4
├─ yargs-parser@21.1.1
├─ yargs-unparser@2.0.0
├─ yauzl@2.10.0
├─ yn@3.1.1
├─ yocto-queue@0.1.0
├─ zip-stream@5.0.2
├─ zwave-js-ui@9.18.0
└─ zwave-js@12.13.1
Done in 457.65s.
+ sudo yarn install
yarn install v1.22.22
warning ../package.json: No license field
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...
success Already up-to-date.
Done in 6.22s.
+ sudo NODE_OPTIONS=--max_old_space_size=4096
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
[command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-D directory] [-g group]
[-h host] [-p prompt] [-R directory] [-T timeout] [-u user]
[VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-D directory] [-g group]
[-h host] [-p prompt] [-R directory] [-T timeout] [-u user] file ...
+ sudo yarn run build
yarn run v1.22.22
warning ../package.json: No license field
$ npm-run-all 'build:*'
warning ../package.json: No license field
$ tsc
warning ../package.json: No license field
$ vite build
vite v4.5.3 building for production...
transforming...
✓ 577 modules transformed.
<--- Last few GCs --->
[24118:0x4262918]   180408 ms: Mark-sweep (reduce) 223.8 (236.4) -> 223.2 (235.9) MB, 3002.5 / 0.0 ms  (average mu = 0.616, current mu = 0.034) allocation failure; scavenge might not succeed
[24118:0x4262918]   183036 ms: Mark-sweep (reduce) 223.8 (236.3) -> 223.7 (236.6) MB, 2618.0 / 0.0 ms  (average mu = 0.465, current mu = 0.004) background allocation failure; GC in old space requested
<--- JS stacktrace --->
FATAL ERROR: Reached 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 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 ']'
+ sudo sed -i 's/console=ttyAMA0,115200//; s/kgdboc=ttyAMA0,115200//' /boot/cmdline.txt
+ sudo sed -i 's|[^:]*:[^:]*:respawn:/sbin/getty[^:]*ttyAMA0[^:]*||' /etc/inittab
sed: can't read /etc/inittab: No such file or directory
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
+ sudo systemctl mask serial-getty@ttyAMA0.service
+ sudo systemctl stop serial-getty@ttyAMA0.service
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=a02082
+ [[ a02082 == \a\0\2\0\8\2 ]]
+ systemctl disable hciuart
++ grep dtoverlay=pi3-miniuart-bt /boot/config.txt
+ [[ ! -n dtoverlay=pi3-miniuart-bt ]]
+ 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******************

et log du plugin :

[2024-09-02 11:00:23] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-02 11:00:23] INFO  : Arrêt du démon ZwaveJS
[2024-09-02 11:00:23] DEBUG  : [configureSettings] Informations reçues de MQTT Manager : {"ip":"192.168.1.14","port":"1883","protocol":"mqtt","user":"dom","password":"XXXXXXX"}
[2024-09-02 11:00:23] INFO  : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=04A1E702011B72D030B9945788063A0B KEY_S2_Unauthenticated=32ECD6F226E7D9138D090204888E8B4F KEY_S2_Authenticated=7BD3537AEB2807FE9F435C7687BA476A KEY_S2_AccessControl=D6385462398B6F3402B9940863E2B488 SESSION_SECRET=jeedomSession yarn start
[2024-09-02 11:05:06] DEBUG  : [refreshIfNeeded] 37/0/targetValue false
[2024-09-02 11:06:48] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-02 11:06:48] INFO  : Arrêt du démon ZwaveJS
[2024-09-02 11:06:48] DEBUG  : [configureSettings] Informations reçues de MQTT Manager : {"ip":"192.168.1.14","port":"1883","protocol":"mqtt","user":"dom","password":"XXXXXXXX"}
[2024-09-02 11:06:48] INFO  : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=04A1E702011B72D030B9945788063A0B KEY_S2_Unauthenticated=32ECD6F226E7D9138D090204888E8B4F KEY_S2_Authenticated=7BD3537AEB2807FE9F435C7687BA476A KEY_S2_AccessControl=D6385462398B6F3402B9940863E2B488 SESSION_SECRET=jeedomSession yarn start
[2024-09-02 11:08:56] INFO  : Arrêt du démon ZwaveJS
[2024-09-02 11:09:05] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-02 11:09:05] INFO  : Arrêt du démon ZwaveJS
[2024-09-02 11:09:06] DEBUG  : [configureSettings] Informations reçues de MQTT Manager : {"ip":"192.168.1.14","port":"1883","protocol":"mqtt","user":"dom","password":"XXXXXXXXX"}
[2024-09-02 11:09:06] INFO  : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=04A1E702011B72D030B9945788063A0B KEY_S2_Unauthenticated=32ECD6F226E7D9138D090204888E8B4F KEY_S2_Authenticated=7BD3537AEB2807FE9F435C7687BA476A KEY_S2_AccessControl=D6385462398B6F3402B9940863E2B488 SESSION_SECRET=jeedomSession yarn start

Les symptomes : Message du driver non initialisé, la page de config du plugin saute au bout de quelques secondes… Et les modules Zwave marchotent, par intermittence (logique dans le sens où le démon ne cesse de redémarrer)
Zwavejs---Jeedom 2

A priori je viens de voir sur un autre sujet que ce pourrait être du au driver Zwave.me… Je vais tenter de le désinstaller.
Merci à tous pour votre temps

2

J’ai désinstallé le driver zway, reboot, et relancé les dépendances. Même log j’ai l’impression, statut OK malgré un fail du build, j’ai pourtant augmenté le swap à 1Go et modifié la variable dans le post_install:

sudo yarn install
sudo NODE_OPTIONS="--max_old_space_size=2048"
sudo yarn run build

+ 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
+ echo 4
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
+ 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 bullseye InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
8 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 bullseye InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
The following packages were automatically installed and are no longer required:
libavahi-client-dev libavahi-common-dev libavahi-compat-libdnssd-dev
libavahi-compat-libdnssd1 libc-ares2 libdbus-1-dev libev4 libmosquitto1
libwebsockets16 sharutils
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
[Check Version NodeJS actuelle : v18.20.4 : [  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 bullseye InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Hit:5 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).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
The following packages were automatically installed and are no longer required:
libavahi-client-dev libavahi-common-dev libavahi-compat-libdnssd-dev
libavahi-compat-libdnssd1 libc-ares2 libdbus-1-dev libev4 libmosquitto1
libwebsockets16 sharutils
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
[Check Version NodeJS actuelle : v18.20.4 : [  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 bullseye InRelease
Hit:3 https://download.docker.com/linux/debian bullseye InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 https://repo.z-wave.me/z-way/raspbian bullseye InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0+rpi1).
The following packages were automatically installed and are no longer required:
libavahi-client-dev libavahi-common-dev libavahi-compat-libdnssd-dev
libavahi-compat-libdnssd1 libc-ares2 libdbus-1-dev libev4 libmosquitto1
libwebsockets16 sharutils
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
[Check Version NodeJS actuelle : v18.20.4 : [  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-09-02 17:18:05--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'
0K .......... .......... .......... .......... .......... 87% 2.15M 0s
50K .......                                               100% 20.3M=0.02s
2024-09-02 17:18:06 (2.42 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.8) 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 6s
+ 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 add zwavejs --network-timeout 300000
yarn add v1.22.22
warning ../package.json: No license field
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 > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
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
error Error: https://registry.yarnpkg.com/zwavejs: Not found
at params.callback [as _callback] (/usr/lib/node_modules/yarn/lib/cli.js:66680:18)
at self.callback (/usr/lib/node_modules/yarn/lib/cli.js:141410:22)
at Request.emit (node:events:517:28)
at Request.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:142382:10)
at Request.emit (node:events:517:28)
at IncomingMessage.<anonymous> (/usr/lib/node_modules/yarn/lib/cli.js:142304:12)
at Object.onceWrapper (node:events:631:28)
at IncomingMessage.emit (node:events:529:35)
at endReadableNT (node:internal/streams/readable:1400:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
+ sudo yarn add zwave-js-ui --network-timeout 300000
yarn add v1.22.22
warning ../package.json: No license field
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 > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
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
warning zwave-js-ui > csurf@1.11.0: Please use another csrf package
warning zwave-js-ui > vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > @zwave-js/server@1.38.0" has incorrect peer dependency "zwave-js@^13.2.0".
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.
success Saved 867 new dependencies.
info Direct dependencies
├─ @actions/github@6.0.0
├─ @babel/register@7.24.6
├─ @mdi/js@7.3.67
├─ @release-it/conventional-changelog@7.0.2
├─ @tsconfig/node18@18.2.4
├─ @types/archiver@5.3.4
├─ @types/chai-as-promised@7.1.8
├─ @types/connect-history-api-fallback@1.5.4
....
├─ zip-stream@5.0.2
├─ zwave-js-ui@9.18.0
└─ zwave-js@12.13.1
Done in 459.14s.
+ sudo yarn install
yarn install v1.22.22
warning ../package.json: No license field
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...
success Already up-to-date.
Done in 9.82s.
+ sudo NODE_OPTIONS=--max_old_space_size=2048
usage: sudo -h | -K | -k | -V
usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
[command]
usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-D directory] [-g group]
[-h host] [-p prompt] [-R directory] [-T timeout] [-u user]
[VAR=value] [-i|-s] [<command>]
usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-D directory] [-g group]
[-h host] [-p prompt] [-R directory] [-T timeout] [-u user] file ...
+ sudo yarn run build
yarn run v1.22.22
warning ../package.json: No license field
$ npm-run-all 'build:*'
warning ../package.json: No license field
$ tsc
warning ../package.json: No license field
$ vite build
vite v4.5.3 building for production...
transforming...
<--- Last few GCs --->
[16055:0x5b56918]   202831 ms: Mark-sweep 219.3 (235.1) -> 217.0 (235.1) MB, 3092.2 / 0.0 ms  (average mu = 0.175, current mu = 0.109) allocation failure; scavenge might not succeed
[16055:0x5b56918]   207935 ms: Mark-sweep 219.3 (235.1) -> 217.1 (235.3) MB, 4847.1 / 0.0 ms  (average mu = 0.101, current mu = 0.050) 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 ']'
+ sudo sed -i 's/console=ttyAMA0,115200//; s/kgdboc=ttyAMA0,115200//' /boot/cmdline.txt
+ sudo sed -i 's|[^:]*:[^:]*:respawn:/sbin/getty[^:]*ttyAMA0[^:]*||' /etc/inittab
sed: can't read /etc/inittab: No such file or directory
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
+ sudo systemctl mask serial-getty@ttyAMA0.service
+ sudo systemctl stop serial-getty@ttyAMA0.service
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=a02082
+ [[ a02082 == \a\0\2\0\8\2 ]]
+ systemctl disable hciuart
++ grep dtoverlay=pi3-miniuart-bt /boot/config.txt
+ [[ ! -n dtoverlay=pi3-miniuart-bt ]]
+ 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******************
3

Bon ça progresse, après avoir tenté de nouvelles commandes relatives au swap, cette fois l’installation des dépendances s’est passée - sauf si j’ai loupé un truc - tout à fait bien, pour de bon.

─ yocto-queue@0.1.0
├─ zip-stream@5.0.2
├─ zwave-js-ui@9.18.0
└─ zwave-js@12.13.1
Done in 456.32s.
+ sudo yarn install
yarn install v1.22.22
warning ../package.json: No license field
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...
success Already up-to-date.
Done in 9.61s.
+ sudo NODE_OPTIONS=--max_old_space_size=2048 yarn run build
yarn run v1.22.22
warning ../package.json: No license field
$ npm-run-all 'build:*'
warning ../package.json: No license field
$ tsc
warning ../package.json: No license field
$ 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-c61f7084.js                         0.26 kB │ gzip:   0.20 kB
dist/assets/ControllerChart-ac3995bb.js               0.54 kB │ gzip:   0.34 kB
dist/assets/ColumnFilterBoolean-42e1d870.js           0.70 kB │ gzip:   0.43 kB
dist/assets/ReinterviewBadge-b23659ae.js              0.77 kB │ gzip:   0.51 kB
dist/assets/BlinkIcon-7531df87.js                     0.86 kB │ gzip:   0.42 kB
dist/assets/MissingKeysAlert-7a9d8cf2.js              1.18 kB │ gzip:   0.56 kB
dist/assets/ColumnFilterDate-f6968704.js              1.20 kB │ gzip:   0.57 kB
dist/assets/ColumnFilterString-b8d711ab.js            1.26 kB │ gzip:   0.63 kB
dist/assets/DialogAdvanced-9ad1aaf1.js                1.31 kB │ gzip:   0.68 kB
dist/assets/StatisticsArrows-02b52a8b.js              1.35 kB │ gzip:   0.73 kB
dist/assets/ErrorPage-0a0f6e23.js                     1.56 kB │ gzip:   0.79 kB
dist/assets/ColumnFilterNumber-7a3706f5.js            1.77 kB │ gzip:   0.75 kB
dist/assets/file-input-8b7d131c.js                    1.84 kB │ gzip:   0.86 kB
dist/assets/RichValue-c9000e32.js                     2.06 kB │ gzip:   0.87 kB
dist/assets/StatisticsCard-7026b532.js                2.56 kB │ gzip:   1.00 kB
dist/assets/Mesh-fe411d3f.js                          2.87 kB │ gzip:   1.19 kB
dist/assets/DialogSceneValue-f98fe1fe.js              3.09 kB │ gzip:   1.18 kB
dist/assets/ColumnFilter-557c4aa7.js                  3.50 kB │ gzip:   1.21 kB
dist/assets/UserCodeTable-ea568970.js                 4.04 kB │ gzip:   1.59 kB
dist/assets/Login-6bac7517.js                         4.14 kB │ gzip:   1.64 kB
dist/assets/DialogAssociation-f928d131.js             4.19 kB │ gzip:   1.51 kB
dist/assets/AssociationGroups-16d25fe8.js             4.34 kB │ gzip:   1.57 kB
dist/assets/ListInput-f63a04fd.js                     4.39 kB │ gzip:   1.41 kB
dist/assets/mdi-084c837b.js                           4.53 kB │ gzip:   1.58 kB
dist/assets/OTAUpdates-d1b603ed.js                    5.13 kB │ gzip:   2.11 kB
dist/assets/Scenes-34f5f703.js                        5.72 kB │ gzip:   1.93 kB
dist/assets/prismeditor.esm-b7e19e8f.js               7.58 kB │ gzip:   2.69 kB
dist/assets/NodeScheduler-e5a6be9a.js                 7.86 kB │ gzip:   2.60 kB
dist/assets/HomeAssistant-56f433d3.js                 8.24 kB │ gzip:   2.43 kB
dist/assets/DialogGatewayValue-5dd1adc4.js            8.29 kB │ gzip:   2.51 kB
dist/assets/ControlPanel-79e40db4.js                  9.49 kB │ gzip:   3.47 kB
dist/assets/SmartView-43100dc1.js                     9.89 kB │ gzip:   3.24 kB
dist/assets/ValueId-7616b4ae.js                      10.46 kB │ gzip:   2.94 kB
dist/assets/Store-1c5dbee0.js                        10.86 kB │ gzip:   3.36 kB
dist/assets/NodeDetails-cdbef06f.js                  12.13 kB │ gzip:   3.36 kB
dist/assets/DialogHealthCheck-d5bd9dce.js            12.39 kB │ gzip:   3.59 kB
dist/assets/SmartStart-70c128ec.js                   12.78 kB │ gzip:   3.78 kB
dist/assets/ExpandedNode-8c1f1b32.js                 14.94 kB │ gzip:   5.04 kB
dist/assets/NodePanel-eef2b2bb.js                    15.39 kB │ gzip:   4.23 kB
dist/assets/Debug-372ace54.js                        16.32 kB │ gzip:   4.18 kB
dist/assets/QrReader-fff27988.js                     20.90 kB │ gzip:   7.30 kB
dist/assets/index-588b9cda.js                        20.98 kB │ gzip:   6.08 kB
dist/assets/qr-scanner-worker.min-5f44a019.js        43.95 kB │ gzip:  10.46 kB
dist/assets/BgRssiChart-424d495b.js                  54.99 kB │ gzip:  24.30 kB
dist/assets/vuedraggable.umd-31440641.js             71.04 kB │ gzip:  24.90 kB
dist/assets/Settings-040f8116.js                     74.67 kB │ gzip:  18.68 kB
dist/assets/index-86c0f865.js                       104.95 kB │ gzip:  43.04 kB
dist/assets/ZwaveGraph-43114e71.js                  561.14 kB │ gzip: 166.35 kB
dist/assets/index-c718ba2f.js                     1,179.73 kB │ gzip: 325.11 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 2.60s
PWA v0.16.7
mode      injectManifest
precache  73 entries (3172.69 KiB)
files generated
dist/sw.js
✓ built in 3m 2s
Done in 267.40s.
+ 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 ']'
+ sudo sed -i 's/console=ttyAMA0,115200//; s/kgdboc=ttyAMA0,115200//' /boot/cmdline.txt
+ sudo sed -i 's|[^:]*:[^:]*:respawn:/sbin/getty[^:]*ttyAMA0[^:]*||' /etc/inittab
sed: can't read /etc/inittab: No such file or directory
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
+ sudo systemctl mask serial-getty@ttyAMA0.service
+ sudo systemctl stop serial-getty@ttyAMA0.service
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=a02082
+ [[ a02082 == \a\0\2\0\8\2 ]]
+ systemctl disable hciuart
++ grep dtoverlay=pi3-miniuart-bt /boot/config.txt
+ [[ ! -n dtoverlay=pi3-miniuart-bt ]]
+ 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******************

Malheureusement, le démon plante, on dirait qu’il a un souci avec MQTT, bizarre…

yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-02 18:18:41.548e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-02 18:18:41.558e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-02 18:18:41.617e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
e[90m2024-09-02 18:19:17.572e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.577e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.579e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.580e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.581e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.582e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.583e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.585e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.586e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.588e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.589e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.590e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.591e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.592e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.593e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.594e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.596e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.596e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.597e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.598e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.600e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.601e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.602e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.603e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.604e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.605e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.606e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.607e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.608e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.609e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.609e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.610e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.611e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.612e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.613e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.613e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.614e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.615e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.616e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.616e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.617e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.618e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.619e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.620e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.620e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.621e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.622e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.623e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.623e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.624e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.625e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.626e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.626e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.627e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.628e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.629e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.630e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.631e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.631e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.632e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.633e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.634e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.634e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.635e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:17.636e[39m e[31mERRORe[39m e[1mMQTTe[22m: Error while publishing a value Connection closed
e[90m2024-09-02 18:19:22.459e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
e[90m2024-09-02 18:19:27.260e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
e[90m2024-09-02 18:19:35.429e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: [Node 061] Interview FAILED: The node is dead
e[90m2024-09-02 18:20:02.528e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
e[90m2024-09-02 18:20:04.552e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
e[90m2024-09-02 18:20:06.619e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
e[90m2024-09-02 18:20:08.713e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
e[90m2024-09-02 18:20:10.835e[39m e[31mERRORe[39m e[1mMQTTe[22m: Mqtt client error write EPIPE
Error: write EPIPE
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:94:16)
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
4

Je me demande si cela n’est pas dû à l’authentification mqtt… Je tape sur un broker mosquitto remote (hébergé sur mon nas), ceci dit lorsque j’exposais les équipements via mqtt cela ne posait aucun problème pour mon autre jeedom pour les voir, donc je n’ai pas l’impression qu’il y ait un souci en lui-même au niveau mqtt, mais davantage à la façon donc zwaveJS communique avec mqtt.

5

Petit update car concrètement j’avais 2 symptomes :

    • Le « clignotement / refresh » de la page de configuration du plugin zwaveJS : j’ai basculé sur un broker local (via docker) de jeedom, le problème a disparu. Curieusement, sur mon autre instance jeedom, je n’ai jamais eu le souci avec zwaveJS et le broquer mosquitto sur mon nas, et après les dernières maj de plugin j’ai également le souci sur cette instance. Donc il y a bien un truc qui ne se fait plus comme avant entre zwaveJS et mqtt.
  2. Le plantage récurrent du démon ZwaveJS : il se passait après la tentative de réinterview d’un module inclus sous openzwave qui n’est plus branché mais dans un carton. Je l’ai exclus, et j’ai moins de plantage, ça redevient utlisable, mais ça plante régulièrement, toutes les 5 min environ :
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 09:46:01.227e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 09:46:01.238e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 09:46:01.310e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 09:51:00.637e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 09:51:00.646e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 09:51:00.702e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 09:56:00.596e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 09:56:00.606e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 09:56:00.663e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 10:01:07.129e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 10:01:07.138e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 10:01:07.217e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
6

Bonjour,

Il serait bien de passer le niveau de log du demon en debug et le relancer.

En cas de plantage on aurait deja beaucoup plus d’informations car la :face_with_peeking_eye:

7

Pardon @lperenna j’avais zapé que je l’avais désactivé pour économiser un peu la carte sd :wink:
Je viens de le passer en debug, je refais un extract dans la journée… Merci pour ton intérêt :slight_smile:

8

bon, log du plugin :

[2024-09-03 10:29:18] DEBUG  : [controllerAction] Exécution d'une action sur le contrôleur de type : refreshNeighbors
[2024-09-03 10:30:57] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-03 10:30:57] INFO  : Arrêt du démon ZwaveJS
[2024-09-03 10:30:57] DEBUG  : [configureSettings] Informations reçues de MQTT Manager : {"ip":"127.0.0.1","port":"1883","protocol":"mqtt","user":"dom","password":"XXXX"}
[2024-09-03 10:30:57] INFO  : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=04A1E702011B72D030B9945788063A0B KEY_S2_Unauthenticated=32ECD6F226E7D9138D090204888E8B4F KEY_S2_Authenticated=7BD3537AEB2807FE9F435C7687BA476A KEY_S2_AccessControl=D6385462398B6F3402B9940863E2B488 SESSION_SECRET=jeedomSession yarn start
[2024-09-03 10:35:51] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-09-03 10:35:51] INFO  : Arrêt du démon ZwaveJS
[2024-09-03 10:35:51] DEBUG  : [configureSettings] Informations reçues de MQTT Manager : {"ip":"127.0.0.1","port":"1883","protocol":"mqtt","user":"dom","password":"XXXXXX"}
[2024-09-03 10:35:51] INFO  : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=04A1E702011B72D030B9945788063A0B KEY_S2_Unauthenticated=32ECD6F226E7D9138D090204888E8B4F KEY_S2_Authenticated=7BD3537AEB2807FE9F435C7687BA476A KEY_S2_AccessControl=D6385462398B6F3402B9940863E2B488 SESSION_SECRET=jeedomSession yarn start

Log du démon :

error Command failed with signal "SIGTERM".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 10:28:45.382e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 10:28:45.392e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 10:28:45.463e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 10:31:13.064e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 10:31:13.074e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 10:31:13.155e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
yarn run v1.22.22
warning ../package.json: No license field
$ node --preserve-symlinks server/bin/www.js
e[90m2024-09-03 10:36:00.917e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-09-03 10:36:00.927e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-09-03 10:36:00.996e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found

Pas très bavard quoi qu’il en soit :-/

9

Ce ne sont pas les logs du demon sur la dernier capture.

10

Ha ? Ce sont ces logs là :

image
image1562×395 48.1 KB

J’ai toujours pensé que ça correspondait au démon quand ça finit par « d ». Peux-tu me dire où les trouver en ce cas ?

11

Desolé je suis sur téléphone
Mais ca dans les dependances c pas ok.

Et le log du demon ne sont pas ceux ou on voit ecrit zwave en logo lettres

12

Tu n’as pas pris le tout dernier log des dépendances. Dans le dernier il n’y a plus de build exited, tout est vraiment OK.

Je n’ai que 3 logs possibles sur zwaveJS : dans l’ordre de gauche à droite :

  1. les logs du plugin
  2. Logs des dépendances
  3. Logs du démon
    image
    image1809×285 40.7 KB

    Soit tu confonds les logs du démon avec les logs du plugin, soit tu me parles d’un autre log que je ne connais pas. Dis-moi où je peux le trouver stp je te le partagerai avec plaisir si ça peut t’aider à m’aider :slight_smile:
13

Question bête mais le plugin openzwave est bien désactivé ?

14

Bonjour,

Pouvez vous remettre la valeur par défaut et tester ?
image

Donc zwave

15

Y a pas de question bête, déjà merci de m’épauler, je me sens moins démuni :wink:
Le démon, oui, il est éteint, mais le plugin, non. Je viens de le désactiver, des fois que cela change quelque chose. Normalement, selon la doc, les deux plugins peuvent coexister du moment que les deux démons ne tournent pas en même temps.

16

Re, j’ai passé en zwave la conf mqtt, j’ai passé en debug et redémarré le démon… puis j’ai joué avec 2 -3 équipements / volets etc… et en effet le démon ne plante plus !

  1. Un grand merci @lperenna
  2. Donc le souci serait lié à l’intégration mqtt de zwaveJS ? Je ne suis pas à la maison donc j’iignore si cela a fonctionné à distance mais y a pas de raison… Il faudrait le remonter à la team de dev du plugin si c’est réellement ça, comment on fait ?
17

Bonjour,

Vous avez modifié le préfixe mqtt dans le plugin zwavejs
Mais coté mqtt manager, on ne sait pas si le plugin abonné a été ok de ce fait

Donc avant de remonter quoique ce soit il faudrait déjà être sûr que tout aie été fait correctement.
Ce qui en l’état n’est pas sûr.

18

Tu as ben raison. Je partais du principe que le plugin zwaveJS communique sa conf au plugin mqtt2 et qu’il n’y a rien à faire côté mqtt.
je vais relire la doc côté mqtt et zwaveJS pour essayer de mieux comprendre… Autrement voici la conf de mon plugin mqtt

image
image780×241 18.7 KB

En l’état j’ai l’impression qu’il s’est bien abonné aux versions successives du préfixe mqtt que j’ai renseigné sur la config du plugin zwavejs…Mais je peux sans doute enlever celles qui ne servent plus ? ou alors je les supprime toutes et je relance le démon pour qu’il reparte d’une base vierge ?

19

J’enlèverai ce qui ne sert plus.

20

Et à votre avis, la config est problématique ? ce serait sans doute un bug à remonter, non ? Je passe votre proposition en solution