Problème capteur Fibaro Motion Sensor

AleiZ · Juillet 10, 2024, 10:38

Bonjour,

Sur 2 installations Jeedom différentes, j’ai le même soucis depuis la mise à jour de zwavejs (ou suite à un sudo apt-get update/upgrade car j’ai fait les deux l’un après l’autre)
J’ai de multiples capteurs sur pile, sur secteurs principalement Fibaro mais aussi Qubino.
Tous fonctionnent bien sauf…

…certains (pas tous du type 30% sur un total de 12) motion sensor de chez Fibaro. Mais ce qui me surprend c’est qu’ils communiquent.

Un capteur qui ne passe jamais à l’état personne détectée dans l’interface jeedom, va basculer en état « sabotage » si je le déplace.

Je ne comprends vraiment pas:

mes devices zwavejs marchent tous sauf certains devices Fibaro motion sensor FGMS-001
mais même ceux qui ne fonctionnent pas pour le détection de présence (l’état indique aucun changement depuis xx j), la fonction détection d’un sabotage (quand on fait bouger le capteur physiquement) elle fonctionne
j’ai regardé les versions des FW des capteurs mais ce sont les mêmes versions entre un qui marche et un qui marche pas
le même soucis sur deux installations différentes (à base de raspberry pi3b)

Bien-sûr réinstallation des dépendances, redémarrage daemon, redémarrage des raspberry…

Honnêtement je ne vois pas la logique du soucis et je ne sais pas quel logs vous donner pour aider…
Ca ne me semble absolument pas logique car la communication marche avec les modules (sabotage) et tous ne sont pas touchés mais quand même>30% sur des installations totalement différentes.

Si quelqu’un a une idée brillante. Merci

Tonio16 · Juillet 10, 2024, 10:40

Salut

Deja la page santé jeedom et les logs des plugins.

Antoine

Fifirept · Juillet 10, 2024, 2:10

Bonjour,

Quels sont les réglages de sensibilité ?
Voilà les miens. ils fonctionnent parfaitement.

AleiZ · Juillet 10, 2024, 2:16

C’est vraiment suite à une MAJ et le capteur me voit bien passé (il clignote).

Je regarde ce soir pour donner les logs.

AleiZ · Juillet 10, 2024, 3:13

Santé Jeedom:

Log d’installation de dépendances:

