Deamon NOK

bonjour la comu,

je viens demandé a l’aide car je pense a la suite d’une maj je ne parviens plus a faire fonctionner mon plugin z2m… je ne sais pas quoi faire…

voici ce que j’ai:

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_z2m
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
Launch pre-install of z2m dependancy
+ echo 3
+ php /var/www/html/core/class/../php/jeecli.php plugin install mqtt2
apt: no process found
apt-get: 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
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
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
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
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+deb10u8).
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.20.2 : [  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 nodistro InRelease
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+deb10u8).
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.20.2 : [  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 nodistro InRelease
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+deb10u8).
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.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
--2024-04-15 21:58:51--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... failed: Network is unreachable.
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.62M 0s
50K .......                                               100% 34.6M=0.02s
2024-04-15 21:58:52 (2.95 MB/s) - 'composer-setup.php' saved [58444/58444]
Begin installation of composer
All settings correct for using Composer
Downloading...
Composer (version 2.7.2) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
added 115 packages in 4s
18 packages are looking for funding
run `npm fund` 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 nodistro InRelease
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://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
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+deb10u8).
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.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 6
+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-yaml
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
php-yaml is already the newest version (2.0.2+1.3.1-4+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 7
+ sudo systemctl restart apache2
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ echo Launch post-install of z2m dependancy
Launch post-install of z2m dependancy
+ realpath /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ dirname /var/www/html/plugins/z2m/resources/post-install.sh
+ BASEDIR=/var/www/html/plugins/z2m/resources
+ [ -d /var/www/html/plugins/z2m/resources/zigbee2mqtt ]
+ mkdir /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ git clone --depth 1 https://github.com/Koenkk/zigbee2mqtt.git /var/www/html/plugins/z2m/resources/zigbee2mqtt
Cloning into '/var/www/html/plugins/z2m/resources/zigbee2mqtt'...
+ cd /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ [ -f /var/www/html/plugins/z2m/resources/../data/wanted_z2m_version ]
+ npm ci
npm ERR! code ENETUNREACH
npm ERR! syscall connect
npm ERR! errno ENETUNREACH
npm ERR! request to https://registry.npmjs.org/zigbee2mqtt-frontend/-/zigbee2mqtt-frontend-0.6.161.tgz failed, reason: connect ENETUNREACH 2606:4700::6810:1a22:443
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-04-15T19_59_30_136Z-debug-0.log
+ npm run build
> zigbee2mqtt@1.36.1 build
> tsc && node index.js writehash
sh: 1: tsc: not found
+ chown www-data:www-data -R /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ echo 9
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end z2m
PHP Warning:  yaml_parse_file(/var/www/html/plugins/z2m/core/class/../../data/configuration.yaml): failed to open stream: No such file or directory in /var/www/html/plugins/z2m/core/class/z2m.class.php on line 212
+ echo 10
+ rm /tmp/jeedom_install_in_progress_z2m
+ echo '*******************End of package installation******************'
*******************End of package installation******************

> zigbee2mqtt@1.36.1 start
> node index.js
node:internal/modules/cjs/loader:1143
throw err;
^
Error: Cannot find module 'semver'
Require stack:
- /var/www/html/plugins/z2m/resources/zigbee2mqtt/index.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15)
at Module._load (node:internal/modules/cjs/loader:981:27)
at Module.require (node:internal/modules/cjs/loader:1231:19)
at require (node:internal/modules/helpers:177:18)
at Object.<anonymous> (/var/www/html/plugins/z2m/resources/zigbee2mqtt/index.js:1:16)
at Module._compile (node:internal/modules/cjs/loader:1364:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
at Module.load (node:internal/modules/cjs/loader:1203:32)
at Module._load (node:internal/modules/cjs/loader:1019:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/var/www/html/plugins/z2m/resources/zigbee2mqtt/index.js' ]
}
Node.js v18.20.2

merci d'avance

Bonjour,

Pouvez-vous partager la page santé jeedom? (À faire pour chaque demande)

Je rencontre le même problème suite à une réinstalle propre en debian 11 puis restauration.
C’est aussi ce que tu as fait ?

Bonjour, désolé la voici

Pour moi je pense avoir résolu le problème en faisant :

Réglages > Systèmes > Configuration > OS/DB > Rétablissement des droits des dossiers et fichiers
et
Réglages > Systèmes > Configuration > OS/DB > Vérification générale

Si ça peut t’aider

Non rien pour moi :confused: tu a fait une manipulation supplémentaire après ca ?

j’ai redémarré les daemons MQTT puis Z2M

Bon beh j’ai pas plus avancé je redémarré jeedom et maintenant j’ai Alexa Api qui ne lance plus non plus son daemon
:confused:

Bon j’ai refait mon install sur debian 11 n’ayant meme pas fait attention a ce point depuis le temps que mon jeedom tourne sans aucun problème… mais rien de plus :confused: maintenant c’est plutôt du coté de MQTT Manager que ca coince

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_mqtt2
+ echo 1
+ echo 2
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: 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://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ echo 3
+ 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://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 4
+ 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ 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://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  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_composer.sh
+ sudo /var/www/html/core/class/../../resources/install_composer.sh
Begin installation of composer
--2024-04-21 23:01:56--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... failed: Network is unreachable.
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.66M 0s
50K .......                                               100% 33.4M=0.02s
2024-04-21 23:01:56 (3.00 MB/s) - 'composer-setup.php' saved [58444/58444]
All settings correct for using Composer
Downloading...
Composer (version 2.7.3) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
+ echo 7
+ cd /var/www/html/core/class/../../plugins/mqtt2/resources/mqtt2d
+ rm -rf node_modules
+ sudo npm install

Bonjour,

J’ai un peu le même souci que toi avec le plugin JeeZigbee. J’ai essayé pas mal de chose mais rien à faire, le demon ne reste pas actif.

Je vais tenter une installation sur debian 11 sur un autre Rpi. Mais apparemment pour toi, ça a empiré les choses…

J’ai un ticket ouvert, je te tiens au courant si je trouves une solution avec l’aide de l’assistance.

Concernant MQTT je vois que tu as maintenant 2 erreurs pour JeeZigbee. Si les dépendances sont KO sur JeeZigbee ça impact le plugin MQTT, en tout cas chez moi c’est le cas. Une fois les dépendances installées, il est passé au vert.

Bonjour
Pour ce genre de problème il faut poster les logs en particulier les démons sans ça vous dire d’où vient le soucis et trouver le bon c’est autant de chance que de gagner au loto (et pour le moment je fais que perdre…)

Bonjour, si c’est en réponse à mon commentaire, c’était simplement pour indiquer que j’ai un problème similaire. Je ne voulais pas polluer l’échange avec mes logs vu que j’ai un ticket ouvert auprès de l’assistance Jeedom. Ce que je peux dire c’est que j’ai une erreur similaire dans z2m « Error: Cannot find module ‹ semver › ».
Personnellement pour l’instant pas de piste, je vais surement tenter le passage à debian 11.
Bonne journée.

Bonjour,
C’est pour tout le monde, si quand vous avez un soucis de ce type vous postez les logs des dépendances et du démon en general si je passe et que je vois le poste vous avez une réponse rapidement. Si il manque des infos je commence a prendre l’habitude d’aller voir les autres poste du community ou tout est complet.

Bonjour,

Pour information, je viens de recevoir une MAJ du plugin JeedomZeegbee. Après son installation, puis réinstallation de dépendance et relance du demon l’accès à ma clé Conbee II est ok !
Changelog :

22/04/2024

  • Correction d’un bug sur duplication de commande (sur les scenes)
  • Correction d’un bug sur les slider avec valeur negative

bonjour @Loic,

est ce que cela convient ? ce que j’ai quand je relance le demon de JeeZigbee

je n’ai aucune explication mais effectivement coté MQTT Manager depuis la MAJ de JeeZigbee tout semble bon …

en tout cas merci d’avance pour l’aide

> zigbee2mqtt@1.36.1 start
> node index.js
node:internal/modules/cjs/loader:1143
throw err;
^
Error: Cannot find module 'rimraf'
Require stack:
- /var/www/html/plugins/z2m/resources/zigbee2mqtt/index.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15)
at Module._load (node:internal/modules/cjs/loader:981:27)
at Module.require (node:internal/modules/cjs/loader:1231:19)
at require (node:internal/modules/helpers:177:18)
at Object.<anonymous> (/var/www/html/plugins/z2m/resources/zigbee2mqtt/index.js:7:22)
at Module._compile (node:internal/modules/cjs/loader:1364:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
at Module.load (node:internal/modules/cjs/loader:1203:32)
at Module._load (node:internal/modules/cjs/loader:1019:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/var/www/html/plugins/z2m/resources/zigbee2mqtt/index.js' ]
}
Node.js v18.20.2
[2024-04-24 20:00: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
[2024-04-24 20:00:05] INFO  : Arrêt du démon z2m
[2024-04-24 20:00:07] INFO  : Démarrage du démon Z2M : ZIGBEE2MQTT_DATA=/var/www/html/plugins/z2m/core/class/../../data npm start --prefix /var/www/html/plugins/z2m/resources/zigbee2mqtt
[2024-04-24 20:00:18] ERROR  : Erreur sur la fonction deamon_start du plugin : Vous devez attendre au moins 45 secondes entre deux lancements du démon. Dernier lancement : 2024-04-24 20:00:05
[2024-04-24 20:05:04] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-04-24 20:05:04] INFO  : Arrêt du démon z2m
[2024-04-24 20:05:05] INFO  : Démarrage du démon Z2M : ZIGBEE2MQTT_DATA=/var/www/html/plugins/z2m/core/class/../../data npm start --prefix /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_z2m
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/pre-install.sh
Launch pre-install of z2m dependancy
+ 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
--2024-04-24 20:08:39--  https://getcomposer.org/installer
Resolving getcomposer.org (getcomposer.org)... 2001:41d0:302:1100::8:104f, 54.36.53.46
Connecting to getcomposer.org (getcomposer.org)|2001:41d0:302:1100::8:104f|:443... failed: Network is unreachable.
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.40M 0s
50K .......                                               100% 36.3M=0.02s
2024-04-24 20:08:39 (2.71 MB/s) - 'composer-setup.php' saved [58444/58444]
Begin installation of composer
All settings correct for using Composer
Downloading...
Composer (version 2.7.4) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
added 117 packages in 5s
19 packages are looking for funding
run `npm fund` 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 6
+ sudo apt install -o Dpkg::Options::=--force-confdef -y php-yaml
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
php-yaml is already the newest version (2.2.1+2.1.0+2.0.4+1.3.2-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 7
+ sudo systemctl restart apache2
+ echo 8
+ sudo chmod +x /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ sudo /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ echo Launch post-install of z2m dependancy
Launch post-install of z2m dependancy
+ realpath /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
+ dirname /var/www/html/plugins/z2m/resources/post-install.sh
+ BASEDIR=/var/www/html/plugins/z2m/resources
+ [ -d /var/www/html/plugins/z2m/resources/zigbee2mqtt ]
+ rm -rf /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ mkdir /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ git clone --depth 1 https://github.com/Koenkk/zigbee2mqtt.git /var/www/html/plugins/z2m/resources/zigbee2mqtt
Cloning into '/var/www/html/plugins/z2m/resources/zigbee2mqtt'...
+ cd /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ [ -f /var/www/html/plugins/z2m/resources/../data/wanted_z2m_version ]
+ npm ci
npm ERR! Exit handler never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/cli/issues>
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-04-24T18_09_10_826Z-debug-0.log
+ npm run build
> zigbee2mqtt@1.36.1 build
> tsc && node index.js writehash
sh: 1: tsc: not found
+ chown www-data:www-data -R /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ echo 9
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end z2m
PHP Fatal error:  Uncaught Exception: Veuillez vérifier la configuration in /var/www/html/plugins/z2m/core/class/z2m.class.php:299
Stack trace:
#0 /var/www/html/plugins/z2m/core/class/z2m.class.php(37): z2m::deamon_start()
#1 /var/www/html/core/php/jeecli.php(61): z2m::dependancy_end()
#2 {main}
thrown in /var/www/html/plugins/z2m/core/class/z2m.class.php on line 299
+ echo 10
+ rm /tmp/jeedom_install_in_progress_z2m
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Salut,

Pourquoi avoir mis le Port d'écoute de Zigbee2MQTT à 8099 au lieu de 8080 par défaut?

j’ai changé pour des essais mais 8080 génère le meme soucie

C’est pas le port et faut vraiment pas touché à ça si vous savez pas ce que vous faite vous allez casser tout jeedom.

La c’est un soucis dans les dépendances au niveau de l’installation de zigbee2mqtt. Le soucis c’est que la on a rien fait côté jeedom et on maîtrise pas du tout cette partie qui est propre a zigbee2mqtt. Aucune idée de pourquoi leur installeur échoue on dirait qu’il manque typescript (tsc) mais aucune idée de pourquoi….

ok il n’y a rien que je puisse faire du coup ?

j’ai dupliqué mon jeedom sur une seconde carte SD pour passer sur debian 11 j’avoue avoir commencer un peux a toucher a tout ayant une sauvegarde et l’ancien jeedom prêt a démarrer

j’ai heureusement la majorité de mon install qui tourne toujours sur Zigbee Officiel, cela m’ennui pour quelque équipements qui n’avais pas était intégré…

juste une info je sais pas si ca a un impacte ca a quand parfaitement marché pendant plusieurs mois mais j’ai deux combi 2 sur Zigbee et 1 POP sur Z2m

Merci pour les retours