Il n’y a rien j’ai essayé l’appairage mais rien ne se passe j’ai même mis mon inter son/off a coté du dongle des fois que ce soit un problème de porté mais rien y fait.
Ce qui me dérange c’est de ne retrouvé aucune traces de ce dongle.
J’ai principalement du zwave sur mon jeedom et la clé zwave apparait au même titre que n’importe quel device
Tu peux essayer de relancer le demon du plugin
As tu d’autres objets zibee pour essayer ?
Dams
Tu peux également mettre des log
Dams
l’inter son/off fonctionne sur l’appli ewelink et j’ai installer le plugin ewejee et tout fonctionne.
j’aimerais a l’avenir passer en mqtt pour avoir le meme « service » pour tout le zigbee
j’ai mis plus haut le log z2md
le log z2m package
<+ 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
+ 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
+++ dirname /var/www/html/core/class/../../plugins/z2m/resources/post-install.sh
++ cd /var/www/html/core/class/../../plugins/z2m/resources
++ pwd
+ 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
+ npm ci
added 787 packages, and audited 788 packages in 1m
81 packages are looking for funding
run `npm fund` for details
3 moderate severity vulnerabilities
To address all issues, run:
npm audit fix
Run `npm audit` for details.
+ npm run build
> zigbee2mqtt@1.32.1 build
> tsc && node index.js writehash
+ chown www-data:www-data -R /var/www/html/plugins/z2m/resources/zigbee2mqtt
+ echo 4
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end z2m
+ rm /tmp/jeedom_install_in_progress_z2m
+ echo '*******************End of package installation******************'
*******************End of package installation******************>
le log mqtt package
<+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_mqtt2
+ echo 1
+ echo 2
+ 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
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Fetched 15.0 kB in 1s (12.1 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+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 112 not upgraded.
[Check Version NodeJS actuelle : v10.24.0 : [ KO ]
Installation de NodeJS 16
npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/
Utilisation du dépot officiel
## Installing the NodeSource Node.js 16.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists...
## Confirming "buster" is supported...
+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_16.x/dists/buster/Release'
## Adding the NodeSource signing key to your keyring...
+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null
## Creating apt sources list file for the NodeSource Node.js 16.x repo...
+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x buster main' >> /etc/apt/sources.list.d/nodesource.list
## Running `apt-get update` for you...
+ apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:3 https://deb.nodesource.com/node_16.x buster InRelease [4584 B]
Get:4 https://deb.nodesource.com/node_16.x buster/main armhf Packages [785 B]
Fetched 5369 B in 1s (3924 B/s)
Reading package lists...
## Run `sudo apt-get install -y nodejs` to install Node.js 16.x and npm
## You may also need development tools to build native addons:
sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt-get update && sudo apt-get install yarn
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
nodejs
0 upgraded, 1 newly installed, 0 to remove and 110 not upgraded.
Need to get 24.2 MB of archives.
After this operation, 119 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_16.x buster/main armhf nodejs armhf 16.20.1-deb-1nodesource1 [24.2 MB]
Fetched 24.2 MB in 5s (5146 kB/s)
Selecting previously unselected package nodejs.
(Reading database ...
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 67687 files and directories currently installed.)
Preparing to unpack .../nodejs_16.20.1-deb-1nodesource1_armhf.deb ...
Unpacking nodejs (16.20.1-deb-1nodesource1) ...
Setting up nodejs (16.20.1-deb-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
[Check Version NodeJS après install : v16.20.1 : [ OK ]
[Check Prefix : /usr/local and sudo prefix : /usr/local and www-data prefix : /usr : [ KO ]
Reset prefix (/usr) pour npm root
+ 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://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_16.x buster 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 110 not upgraded.
[Check Version NodeJS actuelle : v16.20.1 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
+ echo 4
+ cd /var/www/html/core/class/../../plugins/mqtt2/resources/mqtt2d
+ rm -rf node_modules
+ sudo npm install
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
added 148 packages, and audited 149 packages in 48s
15 packages are looking for funding
run `npm fund` for details
2 moderate severity vulnerabilities
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
npm notice
npm notice New major version of npm available! 8.19.4 -> 9.8.0
npm notice Changelog:
npm notice Run `npm install -g npm@9.8.0` to update!
npm notice
+ chown -R www-data:www-data jeedom mqtt2d.js node_modules package-lock.json package.json
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end mqtt2
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
Generating RSA private key, 2048 bit long modulus (2 primes)
....+++++
................................................................+++++
e is 65537 (0x010001)
Generating RSA private key, 2048 bit long modulus (2 primes)
....................................................................................................+++++
................................................+++++
e is 65537 (0x010001)
Signature ok
subject=C = FR, ST = Paris, L = Paris, O = jeedom, CN = jeedom-mosquitto
Getting CA Private Key
Synchronizing state of mosquitto.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mosquitto
+ rm /tmp/jeedom_install_in_progress_mqtt2
+ echo '*******************End of package installation******************'
*******************End of package installation******************>
Bonjour,
Il faut être sûr des ports des contrôleurs, voir ici : [RTEX] Box Jeedom Atlas - plugin MQTT Manager (mqtt2) Mode Broker local - avec plugins abonnés Z-Wave JS (zwavejs) et JeeZigbee (z2m)
akenad 
pour le port j’ai suivi un tuto qui dit de débrancher le dongle de regarder les ports dispo et de brancher le dongle et de voir le nouveau port qui apparait dans la liste .
De plus j’ai essayé le acm0 et le acm1 et le résultat reste identique
Tu as d’autres log?
Peux tu les mettre entre </>
Dams
les autres log sont vides
total 0
lrwxrwxrwx 1 root root 13 Jul 21 12:51 usb-0658_0200-if00 → …/…/ttyACM0
lrwxrwxrwx 1 root root 13 Jul 22 10:39 usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230509091549-if00 → …/…/ttyACM1
Donc ttyACM1 c’est bon
Relance les dépendances pour voir si ça change quelque chose
Il faudra peut-être mettre les log en début pour avoir plus d’infos
Ta clé est récente ? Il est peut-être nécessaire de la mettre à jour
Dams
la clé est neuve
voici le dernier log
<Killed
zigbee2mqtt@1.32.1 start
node index.js
Killed
zigbee2mqtt@1.32.1 start
node index.js>
Tu as relancé les dépendances ?
Je suis surpris que le port soit acm1.
Il y a quoi comme port usb dans la liste ?
Ps: sonoff
Antoine
désolé j’ai du partir chez des amis.
J’ai bien relancé les dépendances de jeezigbee ( cela n’a rien changé)
je ne sais pas si c’est la réponse que tu attend
<Bus 001 Device 006: ID 1a86:55d4 QinHeng Electronics
Bus 001 Device 004: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub>
Non depuis la page configuration du plugin, la liste dans le menu déroulant.
Antoine
j’ai une soixantaine de choix
dernier log de jeezigbee
<[2023-07-22 11:43:37]ERROR : Attention je pense qu’il y a un soucis avec le démon que j’ai relancé plus de 3 fois consécutivement>
