Bonjour à tous,
Je rencontre un problème avec certains de mes équipements zigbee depuis que j’ai supprimé un module secteur LLKZMK11LM.
Je suppose que c’est lié au mapping car celui-ci était placé haut (dans le grenier) et je pense qu’il était le point de passage.
Equipements HS : ruban et ampoule Philips Hue, dimmable Ikea
Test avec une télécommande Philips Hue, aucun problème : Hue dimmer switch
Voici les logs lorsque je tente d’éteindre une lumière :
info 2024-09-20 10:14:02z2m: Interviewing '0x0017880103e00138'
info 2024-09-20 10:15:23z2m: Configuring '0x0017880103e00138'
info 2024-09-20 10:15:33z2m: Successfully configured '0x0017880103e00138'
info 2024-09-20 10:15:33z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/configure', payload '{"data":{"id":"0x0017880103e00138"},"status":"ok","transaction":"7168r-2"}'
error 2024-09-20 10:16:11z2m: Publish 'set' 'state' to '0x0017880103e00138' failed: 'Error: ZCL command 0x0017880103e00138/11 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (no response received (37) waiting for response TIMEOUT)'
info 2024-09-20 10:16:11z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Publish 'set' 'state' to '0x0017880103e00138' failed: 'Error: ZCL command 0x0017880103e00138/11 genOnOff.off({}, {\"timeout\":10000,\"disableResponse\":false,\"disableRecovery\":false,\"disableDefaultResponse\":false,\"direction\":0,\"reservedBits\":0,\"writeUndiv\":false}) failed (no response received (37) waiting for response TIMEOUT)'","meta":{"friendly_name":"0x0017880103e00138"},"type":"zigbee_publish_error"}'
error 2024-09-20 10:17:10z2m: Failed to execute LQI for '0x0017880103e00138'
error 2024-09-20 10:22:04z2m: Request 'zigbee2mqtt/bridge/request/device/interview' failed with error: 'interview of '0x0017880103e00138' (0x0017880103e00138) failed: Error: Interview failed because can not get active endpoints ('0x0017880103e00138')'
info 2024-09-20 10:22:04z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/response/device/interview', payload '{"data":{},"error":"interview of '0x0017880103e00138' (0x0017880103e00138) failed: Error: Interview failed because can not get active endpoints ('0x0017880103e00138')","status":"error","transaction":"7168r-1"}'
J’ai réinstallé les dépendances du plugin z2m et de MQTT mais j’ai toujours des problèmes.
+ 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
+ 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://security.debian.org/debian-security bullseye-security InRelease
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
Fetched 44.1 kB in 0s (97.4 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://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_20.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).
lsb-release is already the newest version (11.1.0).
git is already the newest version (1:2.30.2-1+deb11u3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v20.17.0 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
Clean npm cache
npm warn using --force Recommended protections disabled.
+ 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 warn deprecated 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.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
added 790 packages, and audited 791 packages in 12s
87 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.
+ npm run build
> zigbee2mqtt@1.40.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
+ echo 10
+ rm /tmp/jeedom_install_in_progress_z2m
+ echo '*******************End of package installation******************'
*******************End of package installation******************
Le mapping:
Quand je débranche une ampoule qui ne répond pas et que je la rebranche, je la vois bien communiquer.
Aucun problème du côté du réseau Zwave.
Pouvez-vous m’aider ?
Merci par avance.
Mathieu
