Driver Z-Wave n'est pas initialisé

mustang2 · Septembre 29, 2024, 2:43

N’ayant pas utilisé l’interface Jeedom depuis plusieurs semaines (action uniquement via les commandes manuelles) j’ai souhaité actionner une commande de volet Roller Shutter via les différentes applications dont je dispose…aucun effet que ce soit en passant par la connexion externe ou par le réseau local !! Je me suis rendu dans les mises à jour pour constater qu’effectivement le core ainsi que certains plugins nécessitaient des mises à jour. J’ai ensuite relancer les dépendances dans Z wave et redémarré le démon…ok…je n’ai toujours pas retrouvé la possibilité de le commander…voici quelques captures …dans quelle direction dois-je faire des recherches ??? merci

SWR · Septembre 29, 2024, 6:12

Tout fonctionne, quelle est la question ?

lperenna · Septembre 29, 2024, 6:18

Bonjour

Quand cela ne fonctionne pas en interne il y a quand même peu de probabilité que cela fasse des miracles en externe !

Le test primordial est quand même d’aller sur l’équipement et cliquer sur « tester » de l commande concernée avec le plugin dont cet équipement dépend en mode debug.

La en l’occurrence on peut supposer que c’est un équipement zwave dont on ne sait même pas si le module communique encore avec le contrôleur zwave ou si il est vu dead.

Il va donc être difficile d’en déduire quoique ce soit.

mustang2 · Septembre 29, 2024, 8:14

J’en suis à mes tous débuts avec ce premier équipement. J’essaie de comprendre cette partie informatique…je viens de me rendre dans l’équipement Fibaro FG223 dans l’onglet Commandes …je viens de tester les commandes Haut, Bas et Positionnement à 50%…rien ne se passe…par contre en haut de cette page il y a le message « Le driver Z-Wave n'est pas initialisé, veuillez patienter. Si le message reste trop longtemps, veuillez vérifier la configuration du démon »…or quand je vais voir la configuration du plugin Z wave, le démon est bien au vert comme indiqué sur la capture…par contre dans le log debug du démon il y a des erreurs… Merci de votre aide…
zwavejsd.txt (265,2 Ko)

lperenna · Septembre 30, 2024, 5:02

Bonjour

il faudrait copier ici entre balises

le log zwavejs_packages

Mettre le niveau de log en debug sauvegarder et redémarrer le démon et idem nous donner le log

Nous montrer en capture écran la config complète du plugin zwavejs ui avec le port choisit etc.

Bison · Septembre 30, 2024, 6:14

Bonjour,

Pour les RPi tu peux regarder ce post : [Présentation] akenad - #4 par akenad

Et vérifier en particulier cette partie :
Pour le Pi4 (avec Pi OS 64) :

Dans /boot/config.txt ajouter à la fin :
dtoverlay=disable-bt

Fabrice · Septembre 30, 2024, 6:19

Bonjour.

Si et seulement si le contrôleur Zwave est branché sur le port GPIO. Si le contrôleur est sur un port USB, il ne faut pas faire cela.

Bonne journée à tous

mustang2 · Septembre 30, 2024, 6:47

Bonjour, voici le log packages et la copie écran:

