Problème avec le plugin zwave-js depuis changement de box

Bonjour à tous, j’ai cherché sur le forum mais pas de réponse à mon cas, si je me trompe je m’en excuse par avance.

Je possédais (je l’ai toujours) une jeedom smart et le zwave a toujours fonctionné depuis l’origine (openzwave puis zwave-js). Je voulais passer à l’Atlas mais son manque de disponibilité m’a incité à prendre un Rockpi 4b+ en remplacement et j’ai récupéré le module zwave de la smart pour le remettre sur le roxkpi comme d’autres l’ont fait avec l’Atlas comme @Lydie13 par exemple. Pour installer Debian sur le Rockpi j’ai suivi le tuto d’ @akenad [RTEX] Rock Pi4B+ - eMMC - Armbian Bullseye - Jeedom V4 et tout s’est bien déroulé. J’ai ensuite modifié la version de Python pour la passer en 3.12.2 pour éviter les éventuels problèmes de fuites mémoire évoquées avec la version 3.9 (cela peut il avoir une incidence sur zwave-js?).

Dans la configuration j’ai changé le port pour mettre celui de l’Atlas dev/ttys2 (le ttys1 ne fonctionne pas du tout). Depuis ce changement zwave-js fonctionne parfois mais le plus souvent il est hs, j’ai le bandeau orange en haut en permanence alors que le démon est bien en vert.

voici la page santé de jeedom

Le log des dépendances:

