Depuis la mise à jour, il y a quelques jours, du plugin JeeZigBee de la version 1.36 vers 1.37.1 le Demon reste en statut NOK après chaque relance. Je ne sais donc pas pourquoi sachant que tout fonctionnait bien avant cela.
Quelqu’un aurait-il une idée pour m’aider ?
J’ai bien relancé les dépendances plusieurs fois, redémarré et éteins la box également, mais en vain…
Je ne connaissais pas Jeedom jusqu’à peu et y suis venu pour pouvoir piloter mes chauffages via les modules Nodon ZigBee. Alors en ce moment pas de souci avec les radiateurs mais pour le chauffe-eau ça posse quelques soucis.
La procédure est longue et n’a pas fonctionnée du premier coup. Mais j’y suis arrivé et ai pu recharger ma dernière sauvegarde.
Malheureusement même en relançant les dépendances de MQTT puis JeeZigbee j’en suis au même point. Le Demon du plugin JeeZibee se déconnecte.
+ 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://security.debian.org bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:6 http://mirrors.xtom.de/armbian buster InRelease
Reading package lists...
Building dependency tree...
Reading state information...
68 packages can be upgraded. Run 'apt list --upgradable' to see them.
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:6 http://xogium.performanceservers.nl/apt buster 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 68 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:6 http://armbian.hosthatch.com/apt buster 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 68 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:6 http://mirrors.xtom.de/armbian buster 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 68 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
--2024-05-17 16:35:15-- 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% 6.08M 0s
50K ....... 100% 55.2M=0.008s
2024-05-17 16:35:15 (6.83 MB/s) - 'composer-setup.php' saved [58444/58444]
Begin installation of composer
All settings correct for using Composer
Downloading...
Composer (version 2.7.6) successfully installed to: /var/www/html/core/ajax/composer.phar
Use it: php composer.phar
End installation of composer
added 117 packages, and audited 118 packages in 4s
19 packages are looking for funding
run `npm fund` for details
2 moderate severity vulnerabilities
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://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://deb.debian.org/debian bullseye-backports InRelease
Hit:4 http://security.debian.org bullseye-security InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:6 http://armbian.hosthatch.com/apt buster InRelease
Reading package lists...
Building dependency tree...
Reading state information...
68 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ 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://security.debian.org bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 http://deb.debian.org/debian bullseye-backports InRelease
Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:6 http://xogium.performanceservers.nl/apt buster 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 68 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [ 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 68 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
added 795 packages, and audited 796 packages in 22s
86 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
+ npm run build
> zigbee2mqtt@1.37.1 build
> tsc && node index.js writehash
+ 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******************
Le service assistance de Domadoo a pris la main sur ma box pour vérifier le problème.
Que ce soit la remise en V1.36, relancer les dépendances… rien n’y fait. Même débrancher le dongle USB plus d’une heure.
Il semble que ce soit un problème matériel, donc à voir après échange.
Dans l’histoire j’aurais au moins appris à faire un recovery de l’ATLAS et fais une mise à jour de debian !
et fais une mise à jour de debian !