+ 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.20.0'
Wanted Version: 9.20.0
+ rm -R zwave-js-ui
+ git clone --branch v9.20.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: switching to 'bf3bdc3f13d903cf100b0ba9c3333101ffd29418'.
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://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
24 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 bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.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).
lsb-release is already the newest version (11.1.0).
git is already the newest version (1:2.30.2-1+deb11u3).
0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
[Check Version NodeJS actuelle : v20.17.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/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.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).
lsb-release is already the newest version (11.1.0).
git is already the newest version (1:2.30.2-1+deb11u3).
0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
[Check Version NodeJS actuelle : v20.17.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 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://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.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).
lsb-release is already the newest version (11.1.0).
git is already the newest version (1:2.30.2-1+deb11u3).
0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
[Check Version NodeJS actuelle : v20.17.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 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-29 15:08:05--  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%  997K 0s
50K .......                                               100% 36.7M=0.05s
2024-09-29 15:08:05 (1.11 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.9) 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 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 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 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.13.0: 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 eslint > file-entry-cache > flat-cache > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning eslint > file-entry-cache > flat-cache > 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 mocha > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning mocha > 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 release-it > shelljs > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vite-plugin-pwa > workbox-build > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning vite-plugin-pwa > workbox-build > @rollup/plugin-replace > magic-string > sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > @zwave-js/log-transport-json@3.0.0" has unmet peer dependency "@zwave-js/core@>=10.0.0".
warning " > @zwave-js/log-transport-json@3.0.0" has unmet peer dependency "@zwave-js/shared@>=10.0.0".
warning " > @zwave-js/log-transport-json@3.0.0" has unmet peer dependency "winston-transport@^4.5.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.20.5" has unmet peer dependency "workbox-build@^7.1.0".
warning " > vite-plugin-pwa@0.20.5" has unmet peer dependency "workbox-window@^7.1.0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 219.61s.
+ sudo yarn run build
yarn run v1.22.22
$ npm-run-all 'build:*'
$ tsc
$ vite build
vite v5.4.8 building for production...
transforming...
✓ 546 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.75 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-Droliepd.css            0.04 kB │ gzip:   0.06 kB
dist/assets/DialogGatewayValue-A-SkCATO.css           0.06 kB │ gzip:   0.08 kB
dist/assets/NodeDetails-CBP3OPmg.css                  0.06 kB │ gzip:   0.08 kB
dist/assets/FrameDetails-CIQ12EOu.css                 0.07 kB │ gzip:   0.09 kB
dist/assets/QrReader-HjYxZaii.css                     0.09 kB │ gzip:   0.10 kB
dist/assets/NodePanel-CZwLOHLG.css                    0.09 kB │ gzip:   0.10 kB
dist/assets/RichValue-B_0TC6eQ.css                    0.13 kB │ gzip:   0.12 kB
dist/assets/CCTreeView-WxmqzfXk.css                   0.13 kB │ gzip:   0.12 kB
dist/assets/Settings-DbLZdPoT.css                     0.15 kB │ gzip:   0.14 kB
dist/assets/Mesh-DSRRNttk.css                         0.27 kB │ gzip:   0.21 kB
dist/assets/ValueId-C5xZLsvS.css                      0.31 kB │ gzip:   0.18 kB
dist/assets/ExpandedNode--E63FB__.css                 0.39 kB │ gzip:   0.26 kB
dist/assets/DialogAdvanced-B3IdLJdP.css               0.45 kB │ gzip:   0.23 kB
dist/assets/index-D5uuzJlz.css                        0.51 kB │ gzip:   0.18 kB
dist/assets/Zniffer-BYjnQyPs.css                      0.53 kB │ gzip:   0.24 kB
dist/assets/Store-DS7bGYpj.css                        0.79 kB │ gzip:   0.33 kB
dist/assets/Multipane-CEm3CnxI.css                    1.57 kB │ gzip:   0.46 kB
dist/assets/BgRssiChart-DbNj0r-M.css                  1.65 kB │ gzip:   0.71 kB
dist/assets/Login-1yco1U5P.css                        5.43 kB │ gzip:   1.52 kB
dist/assets/ZwaveGraph-Dfn_CqSH.css                 220.21 kB │ gzip:  31.03 kB
dist/assets/index-r8JReBOx.css                      645.00 kB │ gzip:  86.98 kB
dist/assets/MultipaneResizer-CrhwLeVn.js              0.23 kB │ gzip:   0.20 kB
dist/assets/InvertedCheckbox-Casj3WXU.js              0.42 kB │ gzip:   0.30 kB
dist/assets/ControllerChart-5wbZWPMf.js               0.63 kB │ gzip:   0.40 kB
dist/assets/ColumnFilterBoolean-CpeijMdH.js           0.67 kB │ gzip:   0.43 kB
dist/assets/ReinterviewBadge-BLy0sYPi.js              0.78 kB │ gzip:   0.52 kB
dist/assets/BlinkIcon-DvFDLAnU.js                     0.85 kB │ gzip:   0.42 kB
dist/assets/ColumnFilterDate-C3OzzHhn.js              1.16 kB │ gzip:   0.56 kB
dist/assets/MissingKeysAlert-C4_v-0_e.js              1.17 kB │ gzip:   0.56 kB
dist/assets/ColumnFilterString-BxkWXz5W.js            1.22 kB │ gzip:   0.62 kB
dist/assets/DialogAdvanced-BckhBM6Y.js                1.30 kB │ gzip:   0.68 kB
dist/assets/CCTreeView-k1O-Przt.js                    1.43 kB │ gzip:   0.77 kB
dist/assets/StatisticsArrows-8Hj0lVlk.js              1.44 kB │ gzip:   0.78 kB
dist/assets/ErrorPage-Cj4JtOKm.js                     1.55 kB │ gzip:   0.79 kB
dist/assets/Multipane-C5GYi1Fo.js                     1.63 kB │ gzip:   0.82 kB
dist/assets/ColumnFilterNumber-C9WdFYmt.js            1.74 kB │ gzip:   0.74 kB
dist/assets/file-input-Dgrb79nA.js                    1.83 kB │ gzip:   0.86 kB
dist/assets/RichValue-Ck6H0vCq.js                     2.04 kB │ gzip:   0.87 kB
dist/assets/StatisticsCard-xxmJyWdy.js                2.55 kB │ gzip:   1.00 kB
dist/assets/FrameDetails-BaLcGxDr.js                  2.69 kB │ gzip:   1.07 kB
dist/assets/DialogSceneValue-CWFNB68k.js              3.18 kB │ gzip:   1.24 kB
dist/assets/Mesh-CoXAEodi.js                          3.18 kB │ gzip:   1.36 kB
dist/assets/ColumnFilter-D3n69yLL.js                  3.27 kB │ gzip:   1.30 kB
dist/assets/Login-zcMcZPCe.js                         4.13 kB │ gzip:   1.64 kB
dist/assets/UserCodeTable-BnQr9KPk.js                 4.13 kB │ gzip:   1.65 kB
dist/assets/ListInput-DlZNM1E_.js                     4.38 kB │ gzip:   1.41 kB
dist/assets/AssociationGroups-BcZtJ3en.js             4.46 kB │ gzip:   1.66 kB
dist/assets/OTAUpdates-BSAd5Tou.js                    5.09 kB │ gzip:   2.09 kB
dist/assets/Scenes-BmTuh8IC.js                        5.81 kB │ gzip:   1.99 kB
dist/assets/DialogLinkReliability-DLHzobTP.js         5.89 kB │ gzip:   1.91 kB
dist/assets/DialogAssociation-nzCubccy.js             5.94 kB │ gzip:   2.10 kB
dist/assets/prismeditor.esm-D40xGwwS.js               7.58 kB │ gzip:   2.70 kB
dist/assets/NodeScheduler-BsM0byYe.js                 7.86 kB │ gzip:   2.60 kB
dist/assets/HomeAssistant-CqAyFOeQ.js                 8.23 kB │ gzip:   2.43 kB
dist/assets/DialogGatewayValue-BWAE4Ah2.js            8.38 kB │ gzip:   2.57 kB
dist/assets/ControlPanel-CNg903je.js                  9.53 kB │ gzip:   3.54 kB
dist/assets/SmartView-miIRuWWu.js                     9.89 kB │ gzip:   3.32 kB
dist/assets/ValueId-KPa23EqJ.js                      10.45 kB │ gzip:   2.92 kB
dist/assets/Store-DEGE_ci-.js                        10.95 kB │ gzip:   3.42 kB
dist/assets/NodeDetails-ew-Uciby.js                  12.18 kB │ gzip:   3.40 kB
dist/assets/DialogHealthCheck-YSQW4VHz.js            12.38 kB │ gzip:   3.59 kB
dist/assets/SmartStart-DNtaywos.js                   13.83 kB │ gzip:   3.92 kB
dist/assets/ExpandedNode-CI6_LZhT.js                 15.15 kB │ gzip:   5.19 kB
dist/assets/Debug-fOIkVqm_.js                        16.04 kB │ gzip:   4.18 kB
dist/assets/NodePanel-B-X6G8uJ.js                    16.12 kB │ gzip:   4.40 kB
dist/assets/Zniffer-Ckljv1vm.js                      16.23 kB │ gzip:   5.29 kB
dist/assets/index-BUJ9QklM.js                        20.83 kB │ gzip:   6.14 kB
dist/assets/QrReader-Bq0oP6N0.js                     20.89 kB │ gzip:   7.30 kB
dist/assets/qr-scanner-worker.min-D85Z9gVD.js        43.95 kB │ gzip:  10.46 kB
dist/assets/BgRssiChart-pRwrzX-T.js                  55.70 kB │ gzip:  24.68 kB
dist/assets/vuedraggable.umd-BTynCjer.js             71.01 kB │ gzip:  24.89 kB
dist/assets/Settings-DOlf6SWo.js                     85.81 kB │ gzip:  20.00 kB
dist/assets/index-Blr6EMNg.js                        91.82 kB │ gzip:  46.05 kB
dist/assets/ZwaveGraph-DgkuR_KX.js                  560.41 kB │ gzip: 166.47 kB
dist/assets/index-DRnnQOJz.js                     1,239.34 kB │ gzip: 339.58 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 41.83s
PWA v0.20.5
Building src/sw.js service worker ("es" format)...
vite v5.4.8 building for production...
transforming...
✓ 65 modules transformed.
rendering chunks...
computing gzip size...
dist/sw.mjs  16.17 kB │ gzip: 5.42 kB
✓ built in 761ms
PWA v0.20.5
mode      injectManifest
format:   es
precache  82 entries (3265.17 KiB)
files generated
dist/sw.js
Done in 69.58s.
+ 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.mjs 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=d03115
+ [[ d03115 == a\8 ]]
+ [[ d03115 == a\8 ]]
+ [[ d03115 == 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******************

lperenna · Septembre 30, 2024, 6:54

Qu’avez-vous comme contrôleur zwave ?

peut on voir les choix proposé dans le port contrôleur zwave ? Un contrôleur sur GPIO je suppose ?

mustang2 · Septembre 30, 2024, 6:56

Voici le log demon (le demon vient de passer au rouge):

-------------------- TRUNCATED LOG --------------------
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fabcebe18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 05:55:06.290e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 05:55:06.297e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 05:55:06.340e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[624316:0x2ab282e0]   696714 ms: Scavenge 2041.4 (2082.3) -> 2038.4 (2082.3) MB, 8.28 / 0.00 ms  (average mu = 0.243, current mu = 0.166) task;
[624316:0x2ab282e0]   696780 ms: Scavenge 2041.4 (2082.3) -> 2038.5 (2082.5) MB, 9.12 / 0.00 ms  (average mu = 0.243, current mu = 0.166) task;
[624316:0x2ab282e0]   696838 ms: Scavenge 2041.6 (2082.5) -> 2038.7 (2082.5) MB, 8.02 / 0.00 ms  (average mu = 0.243, current mu = 0.166) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fa2668e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 06:10:07.188e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 06:10:07.195e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 06:10:07.222e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[625619:0x173a52e0]   660812 ms: Scavenge 2039.9 (2078.5) -> 2038.5 (2082.5) MB, 7.06 / 0.00 ms  (average mu = 0.251, current mu = 0.315) task;
[625619:0x173a52e0]   660877 ms: Scavenge 2041.6 (2082.5) -> 2038.6 (2082.5) MB, 8.70 / 0.00 ms  (average mu = 0.251, current mu = 0.315) task;
[625619:0x173a52e0]   660943 ms: Scavenge 2041.7 (2082.5) -> 2038.8 (2082.8) MB, 9.33 / 0.00 ms  (average mu = 0.251, current mu = 0.315) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fa7dcee18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 06:25:08.193e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 06:25:08.201e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 06:25:08.254e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[626892:0x1724b2e0]   645177 ms: Scavenge 2039.4 (2080.3) -> 2036.5 (2080.5) MB, 7.96 / 0.00 ms  (average mu = 0.225, current mu = 0.178) task;
[626892:0x1724b2e0]   645222 ms: Scavenge 2039.6 (2080.5) -> 2036.7 (2080.5) MB, 5.32 / 0.00 ms  (average mu = 0.225, current mu = 0.178) task;
[626892:0x1724b2e0]   645267 ms: Scavenge 2039.7 (2080.5) -> 2036.8 (2088.8) MB, 5.88 / 0.00 ms  (average mu = 0.225, current mu = 0.178) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fa1eb2e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 06:40:06.701e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 06:40:06.707e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 06:40:06.735e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[628195:0x431862e0]   693380 ms: Scavenge 2041.2 (2082.0) -> 2038.3 (2082.3) MB, 5.51 / 0.00 ms  (average mu = 0.205, current mu = 0.168) task;
[628195:0x431862e0]   693427 ms: Scavenge 2041.4 (2082.3) -> 2038.5 (2082.5) MB, 5.44 / 0.00 ms  (average mu = 0.205, current mu = 0.168) task;
[628195:0x431862e0]   693475 ms: Scavenge 2041.5 (2082.5) -> 2038.6 (2082.5) MB, 4.87 / 0.00 ms  (average mu = 0.205, current mu = 0.168) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7f94eaae18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 06:55:06.797e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 06:55:06.804e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 06:55:06.831e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[629470:0x1da722e0]   684158 ms: Scavenge 2041.5 (2082.3) -> 2038.5 (2082.5) MB, 5.77 / 0.00 ms  (average mu = 0.319, current mu = 0.283) task;
[629470:0x1da722e0]   684225 ms: Scavenge 2041.5 (2082.5) -> 2038.6 (2082.5) MB, 4.91 / 0.00 ms  (average mu = 0.319, current mu = 0.283) task;
[629470:0x1da722e0]   684286 ms: Scavenge 2041.7 (2082.5) -> 2038.8 (2082.8) MB, 5.10 / 0.00 ms  (average mu = 0.319, current mu = 0.283) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7faa93de18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 07:10:06.990e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 07:10:06.997e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 07:10:07.028e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[630780:0x369a02e0]   665712 ms: Scavenge 2041.1 (2082.0) -> 2038.2 (2082.3) MB, 5.05 / 0.00 ms  (average mu = 0.312, current mu = 0.311) task;
[630780:0x369a02e0]   665760 ms: Scavenge 2041.3 (2082.3) -> 2038.4 (2082.3) MB, 5.32 / 0.00 ms  (average mu = 0.312, current mu = 0.311) task;
[630780:0x369a02e0]   665806 ms: Scavenge 2041.4 (2082.3) -> 2038.5 (2082.5) MB, 5.07 / 0.00 ms  (average mu = 0.312, current mu = 0.311) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fa2d04e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 07:25:06.622e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 07:25:06.629e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 07:25:06.657e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[631936:0x5b422e0]   688479 ms: Scavenge 2041.3 (2082.3) -> 2038.4 (2082.3) MB, 8.67 / 0.00 ms  (average mu = 0.198, current mu = 0.158) task;
[631936:0x5b422e0]   688537 ms: Scavenge 2041.4 (2082.3) -> 2038.6 (2082.5) MB, 9.08 / 0.00 ms  (average mu = 0.198, current mu = 0.158) task;
[631936:0x5b422e0]   688596 ms: Scavenge 2041.6 (2082.5) -> 2038.7 (2082.8) MB, 8.91 / 0.00 ms  (average mu = 0.198, current mu = 0.158) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7f97771e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 07:40:07.119e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 07:40:07.126e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 07:40:07.154e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[633232:0xa3cb2e0]   726446 ms: Scavenge 2041.3 (2079.8) -> 2039.8 (2079.8) MB, 6.67 / 0.00 ms  (average mu = 0.196, current mu = 0.183) task;
[633232:0xa3cb2e0]   726478 ms: Scavenge 2041.3 (2079.8) -> 2039.9 (2079.8) MB, 6.49 / 0.00 ms  (average mu = 0.196, current mu = 0.183) task;
[633232:0xa3cb2e0]   726512 ms: Scavenge 2041.4 (2079.8) -> 2040.0 (2084.0) MB, 7.88 / 0.00 ms  (average mu = 0.196, current mu = 0.183) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fbd58be18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 07:55:06.832e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 07:55:06.838e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 07:55:06.866e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[634398:0x4273e2e0]   693716 ms: Scavenge 2039.5 (2080.3) -> 2036.6 (2080.5) MB, 5.06 / 0.00 ms  (average mu = 0.228, current mu = 0.193) task;
[634398:0x4273e2e0]   693764 ms: Scavenge 2039.6 (2080.5) -> 2036.7 (2080.5) MB, 4.84 / 0.00 ms  (average mu = 0.228, current mu = 0.193) task;
[634398:0x4273e2e0]   693812 ms: Scavenge 2039.8 (2080.5) -> 2036.9 (2088.8) MB, 6.00 / 0.00 ms  (average mu = 0.228, current mu = 0.193) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7f9bb02e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 08:10:07.385e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 08:10:07.391e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 08:10:07.419e[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-09-30 08:20:36.760e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 08:20:36.767e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 08:20:36.796e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[637035:0x34aee2e0]   662267 ms: Scavenge 2039.1 (2079.8) -> 2036.2 (2080.0) MB, 5.14 / 0.00 ms  (average mu = 0.208, current mu = 0.162) task;
[637035:0x34aee2e0]   662312 ms: Scavenge 2039.2 (2080.0) -> 2036.3 (2080.3) MB, 5.10 / 0.00 ms  (average mu = 0.208, current mu = 0.162) task;
[637035:0x34aee2e0]   662357 ms: Scavenge 2039.4 (2080.3) -> 2036.5 (2088.3) MB, 5.81 / 0.00 ms  (average mu = 0.208, current mu = 0.162) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7f8fe37e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 08:35:06.572e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 08:35:06.579e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 08:35:06.607e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
<--- Last few GCs --->
[639018:0x361b22e0]   720238 ms: Scavenge 2040.1 (2078.5) -> 2038.6 (2082.5) MB, 6.95 / 0.00 ms  (average mu = 0.212, current mu = 0.176) task;
[639018:0x361b22e0]   720308 ms: Scavenge 2041.7 (2082.5) -> 2038.8 (2082.8) MB, 8.47 / 0.00 ms  (average mu = 0.212, current mu = 0.176) task;
[639018:0x361b22e0]   720378 ms: Scavenge 2041.8 (2082.8) -> 2038.9 (2082.8) MB, 8.96 / 0.00 ms  (average mu = 0.212, current mu = 0.176) task;
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xb82448 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xebb25c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
3: 0xebb42c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node]
4: 0x10c302c  [/usr/bin/node]
5: 0x10c3548 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]
6: 0x10d8d30 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node]
7: 0x10d937c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]
8: 0x10d9e80 v8::internal::Heap::FinalizeIncrementalMarkingIfComplete(v8::internal::GarbageCollectionReason) [/usr/bin/node]
9: 0x10db7c4 v8::internal::IncrementalMarkingJob::Task::RunInternal() [/usr/bin/node]
10: 0xd16768  [/usr/bin/node]
11: 0xd19c04 node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/usr/bin/node]
12: 0x17f94c0  [/usr/bin/node]
13: 0x180ce04  [/usr/bin/node]
14: 0x17fa27c uv_run [/usr/bin/node]
15: 0xbbfb00 node::SpinEventLoopInternal(node::Environment*) [/usr/bin/node]
16: 0xcecd4c  [/usr/bin/node]
17: 0xced698 node::NodeMainInstance::Run() [/usr/bin/node]
18: 0xc5fdb0 node::Start(int, char**) [/usr/bin/node]
19: 0x7fa1134e18 __libc_start_main [/lib/aarch64-linux-gnu/libc.so.6]
20: 0xbbde20  [/usr/bin/node]
Aborted
error Command failed with exit code 134.
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-09-30 08:50:07.004e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.20.0.bf3bdc3
e[90m2024-09-30 08:50:07.011e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui

e[90m2024-09-30 08:50:07.058e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found

mustang2 · Septembre 30, 2024, 7:05

Je viens de voir que je n’ai aucune information qui apparait dans Informations du nœud…

lperenna · Septembre 30, 2024, 7:08

le port de votre contrôleur zwave n’est pas le bon

mustang2 · Septembre 30, 2024, 7:18

Serait-ce plutôt le port Raspberry pi situé au dessus de celui sélectionné??

lperenna · Septembre 30, 2024, 7:21

non je ne pense pas

vous pouvez aller dans réglages configuration, onglet os db et cliquer sur administration système
vous enlevez votre votre contrôleur usb gen gen du raspi
faite dans la page un lsusb

vous remettez le contrôleur et refait un lsusb

Vous montrer le résultat à chaque fois.
Car la on dirait que le gen 5 n’est pas vu par le raspi.

J’espère que vous ne l’avez pas branché sur un port usb3

Mips · Septembre 30, 2024, 7:37

il faut mettre le log à l’intérrieur des balises ```, ca ne sert à rien de mettre Texte préformaté autour du log…:

saisissez ou collez du code ici

relisez votre message lorsque vous avez posté: était-ce lisible?

j’ai corrigé les 2 posts précédents

mustang2 · Septembre 30, 2024, 7:48

Désolé, je patine un peu…pouvez-vous m’aider pour ce cheminement?? « réglages configuration » qu’est-ce qu’un Isusb ?
Le contrôleur est bien branché sur un port usb2 du Raspberry. Entre le contrôleur et le Raspberry il y a un DigitalLife Hub USB 2.0 4 Ports pour Claviers/Contrôleurs MIDI USB avec Câble Intégré de 30 cm…en y regardant de plus près il m’a certainement été livré un hub usb3 car les languettes sont de couleur bleues…

Mips · Septembre 30, 2024, 7:53

si votre clé zwave est branché en usb alors vous devez avoir / choisir quelque chose comme ceci dans la liste:

tout autre choix est incorrect.

si ce choix n’apparait pas, vous devez trouver pourquoi (testez sans hub, avec un autre hub etc)

lperenna · Septembre 30, 2024, 7:54

Déjà fait plus haut

mustang2 · Septembre 30, 2024, 8:53

Je viens de changer le port en sélectionnant cette fois le port indiqué ci dessus. J’ai également supprimé le hub usb DigitalLife Hub USB 2.0 qui en fait est certainement un hub usb3 (languettes bleues) contrairement à ce qui est écrit sur l’emballage du hub… J’ai retrouvé le fonctionnement normal !!! Super !!! je reste perplexe sur le fait qu’il ait pu fonctionner sur un port ACMO ou AMMO avec un hub usb…cela dépasse largement mes compétences…un grand merci à Iperenna et à Mips

mustang2 · Septembre 30, 2024, 11:12

Décidemment les bonnes nouvelles auront été de courtes durées…voici les messages reçus…

ainsi que log du demon

[90m2024-09-30 10:22:21.539e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
e[90m2024-09-30 12:41:27.198e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 63 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2024-09-30 12:41:27.211e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 63 on 38-1-targetValue: Fail
e[90m2024-09-30 12:42:46.383e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 60 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2024-09-30 12:42:46.384e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 60 on 38-1-targetValue: Fail
e[90m2024-09-30 12:43:02.599e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 100 on 38-1-targetValue: The node did not respond after 1 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:43:02.602e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 100 on 38-1-targetValue: Fail
e[90m2024-09-30 12:43:21.187e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing true on 38-1-Up: The node did not acknowledge the command (ZW0204)
e[90m2024-09-30 12:43:21.189e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write true on 38-1-Up: Fail
e[90m2024-09-30 12:46:47.236e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 100 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.906e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 98 on 38-1-targetValue: The node did not acknowledge the command (ZW0204)
e[90m2024-09-30 12:47:53.908e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 98 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.910e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 97 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.912e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 97 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.914e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 96 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.915e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 96 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.918e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 95 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.918e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 95 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.919e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 94 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.919e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 94 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.920e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 92 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.920e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 92 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.921e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 93 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.921e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 93 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.922e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 91 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.922e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 91 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.923e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 90 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.923e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 90 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.924e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 89 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.924e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 89 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.925e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 88 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.925e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 88 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.926e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 87 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.926e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 87 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.927e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 86 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.927e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 86 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.930e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 85 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.931e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 85 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.931e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 84 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.932e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 84 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.932e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 83 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.932e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 83 on 38-1-targetValue: Fail
e[90m2024-09-30 12:47:53.933e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 82 on 38-1-targetValue: The node did not respond after 3 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:47:53.933e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 82 on 38-1-targetValue: Fail
e[90m2024-09-30 12:48:28.225e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing 71 on 38-1-targetValue: The node did not respond after 1 attempts, it is presumed dead (ZW0202)
e[90m2024-09-30 12:48:28.228e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write 71 on 38-1-targetValue: Fail
e[90m2024-09-30 12:50:36.361e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing true on 38-1-Up: The node did not acknowledge the command (ZW0204)
e[90m2024-09-30 12:50:36.363e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write true on 38-1-Up: Fail
e[90m2024-09-30 12:58:37.597e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Error while writing true on 38-1-Up: The node did not acknowledge the command (ZW0204)
e[90m2024-09-30 12:58:37.598e[39m e[31mERRORe[39m e[1mZ-WAVEe[22m: Unable to write true on 38-1-Up: Fail

Le noeud passe de Dead à Alive…de plus je n’ai plus le retour de position le widget apparemment…rectification: le positionnement apparait bien plus tard qu’auparavant…