+ 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://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Get:3 http://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]
Get:4 http://security.debian.org bullseye-security InRelease [48.4 kB]
Get:5 http://mirror.vinehost.net/armbian/apt bullseye InRelease [53.3 kB]
Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease
Get:7 http://mirror.vinehost.net/armbian/apt bullseye/main armhf Packages [84.8 kB]
Get:8 http://mirror.vinehost.net/armbian/apt bullseye/main arm64 Packages [230 kB]
Get:9 http://mirror.vinehost.net/armbian/apt bullseye/main all Packages [1959 B]
Get:10 http://mirror.vinehost.net/armbian/apt bullseye/main arm64 Contents (deb) [5857 kB]
Get:11 http://mirror.vinehost.net/armbian/apt bullseye/main armhf Contents (deb) [2118 kB]
Get:12 http://mirror.vinehost.net/armbian/apt bullseye/main all Contents (deb) [30.2 kB]
Get:13 http://mirror.vinehost.net/armbian/apt bullseye/bullseye-utils arm64 Packages [6363 B]
Get:14 http://mirror.vinehost.net/armbian/apt bullseye/bullseye-utils all Packages [1963 B]
Get:15 http://mirror.vinehost.net/armbian/apt bullseye/bullseye-utils armhf Packages [15.8 kB]
Get:16 http://mirror.vinehost.net/armbian/apt bullseye/bullseye-utils arm64 Contents (deb) [3868 B]
Get:17 http://mirror.vinehost.net/armbian/apt bullseye/bullseye-utils armhf Contents (deb) [4558 B]
Fetched 8550 kB in 6s (1520 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
17 packages can be upgraded. Run 'apt list --upgradable' to see them.
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Get:5 http://imola.armbian.com/apt bullseye InRelease [53.3 kB]
Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease
Get:7 http://imola.armbian.com/apt bullseye/bullseye-utils armhf Packages [8778 B]
Fetched 62.1 kB in 3s (24.1 kB/s)
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).
The following packages were automatically installed and are no longer required:
libc-ares2 libuv1-dev
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[Check Version NodeJS actuelle : v18.20.3 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Hit:5 http://imola.armbian.com/apt bullseye InRelease
Hit:6 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).
The following packages were automatically installed and are no longer required:
libc-ares2 libuv1-dev
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[Check Version NodeJS actuelle : v18.20.3 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 http://imola.armbian.com/apt bullseye InRelease
Hit:6 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).
The following packages were automatically installed and are no longer required:
libc-ares2 libuv1-dev
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[Check Version NodeJS actuelle : v18.20.3 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
--2024-05-26 22:13:08--  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% 4.53M 0s
50K .......                                               100% 48.7M=0.01s
2024-05-26 22:13:09 (5.10 MB/s) - 'composer-setup.php' saved [58444/58444]
Begin installation of composer
All settings correct for using Composer
Downloading...
Composer (version 2.7.6) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
added 110 packages, and audited 111 packages in 4s
14 packages are looking for funding
run `npm fund` for details
3 moderate severity vulnerabilities
To address all issues, run:
npm audit fix
Run `npm audit` for details.
+ 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
+ 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 http://fi.mirror.armbian.de/apt bullseye InRelease
Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
17 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://security.debian.org bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Hit:5 http://fi.mirror.armbian.de/apt bullseye InRelease
Hit:6 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).
The following packages were automatically installed and are no longer required:
libc-ares2 libuv1-dev
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[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://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Hit:5 http://imola.armbian.com/apt bullseye InRelease
Hit:6 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).
The following packages were automatically installed and are no longer required:
libc-ares2 libuv1-dev
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 http://imola.armbian.com/apt bullseye InRelease
Hit:6 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).
The following packages were automatically installed and are no longer required:
libc-ares2 libuv1-dev
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded.
[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-05-26 22:13:53--  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% 4.70M 0s
50K .......                                               100% 62.5M=0.01s
2024-05-26 22:13:54 (5.31 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.6) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
+ echo 9
+ sudo npm install --force -g yarn
npm warn using --force Recommended protections disabled.
changed 1 package in 3s
+ 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 > 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
[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 121.39s.
+ sudo 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-7cf72018.js                         0.26 kB │ gzip:   0.20 kB
dist/assets/ControllerChart-1825f094.js               0.54 kB │ gzip:   0.34 kB
dist/assets/ColumnFilterBoolean-49fe237a.js           0.70 kB │ gzip:   0.43 kB
dist/assets/ReinterviewBadge-cdef9c95.js              0.77 kB │ gzip:   0.51 kB
dist/assets/BlinkIcon-d4a7c296.js                     0.86 kB │ gzip:   0.42 kB
dist/assets/MissingKeysAlert-db249ae8.js              1.18 kB │ gzip:   0.56 kB
dist/assets/ColumnFilterDate-83f65348.js              1.20 kB │ gzip:   0.57 kB
dist/assets/ColumnFilterString-365cb160.js            1.26 kB │ gzip:   0.63 kB
dist/assets/DialogAdvanced-93b63b88.js                1.31 kB │ gzip:   0.68 kB
dist/assets/StatisticsArrows-713d2f5d.js              1.35 kB │ gzip:   0.73 kB
dist/assets/ErrorPage-cfb7291e.js                     1.56 kB │ gzip:   0.79 kB
dist/assets/ColumnFilterNumber-82c87122.js            1.77 kB │ gzip:   0.75 kB
dist/assets/file-input-a40d1adf.js                    1.84 kB │ gzip:   0.86 kB
dist/assets/RichValue-24a77ce9.js                     2.06 kB │ gzip:   0.87 kB
dist/assets/StatisticsCard-33130007.js                2.56 kB │ gzip:   1.00 kB
dist/assets/Mesh-881e56e4.js                          2.87 kB │ gzip:   1.19 kB
dist/assets/DialogSceneValue-d8d2d699.js              3.09 kB │ gzip:   1.19 kB
dist/assets/ColumnFilter-205965e4.js                  3.50 kB │ gzip:   1.21 kB
dist/assets/UserCodeTable-704f0f41.js                 4.04 kB │ gzip:   1.59 kB
dist/assets/Login-bd8093ed.js                         4.14 kB │ gzip:   1.64 kB
dist/assets/DialogAssociation-66d805ac.js             4.19 kB │ gzip:   1.51 kB
dist/assets/AssociationGroups-908b5763.js             4.34 kB │ gzip:   1.57 kB
dist/assets/ListInput-4f610f22.js                     4.39 kB │ gzip:   1.41 kB
dist/assets/mdi-084c837b.js                           4.53 kB │ gzip:   1.58 kB
dist/assets/OTAUpdates-8d03e051.js                    5.13 kB │ gzip:   2.11 kB
dist/assets/Scenes-af7460b9.js                        5.72 kB │ gzip:   1.94 kB
dist/assets/prismeditor.esm-22b00d2c.js               7.58 kB │ gzip:   2.69 kB
dist/assets/NodeScheduler-6071c02f.js                 7.86 kB │ gzip:   2.60 kB
dist/assets/HomeAssistant-09c636e3.js                 8.24 kB │ gzip:   2.43 kB
dist/assets/DialogGatewayValue-46803067.js            8.29 kB │ gzip:   2.51 kB
dist/assets/ControlPanel-a8417571.js                  9.49 kB │ gzip:   3.47 kB
dist/assets/SmartView-40284512.js                     9.89 kB │ gzip:   3.24 kB
dist/assets/ValueId-9d2b7255.js                      10.46 kB │ gzip:   2.94 kB
dist/assets/Store-b97e8c06.js                        10.86 kB │ gzip:   3.36 kB
dist/assets/NodeDetails-c0a05d18.js                  12.13 kB │ gzip:   3.37 kB
dist/assets/DialogHealthCheck-018e9ac9.js            12.39 kB │ gzip:   3.59 kB
dist/assets/SmartStart-2eb0f0a6.js                   12.78 kB │ gzip:   3.78 kB
dist/assets/ExpandedNode-4a7f7a8f.js                 14.94 kB │ gzip:   5.04 kB
dist/assets/NodePanel-bcc05073.js                    15.39 kB │ gzip:   4.23 kB
dist/assets/Debug-0d008d6d.js                        16.32 kB │ gzip:   4.18 kB
dist/assets/QrReader-9e545d12.js                     20.90 kB │ gzip:   7.30 kB
dist/assets/index-7366e7f4.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-a9fad3fa.js                  54.99 kB │ gzip:  24.30 kB
dist/assets/vuedraggable.umd-5620d0aa.js             71.04 kB │ gzip:  24.90 kB
dist/assets/Settings-ad41e125.js                     74.67 kB │ gzip:  18.68 kB
dist/assets/index-30330024.js                       104.95 kB │ gzip:  43.04 kB
dist/assets/ZwaveGraph-3897a0bb.js                  561.14 kB │ gzip: 166.35 kB
dist/assets/index-30d03bd0.js                     1,177.81 kB │ gzip: 324.36 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 1.06s
PWA v0.16.7
mode      injectManifest
precache  73 entries (3170.81 KiB)
files generated
dist/sw.js
✓ built in 52.85s
Done in 76.62s.
+ 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=
+ [[ '' == a\8 ]]
+ [[ '' == a\8 ]]
+ [[ '' == a\d ]]
+ 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******************

La suite au post suivant car trop de caractères.


Informations Jeedom

Core : 4.4.6 (V4-stable)
DNS Jeedom : oui

Plugin : Z-Wave JS
Version : 2024-05-21 01:03:19 (beta)
Statut Démon : Démarré - (2024-05-27 05:50:05)

La suite donc:

Le log zwavejs

[2024-05-27 06:10:04] INFO  : Arrêt du démon ZwaveJS
[2024-05-27 06:10:05] DEBUG  : [configureSettings] Informations reçues de MQTT Manager : {"ip":"127.0.0.1","port":"1883","user":"jeedom","password":"***"}
[2024-05-27 06:10:05] INFO  : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=0102030405060708090A0B0C0D0E0F10 KEY_S2_Unauthenticated=B5E62B417E79F28B0FD86105EAA31951 KEY_S2_Authenticated=FF6A6747F6C56EC7B1586D09A60DDC2D KEY_S2_AccessControl=8A0226076B4664A5ECAE7672D68ACAE0 SESSION_SECRET=jeedomSession yarn start

le log zwavejsd

e[90m2024-05-27 06:10:09.838e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
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
$ node --preserve-symlinks server/bin/www.js
e[90m2024-05-27 06:15:10.021e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-05-27 06:15:10.027e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-05-27 06:15:10.059e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found

le log de JMQTT

[2024-05-27 06:15:10] INFO  : Cmd #[Maison][zwave][_CLIENTS:ZWAVE_GATEWAY-Jeedom:version]# <- {"value":"9.12.0","time":1716783310262}
[2024-05-27 06:15:10] INFO  : Cmd #[Maison][zwave][_CLIENTS:ZWAVE_GATEWAY-Jeedom:status]# <- {"value":true,"time":1716783310264}
[2024-05-27 06:15:12] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:15:15] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:15:19] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:15:25] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:15:35] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:15:52] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:16:09] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:16:26] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:16:43] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:17:00] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:17:17] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:17:34] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:17:52] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:18:09] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:18:26] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-27 06:18:43] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:18:59] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:19:17] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:19:34] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-27 06:19:52] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}

