Bonjour
Je suis sur une box luna en V4.4.0
Version de ZwaveJS 2023-11-17 01:03:21
Version de ZwaveJS UI 8.26.0
Impossible depuis les dernières maj de redémarrer le deamon de ZwaveJS
Malgré les conseils sur ce forum celà fait plus de 2 semaines que j’essaye de faire fonctionner mon réseau zwave sans succès
les logs pus bas ;
Peut-on m’aider?
Bien à vous
Bonjour,
As-tu émis un ticket Jeedom ?
Les logs, sans les coller ici entre balises c inexploitable.
Pq etre en version 4.4 qui nest que en beta ou aloha sur une box officielle de prod ?
Bonjour,
Non pas encore.
Je préfère essayer via le forum avant d’ennuyer les progs
Les tickets j’essaye en dernier recours. parfois un peu de patience et une maj résoud le prob mais ici il faut du temps quand même …
Bonjour
tu préfères que je dépose les fichier de logs à télecharger c’est bien celà que tu m’expliques?
J’ai essayer de passer en béta ça à déjà résolu dans certains cas mes probs .
Je n’arrive malheureusement pas ici à repasser sur la version précédente en forçant la maj du core.
zwavejs_packages.txt (8,7 Ko)
Page sante jeedom
Copier coller les logs de dependances entre balises
Page config plugin zwave et mqtt
Savoir ce que tu as deja testé genrz soft reset ou pas ?
-J’ai en effet fait un soft reset du pluggin zwave
-j’ai réinstaller les dépendances plusieurs x et depuis la version de zwaveJS Ui repassée en 8.26.0
-mqtt pareil réinstallé le dépendances
-redémarrage de la box après chaque manip
le log des package jwavejs:
000|+ echo '*******************Begin of package installation******************'
0001|*******************Begin of package installation******************
0002|+ touch /tmp/jeedom_install_in_progress_zwavejs
0003|+ echo 1
0004|+ echo 2
0005|+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
0006|+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
0007|+ echo 'Pre installation de l'\''installation/mise à jour des dépendances zwavejs'
0008|Pre installation de l'installation/mise à jour des dépendances zwavejs
0009|+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/pre_install.sh
0010|++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
0011|++ pwd
0012|+ BASEDIR=/var/www/html/plugins/zwavejs/resources
0013|+ cd /var/www/html/plugins/zwavejs/resources
0014|+ source ../core/config/zwavejs.config.ini
0015|+ echo 'Wanted Version: 8.26.0'
0016|Wanted Version: 8.26.0
0017|+ rm -R zwave-js-ui
0018|+ git clone --branch v8.26.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
0019|Cloning into 'zwave-js-ui'...
0020|Note: switching to '08e6a7e0474aecce39693de56dee4e33ce242206'.
0021|You are in 'detached HEAD' state. You can look around, make experimental
0022|changes and commit them, and you can discard any commits you make in this
0023|state without impacting any branches by switching back to a branch.
0024|If you want to create a new branch to retain commits you create, you may
0025|do so (now or later) by using -c with the switch command. Example:
0026|git switch -c <new-branch-name>
0027|Or undo this operation with:
0028|git switch -
0029|Turn off this advice by setting config variable advice.detachedHead to false
0030|+ echo 'Pre install finished'
0031|Pre install finished
0032|+ echo 3
0033|+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
0034|warning: commands will be executed using /bin/sh
0035|job 244 at Thu Nov 23 13:31:00 2023
0036|+ echo 4
0037|+ sudo apt update
0038|WARNING apt does not have a stable CLI interface. Use with caution in scripts.
0039|Reading package lists...
0040|E: Could not get lock /var/lib/apt/lists/lock. It is held by process 3722464 (apt-get)
0041|E: Unable to lock directory /var/lib/apt/lists/
0042|+ echo 5
0043|+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
0044|+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
0045|Hit:1 https://deb.debian.org/debian bullseye InRelease
0046|Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
0047|Hit:3 https://deb.debian.org/debian bullseye-updates InRelease
0048|Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
0049|Hit:5 https://deb.nodesource.com/node_18.x bullseye InRelease
0050|Hit:6 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
0051|Reading package lists...
0052|Reading package lists...
0053|Building dependency tree...
0054|Reading state information...
0055|apt-utils is already the newest version (2.2.4).
0056|build-essential is already the newest version (12.9).
0057|git is already the newest version (1:2.30.2-1+deb11u2).
0058|lsb-release is already the newest version (11.1.0).
0059|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0060|[Check Version NodeJS actuelle : v18.17.1 : [ OK ]
0061|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
0062|+ echo 6
0063|+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
0064|+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
0065|Hit:1 https://deb.debian.org/debian bullseye InRelease
0066|Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
0067|Hit:3 https://deb.debian.org/debian bullseye-updates InRelease
0068|Hit:4 https://deb.nodesource.com/node_18.x bullseye InRelease
0069|Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
0070|Hit:6 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
0071|Reading package lists...
0072|Reading package lists...
0073|Building dependency tree...
0074|Reading state information...
0075|apt-utils is already the newest version (2.2.4).
0076|build-essential is already the newest version (12.9).
0077|git is already the newest version (1:2.30.2-1+deb11u2).
0078|lsb-release is already the newest version (11.1.0).
0079|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0080|[Check Version NodeJS actuelle : v18.17.1 : [ OK ]
0081|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
0082|+ echo 7
0083|+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
0084|+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
0085|Hit:1 https://deb.debian.org/debian bullseye InRelease
0086|Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
0087|Hit:3 https://deb.debian.org/debian bullseye-updates InRelease
0088|Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
0089|Hit:5 https://deb.nodesource.com/node_18.x bullseye InRelease
0090|Hit:6 https://packagecloud.io/ookla/speedtest-cli/debian bullseye InRelease
0091|Reading package lists...
0092|Reading package lists...
0093|Building dependency tree...
0094|Reading state information...
0095|apt-utils is already the newest version (2.2.4).
0096|build-essential is already the newest version (12.9).
0097|git is already the newest version (1:2.30.2-1+deb11u2).
0098|lsb-release is already the newest version (11.1.0).
0099|0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
0100|[Check Version NodeJS actuelle : v18.17.1 : [ OK ]
0101|[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
0102|+ echo 8
0103|+ sudo chmod +x /var/www/html/core/class/../../resources/install_composer.sh
0104|+ sudo /var/www/html/core/class/../../resources/install_composer.sh
0105|Begin installation of composer
0106|Installer verified
0107|All settings correct for using Composer
0108|Downloading...
0109|Composer (version 2.6.5) successfully installed to: /var/www/html/core/ajax/composer.phar
0110|Use it: php composer.phar
0111|End installation of composer
0112|+ echo 9
0113|+ sudo npm install --force -g yarn
0114|npm WARN using --force Recommended protections disabled.
0115|changed 1 package in 7s
0116|+ echo 10
0117|+ sudo chmod +x /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
0118|+ sudo /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
0119|+ echo 'Post installation de l'\''installation/mise à jour des dépendances zwavejs'
0120|Post installation de l'installation/mise à jour des dépendances zwavejs
0121|+++ dirname /var/www/html/core/class/../../plugins/zwavejs/resources/post_install.sh
0122|++ cd /var/www/html/core/class/../../plugins/zwavejs/resources
0123|++ pwd
0124|+ BASEDIR=/var/www/html/plugins/zwavejs/resources
0125|+ cd /var/www/html/plugins/zwavejs/resources
0126|+ cd zwave-js-ui
0127|+ sudo yarn install
0128|➤ YN0000: ┌ Resolution step
0129|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide @babel/core (pd92f5), requested by @babel/register
0130|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide @egjs/hammerjs (pb72e2), requested by vis-network
0131|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide component-emitter (p9f27e), requested by vis-network
0132|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide esbuild (pe0be1), requested by esbuild-register
0133|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide keycharm (p9e48c), requested by vis-network
0134|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide timsort (pd6433), requested by vis-network
0135|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide uuid (p8cb88), requested by vis-data
0136|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide uuid (p57e35), requested by vis-network
0137|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide vis-util (p81018), requested by vis-data
0138|➤ YN0002: │ zwave-js-ui@workspace:. doesn't provide vis-util (p6ebf7), requested by vis-network
0139|➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
0140|➤ YN0000: └ Completed in 3s 110ms
0141|➤ YN0000: ┌ Fetch step
0142|➤ YN0018: │ typescript@patch:typescript@npm%3A5.2.2#~builtin<compat/typescript>::version=5.2.2&hash=7ad353: The remote archive doesn't match the expected checksum
0143|➤ YN0000: └ Completed in 9s 750ms
0144|➤ YN0000: Failed with errors in 12s 897ms
0145|+ sudo NODE_OPTIONS=--max_old_space_size=2048yarn run build
0146|sudo: run: command not found
0147|+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md app.ts bin certs config docker docs genereteDocs.ts hass index.html kubernetes kustomization.yaml lib nodemon.json package.json package.sh pkg public server_config.js snippets src store test tsconfig.eslint.json tsconfig.json vite.config.js wallaby.js yarn.lock
0148|+ '[' -e /dev/ttyAMA0 ']'
0149|+ '[' -e /dev/ttymxc0 ']'
0150|+ '[' -e /dev/ttyAMA0 ']'
0151|++ cut -d: -f2
0152|++ grep Revision /proc/cpuinfo
0153|++ tr -d ' '
0154|+ RPI_BOARD_REVISION=
0155|+ [[ '' == a\8 ]]
0156|+ [[ '' == a\8 ]]
0157|+ [[ '' == a\d ]]
0158|+ echo 'Everything is successfully installed!'
0159|Everything is successfully installed!
0160|+ echo 11
0161|+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
0162|+ rm /tmp/jeedom_install_in_progress_zwavejs
0163|+ echo '*******************End of package installation******************'
0164|*******************End of package installation******************
le log de jwavejsd:
0515|Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)
0516|$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...
Le log du pluggin jwavejs:
1000|[2023-11-24 10:45:03]DEBUG : [refreshIfNeeded] 37/0/targetValue true
1001|[2023-11-24 10:45:05]ERROR : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
1002|[2023-11-24 10:45:05]INFO : Arrêt du démon ZwaveJS
1003|[2023-11-24 10:45:06]DEBUG : [configureSettings] Informations reçues de MQTT Manager : {"ip":"127.0.0.1","port":"1883","user":"jeedom","password":"qR4FUNYkUmlay3Atb94T4MYYZl3tQbnDh0Q7skfLAbaqi2xlFRIJSrh1qU3QitFC"}
1004|[2023-11-24 10:45:06]INFO : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=E1352DA0E19C9F28EDF46C063156BA6F KEY_S2_Unauthenticated=F757550B0BD302BC34176979FE499E9C KEY_S2_Authenticated=5BB111A38E0E038703FF6DFFFCDACB01 KEY_S2_AccessControl=9977D1EB0535E0E36B5877030D23F522 SESSION_SECRET=jeedomSession yarn start
1005|[2023-11-24 10:45:17]ERROR : Impossible de démarrer le démon ZwaveJS, consultez les logs