Tu ne vois pas sur les copies d’écran que je t’ai envoyé ?
On les trouve où ces log ?
Il faut déjà prendre les problèmes dans l’ordre et pas tout mélanger
sudo apt-get --allow-releaseinfo-change update
sudo apt update
sudo apt upgrade
Est-ce que cela a été fait et quel est le résultat ?
A faire en ssh en se connectant via putty ou autre soft à la box Jeedom
Ensuite, relancer l’installation des dépendances zwavejs
Le log des dépendances est là
zwavejs_packages
Donc log a fournir en copier coller ici entre balises afin que l’on voit ce qui bloque.
Entre balises c’est ici
1 « J'aime »
J’ai fait ça par Réglages/Configuration/OS/DB/Administration système
Voilà ce que j’ai après Sudo apt upgrade
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
cloud-init
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 467 kB of archives.
After this operation, 263 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian buster/main arm64 cloud-init all 20.2-2~deb10u2 [467 kB]
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Fetched 467 kB in 0s (6961 kB/s)
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 76309 files and directories currently installed.)
Preparing to unpack .../cloud-init_20.2-2~deb10u2_all.deb ...
Unpacking cloud-init (20.2-2~deb10u2) over (18.3-6) ...
Setting up cloud-init (20.2-2~deb10u2) ...
Configuration file '/etc/cloud/cloud.cfg'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** cloud.cfg (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package cloud-init (--configure):
end of file on stdin at conffile prompt
Processing triggers for systemd (241-7~deb10u10) ...
Processing triggers for rsyslog (8.1901.0-1+deb10u2) ...
Errors were encountered while processing:
cloud-init
E: Sub-process /usr/bin/dpkg returned an error code (1)
Déjà ça est-ce c’est correct ?
Donc sans etre connecté en ssh à la box jeedom rien que la dessus tu ne peux répondre a ce que ca demande…
Concernant les autres commandes, on a pas le retour non plus.
Allez c’est bon je passe mon tour…
Désolé mais tu as sans doute compris que je ne suis pas un expert sur linux …
et pour les log de dépendances ça n’arrête pas de tourner donc j’attends que ce soit fini avant de les poster
La question n’est pas d’être débutant ou pas, ni d’être expert linux ou pas.
L’aide que l’on peut apporter dépends de ce que la personne nous donne comme info ou pas vu qu’on est pas devant la machine incriminée.
On ne peut donc pas deviner le résultat des actions que l’on demande.
Donc si on reprend
Il y a 3 commandes, la 1ere est importante sous debian 10 puisque cet OS est has been.
En réponse j’ai
« Voilà ce que j’ai après Sudo apt upgrade »
Donc il faut deviner ce que donne la première commande ?
De plus les commandes linux de ce type doivent être faite en étant connecté à l’OS de la box jeedom pas via le menu OS/DB
Bonjour,
Dep zwavejs NOK.
Log Zwavejs_packages ?
akenad 
Ben oui, ca fait juste 3 fois que je les demande aussi…
Bon on va reprendre tout ça et essayer de répondre à ta demande :
sudo apt-get --allow-releaseinfo-change update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists... Done
sudo apt update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 http://deb.debian.org/debian buster-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
sudo apt list --upgradable
Listing... Done
cloud-init/oldoldstable 20.2-2~deb10u2 all [upgradable from: 18.3-6]
N: There are 2 additional versions. Please use the '-a' switch to see them.
sudo apt list --upgradable -a
Listing... Done
cloud-init/oldoldstable 20.2-2~deb10u2 all [upgradable from: 18.3-6]
cloud-init/buster-backports 20.2-2~bpo10+1 all
cloud-init/now 18.3-6 all [installed,upgradable to: 20.2-2~deb10u2]
sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
cloud-init
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 467 kB of archives.
After this operation, 263 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://deb.debian.org/debian buster/main arm64 cloud-init all 20.2-2~deb10u2 [467 kB]
Fetched 467 kB in 0s (3,144 kB/s)
(Reading database ... 76309 files and directories currently installed.)
Preparing to unpack .../cloud-init_20.2-2~deb10u2_all.deb ...
Unpacking cloud-init (20.2-2~deb10u2) over (18.3-6) ...
Setting up cloud-init (20.2-2~deb10u2) ...
Configuration file '/etc/cloud/cloud.cfg'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** cloud.cfg (Y/I/N/O/D/Z) [default=N] ? N
Installing new version of config file /etc/cloud/cloud.cfg.d/README ...
Installing new version of config file /etc/cloud/templates/chef_client.rb.tmpl ...
Installing new version of config file /etc/cloud/templates/ntp.conf.debian.tmpl ...
Installing new version of config file /etc/cloud/templates/resolv.conf.tmpl ...
Installing new version of config file /etc/cloud/templates/sources.list.ubuntu.tmpl ...
Installing new version of config file /etc/profile.d/Z99-cloud-locale-test.sh ...
Processing triggers for systemd (241-7~deb10u10) ...
Processing triggers for rsyslog (8.1901.0-1+deb10u2) ...
Je ne savais pas quoi répondre à
cloud.cfg (Y/I/N/O/D/Z) [default=N] ?
J’ai répondu N …
Maintenant le log d’installation des dependances du plugin zwavejs
J’ai redémarré ma VM de Jeedom afin d’être sûr que les modif soient pris en compte.
Zwavejsd
e[90m2024-02-03 07:37:56.695e[39m e[31mERRORe[39m e[1mAPPe[22m: Unhandled Rejection, reason: ZWaveError: The controller is not yet ready! (ZW0103)
ZWaveError: The controller is not yet ready! (ZW0103)
at Driver.get controller [as controller] (/var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:752:10)
at /var/www/html/plugins/zwavejs/resources/zwave-js-ui/node_modules/zwave-js/src/lib/driver/Driver.ts:1614:43
Donc on attends encore les logs d’installation des dépendances du plugin…
J’ai relancé les dépendances, ça a demandé longtemps, voici les logs avant démarrage du demon celui-ci est NOK:
Zwavejs_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: checking out '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 performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
+ 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.21
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 vite-plugin-pwa > workbox-build > rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
warning vite-plugin-pwa > workbox-build > @surma/rollup-plugin-off-main-thread > magic-string > sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " > vis-data@7.1.9" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
warning " > vis-data@7.1.9" has unmet peer dependency "vis-util@^5.0.1".
warning " > vis-network@9.1.9" has unmet peer dependency "@egjs/hammerjs@^2.0.0".
warning " > vis-network@9.1.9" has unmet peer dependency "component-emitter@^1.3.0".
warning " > vis-network@9.1.9" has unmet peer dependency "keycharm@^0.2.0 || ^0.3.0 || ^0.4.0".
warning " > vis-network@9.1.9" has unmet peer dependency "uuid@^3.4.0 || ^7.0.0 || ^8.0.0 || ^9.0.0".
warning " > vis-network@9.1.9" has unmet peer dependency "vis-util@^5.0.1".
warning " > @babel/register@7.23.7" has unmet peer dependency "@babel/core@^7.0.0-0".
warning " > esbuild-register@3.5.0" has unmet peer dependency "esbuild@>=0.12 <1".
warning " > vite-plugin-pwa@0.16.7" has unmet peer dependency "workbox-build@^7.0.0".
warning " > vite-plugin-pwa@0.16.7" has unmet peer dependency "workbox-window@^7.0.0".
[5/5] Building fresh packages...
success Saved lockfile.
Done in 266.46s.
+ sudo yarn run build
yarn run v1.22.21
$ npm-run-all 'build:*'
$ tsc
$ vite build
vite v4.5.2 building for production...
transforming...
✓ 560 modules transformed.
rendering chunks...
computing gzip size...
dist/registerSW.js 0.14 kB
dist/manifest.webmanifest 0.50 kB
dist/index.html 1.68 kB │ gzip: 0.74 kB
dist/assets/MaterialIcons-Regular-5743ed3d.woff2 125.12 kB
dist/assets/MaterialIcons-Regular-e69d687a.eot 143.45 kB
dist/assets/MaterialIcons-Regular-11ec382a.woff 160.58 kB
dist/assets/MaterialIcons-Regular-29c11fa5.ttf 347.59 kB
dist/assets/DialogHealthCheck-2228ed6c.css 0.04 kB │ gzip: 0.06 kB
dist/assets/DialogGatewayValue-911dd212.css 0.06 kB │ gzip: 0.08 kB
dist/assets/NodeDetails-da00c417.css 0.06 kB │ gzip: 0.08 kB
dist/assets/Settings-5ef4a95d.css 0.08 kB │ gzip: 0.09 kB
dist/assets/QrReader-00dee3fb.css 0.09 kB │ gzip: 0.10 kB
dist/assets/NodePanel-40067732.css 0.09 kB │ gzip: 0.10 kB
dist/assets/RichValue-3ea76a33.css 0.13 kB │ gzip: 0.12 kB
dist/assets/Mesh-1b8d31eb.css 0.26 kB │ gzip: 0.20 kB
dist/assets/ValueId-d2938c42.css 0.31 kB │ gzip: 0.18 kB
dist/assets/ExpandedNode-9f727a42.css 0.39 kB │ gzip: 0.26 kB
dist/assets/index-fe59274b.css 0.39 kB │ gzip: 0.14 kB
dist/assets/DialogAdvanced-eaabda04.css 0.45 kB │ gzip: 0.23 kB
dist/assets/Store-a58f7130.css 0.79 kB │ gzip: 0.33 kB
dist/assets/BgRssiChart-3e7d7555.css 1.66 kB │ gzip: 0.71 kB
dist/assets/Login-1826b0a1.css 5.43 kB │ gzip: 1.53 kB
dist/assets/ZwaveGraph-fe07d4ee.css 220.27 kB │ gzip: 31.14 kB
dist/assets/index-080a55d8.css 645.26 kB │ gzip: 86.84 kB
dist/assets/items-a860d138.js 0.15 kB │ gzip: 0.15 kB
dist/assets/ControllerChart-08aad2cd.js 0.54 kB │ gzip: 0.34 kB
dist/assets/ColumnFilterBoolean-1f3509ac.js 0.70 kB │ gzip: 0.43 kB
dist/assets/ReinterviewBadge-ae8f9a53.js 0.77 kB │ gzip: 0.51 kB
dist/assets/BlinkIcon-cea0d624.js 0.86 kB │ gzip: 0.42 kB
dist/assets/ColumnFilterDate-740f5b20.js 1.20 kB │ gzip: 0.57 kB
dist/assets/ColumnFilterString-1c29472e.js 1.26 kB │ gzip: 0.62 kB
dist/assets/StatisticsArrows-073d1d4c.js 1.28 kB │ gzip: 0.70 kB
dist/assets/DialogAdvanced-827091ca.js 1.31 kB │ gzip: 0.68 kB
dist/assets/ErrorPage-a4a5f8fc.js 1.54 kB │ gzip: 0.77 kB
dist/assets/ColumnFilterNumber-50e501cf.js 1.77 kB │ gzip: 0.75 kB
dist/assets/file-input-154ca099.js 1.84 kB │ gzip: 0.86 kB
dist/assets/RichValue-b9debeeb.js 2.06 kB │ gzip: 0.87 kB
dist/assets/StatisticsCard-86378e6f.js 2.56 kB │ gzip: 1.00 kB
dist/assets/Mesh-6d811d42.js 2.87 kB │ gzip: 1.20 kB
dist/assets/DialogSceneValue-7913911b.js 3.09 kB │ gzip: 1.19 kB
dist/assets/ColumnFilter-abbfacad.js 3.50 kB │ gzip: 1.21 kB
dist/assets/UserCodeTable-e026450a.js 4.04 kB │ gzip: 1.60 kB
dist/assets/Login-b831285c.js 4.14 kB │ gzip: 1.64 kB
dist/assets/DialogAssociation-5ae19430.js 4.19 kB │ gzip: 1.51 kB
dist/assets/AssociationGroups-294695c6.js 4.36 kB │ gzip: 1.58 kB
dist/assets/ListInput-0e25d82c.js 4.39 kB │ gzip: 1.41 kB
dist/assets/OTAUpdates-adb5280e.js 5.14 kB │ gzip: 2.13 kB
dist/assets/Scenes-a60dff2d.js 5.75 kB │ gzip: 1.94 kB
dist/assets/HomeAssistant-5eb6b045.js 7.57 kB │ gzip: 2.25 kB
dist/assets/prismeditor.esm-d5ed0bab.js 7.58 kB │ gzip: 2.70 kB
dist/assets/NodeScheduler-20b73681.js 7.86 kB │ gzip: 2.60 kB
dist/assets/DialogGatewayValue-a9619165.js 8.29 kB │ gzip: 2.52 kB
dist/assets/SmartStart-1e7ed0b0.js 8.46 kB │ gzip: 2.32 kB
dist/assets/mdi-4fe99e39.js 9.43 kB │ gzip: 3.14 kB
dist/assets/SmartView-c8d8abb7.js 9.93 kB │ gzip: 3.25 kB
dist/assets/ValueId-fb17efa8.js 10.46 kB │ gzip: 2.94 kB
dist/assets/Store-f84e85e4.js 10.91 kB │ gzip: 3.36 kB
dist/assets/NodeDetails-1b0c9815.js 12.14 kB │ gzip: 3.36 kB
dist/assets/DialogHealthCheck-1474b432.js 12.23 kB │ gzip: 3.54 kB
dist/assets/ExpandedNode-4254d606.js 13.99 kB │ gzip: 4.80 kB
dist/assets/NodePanel-125c03e5.js 14.96 kB │ gzip: 4.14 kB
dist/assets/Debug-9b312766.js 16.32 kB │ gzip: 4.16 kB
dist/assets/ControlPanel-c3721c13.js 16.54 kB │ gzip: 5.89 kB
dist/assets/index-d21bac54.js 19.81 kB │ gzip: 5.82 kB
dist/assets/QrReader-49aa7408.js 20.90 kB │ gzip: 7.29 kB
dist/assets/qr-scanner-worker.min-5f44a019.js 43.95 kB │ gzip: 10.40 kB
dist/assets/BgRssiChart-c7ea133e.js 54.80 kB │ gzip: 24.04 kB
dist/assets/vuedraggable.umd-d1a19c07.js 71.04 kB │ gzip: 24.84 kB
dist/assets/Settings-79e84c49.js 72.41 kB │ gzip: 18.26 kB
dist/assets/index-dc9d485c.js 104.95 kB │ gzip: 41.40 kB
dist/assets/ZwaveGraph-8e2160a4.js 561.10 kB │ gzip: 165.29 kB
dist/assets/index-b11b98f4.js 1,152.24 kB │ gzip: 314.30 kB
(!) Some chunks are larger than 500 kBs after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
vite v4.5.2 building for production...
transforming...
✓ 65 modules transformed.
rendering chunks...
computing gzip size...
dist/sw.js 43.54 kB │ gzip: 12.27 kB
✓ built in 920ms
PWA v0.16.7
mode injectManifest
precache 72 entries (3146.28 KiB)
files generated
dist/sw.js
✓ built in 1m 15s
Done in 114.89s.
+ chown -R www-data:www-data CHANGELOG.md LICENSE README.md SECURITY.md api certs dist docker docs esbuild-register.js esbuild.js genereteDocs.ts index.html kubernetes kustomization.yaml node_modules nodemon.json package-lock.json package.json package.sh pkg public server server_config.js snippets src store test tsconfig.eslint.json tsconfig.json vite.config.js wallaby.js yarn.lock
+ '[' -e /dev/ttyAMA0 ']'
+ sudo sed -i 's/console=ttyAMA0,115200//; s/kgdboc=ttyAMA0,115200//' /boot/cmdline.txt
sed: can't read /boot/cmdline.txt: No such file or directory
+ 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
++ cut -d: -f2
++ tr -d ' '
++ grep Revision /proc/cpuinfo
+ RPI_BOARD_REVISION=
+ [[ '' == \8 ]]
+ [[ '' == \8 ]]
+ [[ '' == \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******************
Le temps que je copie ce log ici Jeedom a redémarré tout seul et depuis je n’ai plus aucun log dans Zwavejs
mqttmanager a son démon OK ?
oui tout est OK
Dans l’interface web de zwavejs ui, en haut a droite tu as quoi ?
Ce n’est pas ce que je demande…
De plus il est conseillé d’utiliser le port controleur by serial ID et plus comme tu le fais.
Moi je veux voir la page web de zwavejs ui