Il y a un problème de port mais pourquoi alors par moment cela fonctionne?

Résultat de la commande dmesg | grep tty

[    0.000000] Kernel command line: root=UUID=dec02c02-ccd8-480d-9b4f-da9523ed969e rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=3552739c-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[    0.001982] printk: console [tty1] enabled
[    2.035091] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 42, base_baud = 1500000) is a 16550A
[    2.035276] serial serial0: tty port ttyS0 registered
[    2.036273] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 43, base_baud = 1500000) is a 16550A
[    2.036550] printk: console [ttyS2] enabled
[    4.757967] systemd[1]: Created slice system-getty.slice.
[    4.762098] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    6.001596] systemd[1]: Found device /dev/ttyS2.
[    6.058664] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
[    6.766867] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0
[    6.825691] usb 7-1: FTDI USB Serial Device converter now attached to ttyUSB1

Dans mqtt2 je peux voir parfois ce log

[2024-05-26 03:20:12][DEBUG] : Message reçu sans prise en charge par un plugin : {"jeedom":{"cmd":{"event":{"6395":{"value":"{\"data\":[{\"message\":\"Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)\\n    at Driver.sendMessage (\/var\/www\/html\/plugins\/zwavejs\/resources\/zwave-js-ui\/node_modules\/zwave-js\/src\/lib\/driver\/Driver.ts:5349:23)\\n    at ZWaveController.queryCapabilities (\/var\/www\/html\/plugins\/zwavejs\/resources\/zwave-js-ui\/node_modules\/zwave-js\/src\/lib\/controller\/Controller.ts:970:37)\\n    at Driver.initializeControllerAndNodes (\/var\/www\/html\/plugins\/zwavejs\/resources\/zwave-js-ui\/node_modules\/zwave-js\/src\/lib\/driver\/Driver.ts:1458:46)\\n    at Immediate.<anonymous> (\/var\/www\/html\/plugins\/zwavejs\/resources\/zwave-js-ui\/node_modules\/zwave-js\/src\/lib\/driver\/Driver.ts:1259:16) (ZW0100)\",\"code\":100}]}","humanName":"[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]","unite":"","name":"_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error","type":"info","subtype":"string"}}}}}

