Problème Zooz 800 ZST39

Bonjour,
Je viens de faire un essai avec la ZST39 en partant d’une Z stick Z5 V1.00. Je suis passé par l’intermédiaire d’un Z5 plus. J’ai passé la ZST en 1.5.
Tout c’est très bien passé en 20 mn. Le démarrage ok : tous les nœuds reconnus.
Quelques heures plus tard des difficultés: la réaction à certaines commandes deviennent longues ou pas de réaction. Certains nœuds passent dead puis alive… Par moment ça fonctionne, puis pas. Relance des dépendances, ok parfait puis re-problème, reboot du RPi idem en pire. Le réseau devient instable à 95 % du temps. Bref retour à ma Z5 et tout refonctionne parfaitement… Avez-vous une idée? Merci par avance.



Exemple avec la clé Zooz:

Fonctionnement avec la clé Gen5 en 10H de fonctionnement:

+ 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.29.0'
Wanted Version: 9.29.0
+ rm -R zwave-js-ui
+ git clone --branch v9.29.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: switching to 'b8373a3567766d39d3569f81719df8bbd867590e'.
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
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 bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Get:6 https://pkgs.tailscale.com/stable/raspbian bullseye InRelease
Fetched 6581 B in 1s (11.1 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
6 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://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Get:6 https://pkgs.tailscale.com/stable/raspbian bullseye InRelease
Fetched 6581 B in 1s (12.0 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (12.0-1).
build-essential is already the newest version (12.9).
apt-utils is already the newest version (2.6.1).
git is already the newest version (1:2.39.5-0+deb12u2).
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
[Check Version NodeJS actuelle : v20.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Clean npm cache
npm warn using --force Recommended protections disabled.
+ echo 6
+ 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 npm install
npm warn deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated 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
npm warn deprecated csurf@1.11.0: Please use another csrf package
npm warn deprecated @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.
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated vue@2.7.16: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
added 1667 packages, and audited 1668 packages in 25s
334 packages are looking for funding
run `npm fund` for details
42 vulnerabilities (10 low, 26 moderate, 6 high)
To address issues that do not require attention, run:
npm audit fix
To address all issues possible (including breaking changes), run:
npm audit fix --force
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
+ sudo npm run build
> zwave-js-ui@9.29.0 build
> npm-run-all build:*
> zwave-js-ui@9.29.0 build:server
> tsc
> zwave-js-ui@9.29.0 build:ui
> vite build
vite v5.4.11 building for production...
transforming...
✓ 421 modules transformed.
rendering chunks...
computing gzip size...
dist/registerSW.js                                    0.14 kB
dist/manifest.webmanifest                             0.50 kB
dist/index.html                                       1.69 kB │ gzip:   0.74 kB
dist/assets/MaterialIcons-Regular-DOtZ65Va.woff2    125.12 kB
dist/assets/MaterialIcons-Regular-BjXOXp5c.eot      143.45 kB
dist/assets/MaterialIcons-Regular-FsbMSDLx.woff     160.58 kB
dist/assets/MaterialIcons-Regular-DEUTIz1o.ttf      347.59 kB
dist/assets/DialogHealthCheck-BQ_HIZzk.css            0.04 kB │ gzip:   0.06 kB
dist/assets/DialogGatewayValue-Dm4ULrQ4.css           0.06 kB │ gzip:   0.08 kB
dist/assets/NodeDetails-BVv96O7e.css                  0.06 kB │ gzip:   0.08 kB
dist/assets/FrameDetails-DfeKn8lA.css                 0.07 kB │ gzip:   0.09 kB
dist/assets/QrReader-CWgAkvgE.css                     0.09 kB │ gzip:   0.10 kB
dist/assets/NodePanel-NlzD7HjS.css                    0.09 kB │ gzip:   0.10 kB
dist/assets/RichValue-D2CNQpme.css                    0.13 kB │ gzip:   0.12 kB
dist/assets/CCTreeView-CpgHtNhq.css                   0.13 kB │ gzip:   0.12 kB
dist/assets/Settings-Dm6CEHC0.css                     0.15 kB │ gzip:   0.14 kB
dist/assets/Mesh-BGDvcFfn.css                         0.27 kB │ gzip:   0.21 kB
dist/assets/ValueId-CvU87fFq.css                      0.31 kB │ gzip:   0.18 kB
dist/assets/ExpandedNode-Cz-LXYo1.css                 0.39 kB │ gzip:   0.26 kB
dist/assets/DialogAdvanced-D5KZ1_3L.css               0.45 kB │ gzip:   0.23 kB
dist/assets/index-BV77wOsY.css                        0.51 kB │ gzip:   0.18 kB
dist/assets/Zniffer-DKOnYIE1.css                      0.53 kB │ gzip:   0.25 kB
dist/assets/Store-DXshLReN.css                        0.79 kB │ gzip:   0.33 kB
dist/assets/Multipane-Ds04H7aO.css                    1.57 kB │ gzip:   0.46 kB
dist/assets/BgRssiChart-D1GxaB_c.css                  1.65 kB │ gzip:   0.71 kB
dist/assets/Login-gAZskv5f.css                        5.43 kB │ gzip:   1.52 kB
dist/assets/ZwaveGraph-CV956Kpy.css                 220.21 kB │ gzip:  31.03 kB
dist/assets/index-BsI52nnX.css                      644.96 kB │ gzip:  86.97 kB
dist/assets/MultipaneResizer-CKKpf-t7.js              0.23 kB │ gzip:   0.20 kB
dist/assets/InvertedCheckbox-CBdSJsR_.js              0.42 kB │ gzip:   0.30 kB
dist/assets/ControllerChart-FGuofXG1.js               0.63 kB │ gzip:   0.40 kB
dist/assets/ColumnFilterBoolean-DzhkCjdE.js           0.67 kB │ gzip:   0.43 kB
dist/assets/ReinterviewBadge-C0jBHbcO.js              0.78 kB │ gzip:   0.52 kB
dist/assets/BlinkIcon-Csr_Offt.js                     0.85 kB │ gzip:   0.42 kB
dist/assets/ColumnFilterDate-_GGe-eAb.js              1.16 kB │ gzip:   0.56 kB
dist/assets/MissingKeysAlert-8ltSJmg-.js              1.17 kB │ gzip:   0.56 kB
dist/assets/ColumnFilterString-DKcokM3A.js            1.22 kB │ gzip:   0.61 kB
dist/assets/DialogAdvanced-hGcx51DP.js                1.30 kB │ gzip:   0.68 kB
dist/assets/CCTreeView-Ou48zXDd.js                    1.43 kB │ gzip:   0.77 kB
dist/assets/StatisticsArrows-BRpWCqBe.js              1.44 kB │ gzip:   0.78 kB
dist/assets/ErrorPage-Dj-MvsSW.js                     1.55 kB │ gzip:   0.79 kB
dist/assets/Multipane-YjHRqU4X.js                     1.63 kB │ gzip:   0.82 kB
dist/assets/ColumnFilterNumber-BL1-dASa.js            1.74 kB │ gzip:   0.74 kB
dist/assets/file-input-CQWvHRCU.js                    1.83 kB │ gzip:   0.86 kB
dist/assets/RichValue-aZStO_pF.js                     2.04 kB │ gzip:   0.87 kB
dist/assets/StatisticsCard-DaUEOlUW.js                2.55 kB │ gzip:   1.00 kB
dist/assets/FrameDetails-DImo9dTA.js                  2.69 kB │ gzip:   1.07 kB
dist/assets/DialogSceneValue-3B9Sf4Lq.js              3.18 kB │ gzip:   1.24 kB
dist/assets/Mesh-CfZGUgOJ.js                          3.18 kB │ gzip:   1.36 kB
dist/assets/ColumnFilter-BhVmR6Xb.js                  3.27 kB │ gzip:   1.30 kB
dist/assets/Login-BjyrmTLG.js                         4.13 kB │ gzip:   1.64 kB
dist/assets/UserCodeTable-BbEm6bro.js                 4.13 kB │ gzip:   1.65 kB
dist/assets/ListInput-DEwDWxmu.js                     4.38 kB │ gzip:   1.42 kB
dist/assets/AssociationGroups-Cdx35XKy.js             4.40 kB │ gzip:   1.63 kB
dist/assets/OTAUpdates-Dalsc8uI.js                    5.70 kB │ gzip:   2.32 kB
dist/assets/DialogAssociation-D0AW8Y0N.js             5.79 kB │ gzip:   2.07 kB
dist/assets/Scenes-D44_HELB.js                        5.81 kB │ gzip:   1.99 kB
dist/assets/DialogLinkReliability-BWr4lUy1.js         5.89 kB │ gzip:   1.91 kB
dist/assets/prismeditor.esm-Do-Rj-tb.js               7.58 kB │ gzip:   2.69 kB
dist/assets/NodeScheduler-Bz4-8uZf.js                 7.72 kB │ gzip:   2.57 kB
dist/assets/HomeAssistant-BEPzqUk6.js                 8.23 kB │ gzip:   2.43 kB
dist/assets/DialogGatewayValue-9oqltRi0.js            8.38 kB │ gzip:   2.57 kB
dist/assets/ControlPanel-DAuCE5yE.js                  9.53 kB │ gzip:   3.54 kB
dist/assets/SmartView-sTQAuV5k.js                     9.90 kB │ gzip:   3.31 kB
dist/assets/ValueId-CIaZUH3v.js                      10.48 kB │ gzip:   2.92 kB
dist/assets/Store-CwqQjM70.js                        12.08 kB │ gzip:   3.69 kB
dist/assets/DialogHealthCheck-D2_ja1Y0.js            12.34 kB │ gzip:   3.57 kB
dist/assets/SmartStart-BHTNkO-b.js                   13.89 kB │ gzip:   3.94 kB
dist/assets/NodeDetails-DJzyb2Tc.js                  15.05 kB │ gzip:   4.24 kB
dist/assets/ExpandedNode-DigAUgNp.js                 15.14 kB │ gzip:   5.18 kB
dist/assets/NodePanel-CN9QVaha.js                    15.97 kB │ gzip:   4.39 kB
dist/assets/Zniffer-1rVJCCZi.js                      16.09 kB │ gzip:   5.30 kB
dist/assets/Debug-MSJyu__z.js                        16.47 kB │ gzip:   4.32 kB
dist/assets/index-jFGEU1d-.js                        20.82 kB │ gzip:   6.14 kB
dist/assets/qr-scanner-worker.min-D85Z9gVD.js        43.95 kB │ gzip:  10.46 kB
dist/assets/BgRssiChart-DfUuPzkE.js                  55.69 kB │ gzip:  24.67 kB
dist/assets/QrReader-CRn3j8mk.js                     63.12 kB │ gzip:  22.19 kB
dist/assets/vuedraggable.umd-BUwyx-MQ.js             71.01 kB │ gzip:  24.89 kB
dist/assets/Settings-Ehs_W54t.js                     87.69 kB │ gzip:  20.29 kB
dist/assets/index-Blr6EMNg.js                        91.82 kB │ gzip:  46.05 kB
dist/assets/ZwaveGraph-CSuN5Kbk.js                  560.20 kB │ gzip: 166.50 kB
dist/assets/index-CpYaRATg.js                     1,109.70 kB │ gzip: 306.74 kB
(!) Some chunks are larger than 500 kB 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.
✓ built in 14.80s
PWA v0.20.5
Building src/sw.js service worker ("es" format)...
vite v5.4.11 building for production...
transforming...
✓ 65 modules transformed.
rendering chunks...
computing gzip size...
dist/sw.mjs  16.17 kB │ gzip: 5.42 kB
✓ built in 797ms
PWA v0.20.5
mode      injectManifest
format:   es
precache  83 entries (4096.29 KiB)
files generated
dist/sw.js
+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md api certs dist docker docs esbuild-import-meta-url-shim.js 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.mjs wallaby.js
+ '[' -e /dev/ttyAMA0 ']'
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=c04170
+ [[ c04170 == a\8 ]]
+ [[ c04170 == a\8 ]]
+ [[ c04170 == a\d ]]
+ echo 'Everything is successfully installed!'
Everything is successfully installed!
+ echo 7
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
+ echo 8
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Dernière info, je passé zwave js iu en 9.29.0 car j’ai vu dans le forum que cela avait été conseillé : ça n’a rien changé ni en bien ni en mal…
Avez-vous une idée? Merci par avance.

Reinterroger les noeuds par exemple.
Pour les logs merci de copié collé le texte en utilisant pour le formatage:

Antoine

Je l’ai fait pour certains mais je n’ai pas fait un systématique…

Exemple avec la zst39

e[90m2025-04-19 01:04:02.455e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 01:04:02.605e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:04:02.606e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 01:05:01.990e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing false on 37-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:05:01.992e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write false on 37-1-targetValue: Fail
e[90m2025-04-19 01:05:02.685e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing false on 37-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:05:02.687e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write false on 37-1-targetValue: Fail
e[90m2025-04-19 01:05:02.743e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:05:02.744e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 01:05:02.765e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:05:02.765e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 01:06:02.347e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing false on 37-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:06:02.347e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write false on 37-1-targetValue: Fail
e[90m2025-04-19 01:06:02.581e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing false on 37-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:06:02.582e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write false on 37-1-targetValue: Fail
e[90m2025-04-19 01:06:02.709e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:06:02.709e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 01:06:02.745e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:06:02.745e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 01:08:35.019e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 23 on 38-0-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:08:35.019e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 23 on 38-0-targetValue: Fail
e[90m2025-04-19 01:08:39.182e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 24 on 38-0-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:08:39.182e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 24 on 38-0-targetValue: Fail
e[90m2025-04-19 01:08:42.449e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing true on 37-0-targetValue: Failed to send the command after 1 attempts (ZW0202)
e[90m2025-04-19 01:08:42.449e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write true on 37-0-targetValue: Fail
e[90m2025-04-19 01:08:45.654e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing false on 37-0-targetValue: Failed to send the command

Avec gen5 en 16H:

|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2025-04-19 01:20:29.608e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
e[90m2025-04-19 01:36:18.298e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 99 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-19 01:36:18.300e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 99 on 38-1-targetValue: Fail
e[90m2025-04-19 06:09:21.513e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-19 06:09:21.515e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-19 17:22:24.929e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-19 17:22:24.930e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail

En plus lisible !

C’est quoi comme appareil? Tu as testé de le Reinterroger ? De refaire l’appairage?

Antoine

Hello Antoine,
De retour…
J’ai fait un "interview de tous les nœuds sur secteur. ça a été une cat pendant une demi heure puis fonctionnement parfait pendant une vingtaine d’heure!
Puis ça a recommencer à merdouiller sérieux: aucun ordre ne passait. Il doit y avoir un nœud qui merdouille et après c’est la cata. J’ai remis ma vielle clé avant de partir et il a fallu plusieurs heures avant que tout se calme (plusieurs relance des dépendances, arrêt de tous les scénarios qui envoie des ordres) le temps que ça se calme. Depuis ok mais j’ai ça qui me pose problème:

[2025-04-22 18:36:02] DEBUG  : [refreshIfNeeded] 37/1/targetValue false
[2025-04-22 18:36:02] DEBUG  : [refreshIfNeeded] 37/1/targetValue false
[2025-04-22 18:36:02] DEBUG  : [refreshIfNeeded] 38/1/targetValue 5
[2025-04-22 18:37:02] DEBUG  : [refreshIfNeeded] 37/1/targetValue false
[2025-04-22 18:37:03] DEBUG  : [refreshIfNeeded] 37/1/targetValue false
[2025-04-22 18:37:03] DEBUG  : [refreshIfNeeded] 38/1/targetValue 5
[2025-04-22 18:38:02] DEBUG  : [refreshIfNeeded] 37/1/targetValue false
[2025-04-22 18:38:02] DEBUG  : [refreshIfNeeded] 37/1/targetValue false
[2025-04-22 18:38:02] DEBUG  : [refreshIfNeeded] 38/1/targetValue 5

qui sort toutes minutes et qui doit correspondre à l’envoie de la valeur 5 toutes les minutes:


mais les deux lignes « 37/1 target value false » je ne sais pas comment trouver ce que c’est?
De plus, j’ai ça qui sort en erreur de temps en temps :

e[90m2025-04-22 13:54:22.895e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 13:54:22.896e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 14:10:24.804e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 14:10:24.805e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 14:15:22.995e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 14:15:22.995e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 14:29:25.206e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 14:29:25.206e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 15:04:23.788e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 15:04:23.789e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 15:28:26.916e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 15:28:26.916e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 15:50:25.949e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 15:50:25.949e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 16:07:26.943e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 16:07:26.944e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail
e[90m2025-04-22 16:45:24.789e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 5 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2025-04-22 16:45:24.790e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 5 on 38-1-targetValue: Fail

C’est surement le même nœud ?
Comment savoir quel nœud pose ce problème?

Bonjour,

Ce n’est pas le même noeud.

Essaye de passer en zwavejsui 10.2.0 (puisque apparemment tu sais comment faire).
Je ne promet rien mais cette version corrige un bug qui pourrait s’appliquer à ton problème.

Faudrait arrêter, cela sert probablement à rien, sauf à mettre le binz.

Bonjour,
Merci pour vos différents conseils. Je vous fais un compte rendu de mon installation.
J’ai upgradé en 10.2.0 puis repassé mon réseau sur la ZST39 hier début après midi. Fonctionnement correct jusque dans la soirée, puis quelques latences et quelques défauts de communications… En regardant tous les paramètres et statistiques du réseau zwave, je me suis aperçu qu’un module Qubino ZMNHDD avait transmis 125000 trames alors que les autres en avais transmis 2 ou 3000 au maxi. La vitesse de transfert du module était à 9,6 Kbit/s soit beaucoup moins que ce qui était prévu.
Sur ce module, j’ai changé le paramètre de temps entre deux transfert de la puissance instantanée (passé de 1 à 20). Le nombre de transfert diminue nettement. La vitesse de transfert est restée la même.
Ce matin, aucun défaut dans les log pendant la nuit mais quelques latences quand on envoie un ordre sur le réseau.
J’ai fait une réinterview de ce nœud. A priori rien de changé mais ce midi la vitesse de transfert de ce modèle est passée à 100 kbits/s…
J’ai passé quelques ordres et tout fonctionne sans latence.
Je ne crie pas, encore victoire, l’expérience me dit qu’il faut très être patient mais j’espère être sur la bonne voie. Je confirmerai d’ici quelques jours si c’est ok.
Je pense que le module ZST39 supporte moins bien les « surcharges » que l’ancien Z-stick Gen5 d’Aeotec V1.00.
Pourquoi ce changement de vitesse de transfert du module Qubino??? (ma petite explication mais sans aucune certitude: si un module envoie trop d’info, il commence à saturer le réseau, des erreurs doivent commencer à se produire donc le module commence à ralentir sa vitesse de transfert et donc utilise encore plus de temps sur le réseau etc… ce qui écroule complètement le réseau).
Encore merci à tous,

Bonjour,
Cela fait quelques jours maintenant et plus aucun problème de fonctionnement et plus de défaut dans les log.
Merci à Madcow et à Tonio16

1 « J'aime »

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.