Il y a un menu dans jedom mais je ne l’ai jamais utilisé.
Antoine
1 « J'aime »
Merci pour ces informations. Je vais essayer de suivre toutes ces instructions.
sinon, Réglages > Système > Configuration, Onglet OS/DB > Administration Système puis à gauche : Dpkg configure
Y a ca aussi a voir
non, c’est lié, si pas de dpkg fonctionnel NodeJS pourra j’amais s’installer. donc en résolvant son problème de dpkg il résoud aussi nodejs
J’ai envoyé ta demande dans un nouveau sujet, c’est mieux que de squatter celui des autres 
Je t’invite à lire ce post qui explique comment faire des bons posts et ne plus faire ce genre d’erreurs à l’avenir : Comment nous aider à vous aider - ou Comment poser une bonne question?
1 « J'aime »
Désolé pour cette erreur, je vais lire le lien et faire attention le prochaines fois.
Merci d’avoir créé un nouveau sujet
Si j’ai bien compris je doit saisir " sudo dpkg --configure -a " dans la ligne de commande Dpkg configure pour corriger le problème.
non tu cliques juste sur Dpkg configure et ça le fait pour toi ! puis tu relances les dépendances du plugin.
Malheureusement cela n’a pas fonctionné.
J’ai donc redémarrer la box LUNA relancé les dépendances mais le DEMON ne veut pas démarrer.
tu connais la chanson, sans les logs c’est comme aller chez le docteur et dire « J’ai mal ».
Fournis le log des dépendances du plugin et _packages aussi
Log update
[START UPDATE]
[PROGRESS][1]
****Update from 4.3.21 (2024-01-02 15:37:46)****
Parameters : {"preUpdate":"0","backup::before":"0","plugins":"0","core":"1","force":"0","update::reapply":""}
Send begin of update event...OK
[PROGRESS][5]
Check rights...
OK
[PROGRESS][10]
[PROGRESS][15]
Download url : https://github.com/jeedom/core/archive/V4-stable.zip
Download in progress...--2024-01-02 14:37:50-- https://github.com/jeedom/core/archive/V4-stable.zip
Resolving github.com (github.com)... 140.82.121.3
Connecting to github.com (github.com)|140.82.121.3|:443... connected.
HTTP request sent, awaiting response...
302 Found
Location: https://codeload.github.com/jeedom/core/zip/refs/heads/V4-stable [following]
--2024-01-02 14:37:50-- https://codeload.github.com/jeedom/core/zip/refs/heads/V4-stable
Resolving codeload.github.com (codeload.github.com)... 140.82.121.10
Connecting to codeload.github.com (codeload.github.com)|140.82.121.10|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 82253287 (78M) [application/zip]
Saving to: '/tmp/jeedom/install/jeedom_update.zip'
0K ........ ........ .
....... ........ ........ ........ 3% 1.85M 41s
3072K .......
. ........ ........ ........ ........ ......
.. 7% 2.15M 36s
6144K ........ ........ ........ ........ .....
... ........ 11% 2.14M 34s
9216K ........ ........ ........ .
....... ........ ........ 15% 2.10M 32s
12288K ........ ........
........ ........ ........ ........ 19% 2.16M 31s
15360K .......
. ........ ........ ........ ........ .....
... 22% 2.14M 29s
18432K ........ ........ ........ ........ ........ ......
.. 26% 2.12M 28s
21504K ........ ........ ........ .......
. ........ ........ 30% 1.96M 26s
24576K ........ ........ ......
.. ........ ........ ........ 34% 2.20M 25s
27648K ........ ......
.. ........ ........ ........ ........ 38% 2.15M 23s
30720K .......
. ........ ........ ........ ........ .......
. 42% 2.08M 22s
33792K ........ ........ ........ ........ .......
. ........ 45% 2.15M 20s
36864K ........ ........ ........ .......
. ........ ........ 49% 2.18M 19s
39936K ........ ........ .....
... ........ ........ ........ 53% 2.12M 17s
43008K ........ ....
.... ........ ........ ........ ........ 57% 2.18M 16s
46080K ..
...... ........ ........ ........ ........
........ 61% 2.09M 14s
49152K ........ ........ ........ .....
... ........ ........ 65% 2.15M 13s
52224K ........ ........ ....
.... ........ ........ ........ 68% 2.16M 12s
55296K ........ ..
...... ........ ........ ........ .......
. 72% 2.07M 10s
58368K ........ ........ ........ ........ .....
... ........ 76% 2.16M 9s
61440K ........ ........ ........ .....
... ........ ........ 80% 2.16M 7s
64512K ........ ........ ....
.... ........ ........ ........ 84% 2.17M 6s
67584K ........ ..
...... ........ ........ ........ ........ 87% 2.15M 4s
70656K ........ ........ ........ ........ ......
.. ........ 91% 2.11M 3s
73728K ........ ........ ........ .....
... ........ ........ 95% 2.21M 2s
76800K ........ ........ ...
..... ........ ........ ........ 99% 2.15M 0s
79872K ....... 100% 1.91M=37s
2024-01-02 14:38:28 (2.12 MB/s) - '/tmp/jeedom/install/jeedom_update.zip' saved [82253287/82253287]
[PROGRESS][25]
OK
Cleaning folders...OK
[PROGRESS][30]
Create temporary folder...OK
[PROGRESS][35]
Unzip in progress...
OK
[PROGRESS][40]
Clean temporary files (tmp)...OK
Disable all task
OK
Disable all scenario.... OK
[PROGRESS][45]
Moving files...
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/de_DE/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/en_US/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/es_ES/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/fr_FR/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/pt_PT/noteVersion.md because size is 0
OK
[PROGRESS][50]
Remove temporary files...OK
[PROGRESS][52]
Remove useless files...
Cleaning 3rdparty
Cleaning desktop
Cleaning mobile
Cleaning core
Cleaning docs
Cleaning install
Cleaning script
find: '/var/www/html/install/../script/*': No such file or directory
Cleaning vendor
[PROGRESS][55]
Check jeedom consistency...
[START CONSISTENCY]
[START CHECK AND FIX DB]
[END CHECK AND FIX DB]
Check jeedom package...
OK
Check jeedom database...OK
Check crons...
Check filesystem right...
OK
Flush cache widget...
Check jeedom object...OK
Check jeedom cmd...OK
Set cache hour...OK
Check nodejs...
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Hit:1 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:2 https://deb.debian.org/debian bullseye InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
Reading package lists...
[Check Version NodeJS actuelle : v16.17.0 : [ KO ]
Installation de NodeJS 18
Utilisation du dépot officiel
deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main
Hit:1 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:2 https://deb.debian.org/debian bullseye InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
Reading package lists...
[Check Version NodeJS après install : v16.17.0 : [ KO ] -> relancez les dépendances
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : : [ KO ]
Reset prefix (/usr) pour npm root
OK
[END CONSISTENCY]
OK
Check update...OK
***************Jeedom is up to date in 4.3.21***************
[PROGRESS][75]
[PROGRESS][90]
Check update
OK
[PROGRESS][95]
Enable scenario : OK
Enable task : OK
[PROGRESS][100]
Launch cron dependancy plugins...
OK
Send end of update event...OK
Update duration : 133s
[END UPDATE SUCCESS]
Log packages
+ 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.6.2'
Wanted Version: 9.6.2
+ rm -R zwave-js-ui
+ git clone --branch v9.6.2 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: switching to '6e369a1bc8fac7ea92a3c069e808a46b42c68a8d'.
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
+ 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.19
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...
error zwave-js-ui@9.6.2: The engine "node" is incompatible with this module. Expected version ">= 18.12". Got "16.17.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
+ sudo yarn run build
yarn run v1.22.19
error zwave-js-ui@9.6.2: The engine "node" is incompatible with this module. Expected version ">= 18.12". Got "16.17.0"
error Commands cannot run with an incompatible environment.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md api certs docker docs esbuild-register.js esbuild.js genereteDocs.ts index.html kubernetes kustomization.yaml nodemon.json package-lock.json package.json package.sh pkg public server_config.js snippets src store test tsconfig.eslint.json tsconfig.json vite.config.js wallaby.js
+ '[' -e /dev/ttyAMA0 ']'
+ '[' -e /dev/ttymxc0 ']'
+ '[' -e /dev/ttyAMA0 ']'
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
++ tr -d ' '
+ RPI_BOARD_REVISION=
+ [[ '' == a\8 ]]
+ [[ '' == a\8 ]]
+ [[ '' == a\d ]]
+ echo 'Everything is successfully installed!'
Everything is successfully installed!
+ echo 4
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end zwavejs
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************
tu vas dans Réglages > Système > Configuration, Onglet OS/DB > Vérification Générale et tu fournis le log qui s’affiche (une fois qu’il a terminé évidemment)
1 « J'aime »
Log de vérification générale. La vérification me semble rapide. juste quelques secondes est-ce normale?
[START CONSISTENCY]
[START CHECK AND FIX DB]
[END CHECK AND FIX DB]
Check jeedom package...
OK
Check jeedom database...OK
Check crons...
Check filesystem right...
OK
Flush cache widget...
Check jeedom object...OK
Check jeedom cmd...OK
Set cache hour...OK
Check nodejs...
c’est la dernière partie qui nous intéresse (nodejs), elle est toujours en cours 
attend [STOP CONSISTENCY]
la c’est mieux
[START CONSISTENCY]
[START CHECK AND FIX DB]
[END CHECK AND FIX DB]
Check jeedom package...
OK
Check jeedom database...OK
Check crons...
Check filesystem right...
OK
Flush cache widget...
Check jeedom object...OK
Check jeedom cmd...OK
Set cache hour...OK
Check nodejs...
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:3 https://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (2.2.4).
build-essential is already the newest version (12.9).
git is already the newest version (1:2.30.2-1+deb11u2).
lsb-release is already the newest version (11.1.0).
0 upgraded, 0 newly installed, 0 to remove and 95 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
OK
[END CONSISTENCY]
ok maintenant tu relances les dep du plugin
l’installation des dépendances est en cours et ne s’est pas arrêtée au bout de 4 secondes comme avant. Je laisse les choses se faire tranquillement et je mettrais un message du résultat.
Le DEMON a redémarrer !
Mon réseau Zwave semble ok car les températures de mon thermostat et des tête thermostatique se sont mises à jour.
MERCI beaucoup pour l’aide!!! Vraiment au top !!!
1 « J'aime »