Merci d’avance.

Bonjour,

Je vois plusieurs problèmes

355 fois un manque de mémoire
Votre modification de Python (elle n’est pas recommandée par les dev, lisez la réponse de Mips à ce sujet)

Pour moi, mais cela n’engage que moi :
Refaites un installation de 0 en suivant le même tutoriel et ne touchez pas à Python.
Sélectionnez le port ZwaveJS avec le numéro du port tel qu’il faut le définir dans Jeedom depuis fin 2023

Merci @Fabrice , pour le port on n’a pas trop le choix, il y a une liste déroulante et on ne peut choisir que là dedans

Merci pour les autres conseils, c’est ce que je me suis fixé ce soir s’il n’y a pas d’autres possibilités

Donc sur les conseils de @Fabrice j’ai refait une install et laissé python en 3.9. Après avoir tout réinstallé miracle zwave-js fonctionnait bien, remontée de tous mes équipements. Super, j’ai donc tenté un reboot pour vérifier que cela repartait bien et là même problème que précédemment… Le driver Z-Wave n\'est pas initialisé, veuillez patienter...

Quelqu’un aurait une idée?

ma page santé actuelle après réinstallation

Salut,

Il est normal d’avoir ce message un petit moment mais tu peux aussi regarder du côté du soft reset et le désactiver pour voir si c’est mieux.

