J’hébergeais récemment mon jeedom dans une VM de la freebox Delta, j’ai eu pas mal de soucis : réduction de la ram à 512Mo, plus de partage du port usb-c, et là elle ne démarre même plus (bloqué au boot cd-rom)
(=> Je vous dis ça juste pour vous donner du context mais ce n’est pas la raison de mon post)
J’ai migré sur un raspberry pi 4, enfin j’essaye !
J’ai UN problème avec le plugin zwave-JS « Le driver Z-Wave n’est pas initialisé » !
J’ai consulté les autres post qui traite ce problème mais je ne m’en sort pas.
À la base ma VM était sous Debian 10 Buster et Jeedom 4.3
J’ai essayé de restaurer une première fois mon backup sous RaspiOS 11 Bubulleye.
Mais j’ai eu le même soucis (de driver zwave) j’ai envisagé que ça venait de là donc j’ai tout recommencé avec RaspiOS 10 Buster (je ferais la migration plus tard).
J’ai essayé :
Changer le port de la clé (Pour info la commande « ls -l /dev/serial/by-id » ne fonctionne pas sur mon raspberry pi, je ne sais pas pourquoi)
Réinstaller les dépendances
Désactiver le Soft Reset
Lancer le démon en mode debug
Qand j’était sous bullseye j’ai même essayé de passer en jeedom 4.4
Les démons de MQTT Manager, jMQTT et Z-Wave JS sont bien démarré.
Si ça peut être utile j’ai l’erreur « scenes.json not found » dans les logs zwavejsd
Je vais mettre en pièce jointe :
Page santé Jeedom
Page config du plugin
Log demon en debug
Je ne sais pas où trouver les logs d’install des dépendances.
Si vous avez besoin d’autre copie d’écran, de log => n’hésitez pas.
S’il le faut vraiment je refait une carte SD avec Bulleye ce soir => je fais ça ?
Ok :
+ 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.12.0'
Wanted Version: 9.12.0
+ rm -R zwave-js-ui
+ git clone --branch v9.12.0 --depth 1 https://github.com/zwave-js/zwave-js-ui
Cloning into 'zwave-js-ui'...
Note: checking out '96eeb76b110f27d3ce16cfb4b3992cb8f8dc34d8'.
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.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 archiver > archiver-utils > glob@8.1.0: Glob versions prior to v9 are no longer supported
warning archiver > archiver-utils > 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 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 c8 > test-exclude > glob@7.2.3: Glob versions prior to v9 are no longer supported
warning c8 > test-exclude > 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 c8 > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning c8 > rimraf > glob@7.2.3: Glob versions prior to v9 are no longer supported
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.11.14: Use @eslint/config-array instead
warning eslint > file-entry-cache > flat-cache > rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
warning eslint > @humanwhocodes/config-array > @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
warning mocha > glob@8.1.0: Glob versions prior to v9 are no longer supported
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 " > 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.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 210.88s.
+ sudo yarn run build
yarn run v1.22.22
$ npm-run-all 'build:*'
$ tsc
$ vite build
vite v4.5.3 building for production...
transforming...
✓ 577 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-81719688.css 0.08 kB │ gzip: 0.10 kB
dist/assets/QrReader-00dee3fb.css 0.09 kB │ gzip: 0.10 kB
dist/assets/NodePanel-c9b9749c.css 0.09 kB │ gzip: 0.10 kB
dist/assets/RichValue-3ea76a33.css 0.13 kB │ gzip: 0.12 kB
dist/assets/Mesh-b27cd214.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-2a960184.css 0.39 kB │ gzip: 0.14 kB
dist/assets/DialogAdvanced-eaabda04.css 0.45 kB │ gzip: 0.23 kB
dist/assets/Store-6f25927f.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.52 kB
dist/assets/ZwaveGraph-fe07d4ee.css 220.27 kB │ gzip: 31.02 kB
dist/assets/index-fc01ccc5.css 645.37 kB │ gzip: 87.03 kB
dist/assets/items-6552f0ec.js 0.26 kB │ gzip: 0.20 kB
dist/assets/ControllerChart-9909c34e.js 0.54 kB │ gzip: 0.34 kB
dist/assets/ColumnFilterBoolean-edeb1b9f.js 0.70 kB │ gzip: 0.43 kB
dist/assets/ReinterviewBadge-6728d903.js 0.77 kB │ gzip: 0.51 kB
dist/assets/BlinkIcon-b93c05e4.js 0.86 kB │ gzip: 0.42 kB
dist/assets/MissingKeysAlert-3919d4d9.js 1.18 kB │ gzip: 0.56 kB
dist/assets/ColumnFilterDate-d9e05459.js 1.20 kB │ gzip: 0.57 kB
dist/assets/ColumnFilterString-43eca2b0.js 1.26 kB │ gzip: 0.63 kB
dist/assets/DialogAdvanced-5b2d0ec5.js 1.31 kB │ gzip: 0.68 kB
dist/assets/StatisticsArrows-12aabae4.js 1.35 kB │ gzip: 0.73 kB
dist/assets/ErrorPage-f699cd87.js 1.56 kB │ gzip: 0.79 kB
dist/assets/ColumnFilterNumber-7fb1a2ee.js 1.77 kB │ gzip: 0.75 kB
dist/assets/file-input-f24a7a76.js 1.84 kB │ gzip: 0.86 kB
dist/assets/RichValue-47394f8b.js 2.06 kB │ gzip: 0.87 kB
dist/assets/StatisticsCard-4b2a40e3.js 2.56 kB │ gzip: 1.00 kB
dist/assets/Mesh-06b54703.js 2.87 kB │ gzip: 1.19 kB
dist/assets/DialogSceneValue-ec18d891.js 3.09 kB │ gzip: 1.18 kB
dist/assets/ColumnFilter-062e5cf3.js 3.50 kB │ gzip: 1.21 kB
dist/assets/UserCodeTable-24821c04.js 4.04 kB │ gzip: 1.59 kB
dist/assets/Login-c1a09dbc.js 4.14 kB │ gzip: 1.64 kB
dist/assets/DialogAssociation-b4eaae4c.js 4.19 kB │ gzip: 1.51 kB
dist/assets/AssociationGroups-26c268dc.js 4.34 kB │ gzip: 1.57 kB
dist/assets/ListInput-8b4ffe3f.js 4.39 kB │ gzip: 1.41 kB
dist/assets/mdi-084c837b.js 4.53 kB │ gzip: 1.58 kB
dist/assets/OTAUpdates-55c8bbff.js 5.13 kB │ gzip: 2.11 kB
dist/assets/Scenes-523c80fa.js 5.72 kB │ gzip: 1.94 kB
dist/assets/prismeditor.esm-bb9d1a0f.js 7.58 kB │ gzip: 2.69 kB
dist/assets/NodeScheduler-ebf31fcf.js 7.86 kB │ gzip: 2.60 kB
dist/assets/HomeAssistant-42c8c444.js 8.24 kB │ gzip: 2.43 kB
dist/assets/DialogGatewayValue-ef1b3b2f.js 8.29 kB │ gzip: 2.51 kB
dist/assets/ControlPanel-bdb0d994.js 9.49 kB │ gzip: 3.47 kB
dist/assets/SmartView-28c7cc69.js 9.89 kB │ gzip: 3.24 kB
dist/assets/ValueId-522cc7fe.js 10.46 kB │ gzip: 2.94 kB
dist/assets/Store-8ae386ab.js 10.86 kB │ gzip: 3.36 kB
dist/assets/NodeDetails-66598c59.js 12.13 kB │ gzip: 3.36 kB
dist/assets/DialogHealthCheck-e1171a78.js 12.39 kB │ gzip: 3.59 kB
dist/assets/SmartStart-529bd83c.js 12.78 kB │ gzip: 3.78 kB
dist/assets/ExpandedNode-0d2f9348.js 14.94 kB │ gzip: 5.04 kB
dist/assets/NodePanel-95fd071c.js 15.39 kB │ gzip: 4.23 kB
dist/assets/Debug-56b9ab16.js 16.32 kB │ gzip: 4.18 kB
dist/assets/QrReader-de63e501.js 20.90 kB │ gzip: 7.30 kB
dist/assets/index-58b7e7b6.js 20.98 kB │ gzip: 6.09 kB
dist/assets/qr-scanner-worker.min-5f44a019.js 43.95 kB │ gzip: 10.46 kB
dist/assets/BgRssiChart-e3ca1964.js 54.99 kB │ gzip: 24.30 kB
dist/assets/vuedraggable.umd-b288d476.js 71.04 kB │ gzip: 24.90 kB
dist/assets/Settings-48e5e2be.js 74.67 kB │ gzip: 18.68 kB
dist/assets/index-db198434.js 104.95 kB │ gzip: 43.04 kB
dist/assets/ZwaveGraph-fc4291af.js 561.14 kB │ gzip: 166.35 kB
dist/assets/index-bfe5f650.js 1,178.22 kB │ gzip: 324.45 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.3 building for production...
transforming...
✓ 65 modules transformed.
rendering chunks...
computing gzip size...
dist/sw.js 43.54 kB │ gzip: 12.25 kB
✓ built in 1.21s
PWA v0.16.7
mode injectManifest
precache 73 entries (3171.22 KiB)
files generated
dist/sw.js
✓ built in 52.61s
Done in 75.53s.
+ 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
+ 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=c03111
+ [[ c03111 == a\8 ]]
+ [[ c03111 == a\8 ]]
+ [[ c03111 == 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
+ echo 5
+ rm /tmp/jeedom_install_in_progress_zwavejs
+ echo '*******************End of package installation******************'
*******************End of package installation******************
Oui ça me semble très étrange, mais clé est une zstick gen5 (normalement)
Dans /dev j’ai ça :
lrwxrwxrwx 1 root root 5 Jun 30 22:05 /dev/serial1 → ttyS0
lrwxrwxrwx 1 root root 7 Jun 30 22:05 /dev/serial0 → ttyAMA0
J’ai essayé les ttyS0 et ttyAMA0.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Je n’y aurai jamais pensé !
Idem je test ce soir j’en ai un sous le coude (je suis à distance là)
Déjà merci à tous, je vous tiens au courant ce soir ou demain.
Hourra ! ça fonctionne
J’ai ajouté un hub USB entre la clé et le rapberry pi 4.
Pour l’anecdote j’ai commencé par un hub avec alimentation séparée, ça ne fonctionnait pas, j’ai ensuite essayé avec un autre hub autoalimenté => et c’est lui qui fonctionne