+ 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
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
apt: no process found
apt-get: no process found
unattended-upgr: no process found

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Get:3 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Fetched 53.9 kB in 3s (20.9 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Get:3 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Fetched 53.9 kB in 2s (21.8 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 2s (22.6 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 3s (20.0 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
--2024-07-10 15:28:21--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'

     0K .......... .......... .......... .......... .......... 87% 2.21M 0s
    50K .......                                               100% 27.0M=0.02s

2024-07-10 15:28:21 (2.50 MB/s) - 'composer-setup.php' saved [58444/58444]

Begin installation of composer
All settings correct for using Composer
Downloading...

Composer (version 2.7.7) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar

End installation of composer

added 110 packages, and audited 111 packages in 14s

13 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (3 moderate, 1 high)

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
Synchronizing state of mosquitto.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mosquitto
+ 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://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 3s (17.8 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ 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://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 4s (12.9 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ 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://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 3s (19.2 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ 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://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x buster InRelease
Get:4 https://download.docker.com/linux/debian buster InRelease [53.9 kB]
Fetched 53.9 kB in 5s (11.7 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u9).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ 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-07-10 15:30:47--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 54.36.53.46, 2001:41d0:302:1100::8:104f
Connecting to getcomposer.org (getcomposer.org)|54.36.53.46|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58444 (57K) [application/octet-stream]
Saving to: 'composer-setup.php'

     0K .......... .......... .......... .......... .......... 87% 2.00M 0s
    50K .......                                               100% 8.04M=0.03s

2024-07-10 15:30:47 (2.21 MB/s) - 'composer-setup.php' saved [58444/58444]

All settings correct for using Composer
Downloading...

Composer (version 2.7.7) 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 12s
+ 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 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 476.64s.
+ sudo NODE_OPTIONS=--max_old_space_size=2048 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.09 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.53 kB
dist/assets/ZwaveGraph-fe07d4ee.css                 220.27 kB │ gzip:  31.14 kB
dist/assets/index-fc01ccc5.css                      645.37 kB │ gzip:  86.89 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.44 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.62 kB
dist/assets/DialogAdvanced-5b2d0ec5.js                1.31 kB │ gzip:   0.68 kB
dist/assets/StatisticsArrows-12aabae4.js              1.35 kB │ gzip:   0.72 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.19 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.56 kB
dist/assets/ListInput-8b4ffe3f.js                     4.39 kB │ gzip:   1.42 kB
dist/assets/mdi-084c837b.js                           4.53 kB │ gzip:   1.60 kB
dist/assets/OTAUpdates-55c8bbff.js                    5.13 kB │ gzip:   2.12 kB
dist/assets/Scenes-523c80fa.js                        5.72 kB │ gzip:   1.94 kB
dist/assets/prismeditor.esm-bb9d1a0f.js               7.58 kB │ gzip:   2.70 kB
dist/assets/NodeScheduler-ebf31fcf.js                 7.86 kB │ gzip:   2.60 kB
dist/assets/HomeAssistant-42c8c444.js                 8.24 kB │ gzip:   2.44 kB
dist/assets/DialogGatewayValue-ef1b3b2f.js            8.29 kB │ gzip:   2.52 kB
dist/assets/ControlPanel-bdb0d994.js                  9.49 kB │ gzip:   3.47 kB
dist/assets/SmartView-28c7cc69.js                     9.89 kB │ gzip:   3.23 kB
dist/assets/ValueId-522cc7fe.js                      10.46 kB │ gzip:   2.94 kB
dist/assets/Store-8ae386ab.js                        10.86 kB │ gzip:   3.37 kB
dist/assets/NodeDetails-66598c59.js                  12.13 kB │ gzip:   3.36 kB
dist/assets/DialogHealthCheck-e1171a78.js            12.39 kB │ gzip:   3.60 kB
dist/assets/SmartStart-529bd83c.js                   12.78 kB │ gzip:   3.78 kB
dist/assets/ExpandedNode-0d2f9348.js                 14.94 kB │ gzip:   5.05 kB
dist/assets/NodePanel-95fd071c.js                    15.39 kB │ gzip:   4.23 kB
dist/assets/Debug-56b9ab16.js                        16.32 kB │ gzip:   4.16 kB
dist/assets/QrReader-de63e501.js                     20.90 kB │ gzip:   7.29 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.40 kB
dist/assets/BgRssiChart-e3ca1964.js                  54.99 kB │ gzip:  24.07 kB
dist/assets/vuedraggable.umd-b288d476.js             71.04 kB │ gzip:  24.84 kB
dist/assets/Settings-48e5e2be.js                     74.67 kB │ gzip:  18.60 kB
dist/assets/index-db198434.js                       104.95 kB │ gzip:  41.40 kB
dist/assets/ZwaveGraph-fc4291af.js                  561.14 kB │ gzip: 165.35 kB
dist/assets/index-bfe5f650.js                     1,178.22 kB │ gzip: 322.59 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.27 kB
✓ built in 8.28s

PWA v0.16.7
mode      injectManifest
precache  73 entries (3171.22 KiB)
files generated
  dist/sw.js
✓ built in 4m 11s
Done in 390.35s.
+ 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
++ tr -d ' '
++ grep Revision /proc/cpuinfo
++ cut -d: -f2
+ RPI_BOARD_REVISION=a020d3
+ [[ a020d3 == \a\0\2\0\8\2 ]]
+ [[ a020d3 == \a\2\2\0\8\2 ]]
+ [[ a020d3 == \a\0\2\0\d\3 ]]
+ systemctl disable hciuart
++ grep dtoverlay=pi3-miniuart-bt /boot/config.txt
+ [[ ! -n dtoverlay=pi3-miniuart-bt ]]
+ 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******************

Log zwavejsd

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-07-10 15:50:33.988e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-07-10 15:50:34.036e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-07-10 15:50:34.265e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found
(node:5546) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 1001 drain listeners added to [Socket]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

Et voici le second jeedom qui a les mêmes soucis:
Page santé

et les logs

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-07-10 17:35:26.761e[39m e[32mINFOe[39m e[1mAPPe[22m: Version: 9.12.0.96eeb76
e[90m2024-07-10 17:35:26.789e[39m e[32mINFOe[39m e[1mAPPe[22m: Application path:/var/www/html/plugins/zwavejs/resources/zwave-js-ui
______  __          __                      _  _____     _    _ _____
|___  /  \ \        / /                     | |/ ____|   | |  | |_   _|
/ /____\ \  /\  / /_ ___   _____         | | (___     | |  | | | |
/ /______\ \/  \/ / _' \ \ / / _ \    _   | |\___ \    | |  | | | |
/ /__      \  /\  / (_| |\ V /  __/   | |__| |____) |   | |__| |_| |_
/_____|      \/  \/ \__,_| \_/ \___|    \____/|_____/     \____/|_____|
e[90m2024-07-10 17:35:26.912e[39m e[33mWARNe[39m e[1mSTOREe[22m: scenes.json not found

Tonio16 · Juillet 10, 2024, 3:27

Vous avez un service intégré pour les images. Les modérateurs vont probablement enlever celle hepébergée en extérieur.

ANTOINE

Mips · Juillet 10, 2024, 5:52

Salut,

Sur l’un de mes capteurs suite à la dernière maj j’ai du changer la config des commandes.
Testez avec l’écran valeur du module pour vérifier laquelle remonte en cas de mouvement et adapter la commande présence en conséquence.

AleiZ · Juillet 10, 2024, 6:24

Merci. J’ai fait régénérer les commandes en enlevant les anciennes et aussi comparé tous les champs entre un module motion sensor qui marche et un qui ne marche pas et ils sont strictement identiques.

Je vais probablement desapparairer et reappairer mais sur l’autre jeedom que je gère en remote je ne vais pas pouvoir

Mips · Juillet 10, 2024, 6:29

Mais non ca ne sert à rien d’exclure.
Ne régénérez pas les commandes à l’aveugle, faites ce que j’ai dit et ca fonctionnera

AleiZ · Juillet 10, 2024, 8:05

J’y avais déjà passé 3h, là je viens d’exclure et réinclure 20 modules (j’ai refait aussi les sirenes alarme, sirene incendie…), je repars avec des commandes dernières version et ça fonctionne.

Avant d’avoir fait ça, je peux t’assurer que ça ne bougeait pas du tout ici même quand je passais devant:

Sur le jeedom remote (chez mes beaux parents) j’essaierai d’investiguer plus quand j’y serai mais là il me fallait une alarme qui fonctionne de façon certaine dès demain donc j’ai fait la solution bourrin.

Il n’empêche que deux jeedoms distants avec des OS installés à des périodes différentes qui ont le même soucis sur les mêmes capteurs, je ne pense pas que ça vienne d’une fausse manip de ma part. On va voir si je suis le seul

EDIT: je viens de regarder sur le jeedom remote.

=> le general purpose semble être le bon, mais c’est quand même bizarre ce bazar de commande… j’ai créé une commande on va voir mais comme c’est pas chez moi, je vais devoir me faire un avis selon l’heure de coucher de mes beaux parents

system · Septembre 29, 2024, 7:01

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.