Oui j’ai vu dans un des posts sur le forum cette histoire de soft reset mais apparemment cela ne change rien à mon pb. Quand tu parles d’un petit moment ça peut aller jusqu’à plusieurs heures?

je n’y connais pas grand chose dans ces histoire de port et autres dans debian mais est ce que le fait que la commande dmesg | grep tty indique plusieurs ttyS2 peut jouer? Il y en a un c’est pour la console si je comprends bien et l’autres c’est le contrôleur zwave mais lui est en /dev/ttyS2, c’est la même chose ou pas?

[    0.000000] Kernel command line: root=UUID=dec02c02-ccd8-480d-9b4f-da9523ed969e rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=3552739c-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[    0.001982] printk: console [tty1] enabled
[    2.035091] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 42, base_baud = 1500000) is a 16550A
[    2.035276] serial serial0: tty port ttyS0 registered
[    2.036273] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 43, base_baud = 1500000) is a 16550A
[    2.036550] printk: console [ttyS2] enabled
[    4.757967] systemd[1]: Created slice system-getty.slice.
[    4.762098] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    6.001596] systemd[1]: Found device /dev/ttyS2.
[    6.058664] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
[    6.766867] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0
[    6.825691] usb 7-1: FTDI USB Serial Device converter now attached to ttyUSB1

Non en principe ça reste quelques minutes… 2 à 5 minutes

pour l’instant j’en suis à 45 minutes…

j’ai viré le redémarrage auto du démon et j’ai de nouveau logs qui apparaissent dans jmqtt:

[2024-05-28 10:37:24] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}
[2024-05-28 10:37:45] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Failed to initialize the driver: ZWaveError: Timeout while waiting for an ACK from the controller (ZW0200)\n    at Driver.sendMessage (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:5349:23)\n    at ZWaveController.queryCapabilities (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/controller/Controller.ts:970:37)\n    at Driver.initializeControllerAndNodes (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:1458:46)\n    at Immediate.<anonymous> (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:1259:16) (ZW0100)","code":100}]}
[2024-05-28 10:38:02] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: The serial port closed unexpectedly! (ZW0100)","code":100}]}
[2024-05-28 10:38:03] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Failed to initialize the driver: ZWaveError: The driver is not ready or has been destroyed (ZW0103)\n    at Driver.ensureReady (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:2867:10)\n    at Driver.sendMessage (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:5269:8)\n    at ZWaveController.queryCapabilities (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/controller/Controller.ts:970:37)\n    at Driver.initializeControllerAndNodes (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:1458:46)\n    at Immediate.<anonymous> (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:1259:16) (ZW0100)","code":100}]}
[2024-05-28 10:38:19] INFO  : Cmd #[Maison][zwave][_EVENTS:ZWAVE_GATEWAY-Jeedom:driver:driver_error]# <- {"data":[{"message":"Serial port errored: EIO: i/o error, write (ZW0100)","code":100}]}

le message vient tout juste de disparaitre, presque 1 heure. Certain que si je reboot c’est rebelote

est ce que cela pourrait être un pb d’alim? J’ai pourtant mis une bonne de 65w mais je me pose la question

et zut le message est revenu même sans reboot…

Tu as quoi dans le port du contrôleur ?

Il est préférable de mettre les byid

C’est le contrôleur de ma smart que j’ai remis dans le rock pi 4b+, ça se met sur le gpio. Il n’y a pas le choix de byid avec le port /dev/ttyS2 utilisé

Bonjour,

Au cas où : le contrôleur est bien enfiché ?
Il n’a pas d’oxydation etc ?

salut @Madcow , oui c’est bien enfiché et c’est quasi neuf, ça brille

Bonjour
Vérifies si l’OS voit tjs la clé avec lsusb

Vérifies aussi que tu n’as pas de device qui apparaît dans /dev/serial ex chez moi:

docker@docker> ls -l /dev/serial/by-id
total 0
lrwxrwxrwx 1 root root 13 28 mai 13:10 usb-0658_0200-if00 → …/…/ttyACM0

Ok, je regarde ça dès que je rentre. Par contre ce n’est pas une clé USB mais une carte enfichée sur le port gpio, ça se voit quand même avec lsusb?