# Dongle zigbee cc2652P pas pris en compte par Gladys \[Résolu\] **URL:** \ **Category:** Configuration\ **Tags:** zigbee2mqtt\ **Created:** [Mars 17, 2023, 6:15 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026 "2023-03-17T18:15:04Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![kazuke](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kazuke](https://community.gladysassistant.com/u/kazuke)\ **Post date:** [Mars 17, 2023, 6:15 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/1 "2023-03-17T18:15:04Z")
Bonjour, Après une fraiche insttal, un soucis sur la connection d’un dongle zigbee : « ZBDongle Zigbee 3.0 USB Dongle Plus » lien d’achat : [Amazon.fr](https://www.amazon.fr/dp/B09KXTCMSC?tag=gladproj-21) Puce CC2652P compatible ? Dans configuration du service Zigbee2mqqt croix rouge après MQTT les résultats dans la console : pi@gladys:~ $ lsusb Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 004: ID 0461:4ed3 Primax Electronics, Ltd ACER Predator Gaming Keyboard Bus 001 Device 006: ID 0480:0301 Toshiba America Inc External USB HDD Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub pi@gladys:~ $ ls -l /dev/ttyUSB\* crw-rw---- 1 root dialout 188, 0 Mar 17 13:59 /dev/ttyUSB0 pi@gladys:~ $ ls -l /dev/serial/by-id total 0 lrwxrwxrwx 1 root root 13 Mar 17 13:59 usb-Silicon\_Labs\_Sonoff\_Zigbee\_3.0\_USB\_Dongle\_Plus\_0001-if00-port0 → …/…/ttyUSB0 pi@gladys:~ $ sudo dmesg | grep tty [0.000000] Kernel command line: coherent\_pool=1M 8250.nr\_uarts=0 snd\_bcm2835.enable\_compat\_alsa=0 snd\_bcm2835.enable\_hdmi=1 video=Composite-1:720x480@60i vc\_mem.mem\_base=0x3ec00000 vc\_mem.mem\_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=fbd008b5-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [0.000459] printk: console [tty1] enabled [2.807175] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 99, base\_baud = 0) is a PL011 rev2 [7.475101] systemd[1]: Created slice system-getty.slice. [11.524772] usb 1-1.5: cp210x converter now attached to ttyUSB0 Dois-je retourner cette clé ? Merci pour vos réponses Edit ; image Gladys 32 bits sur rpi 3 b+ ---
**Author:** ![GBoulvin](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/gboulvin/32/10006_2.png) [@GBoulvin](https://community.gladysassistant.com/u/GBoulvin)\ **Post date:** [Mars 17, 2023, 8:44 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/2 "2023-03-17T20:44:04Z")
Salut! Quand tu vas sur la page de configuration du service, tu sélectionnes bien ton dongle dans la liste? ![Screenshot_20230317_214012_com.android.chrome](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/c/cc67adb1917a0e6f5ba5a958af3207eee1eeee32.jpeg) Alors avoir sauvegardé, tu attends suffisamment longtemps (parfois 5-10 minutes la première fois car un téléchargement/déploiement peut avoir lieu)? Ensuite, que donnent les commandes, en ssh, ‹ docker logs gladys-z2m-zigbee2mqtt › et ‹ docker logs gladys › ? ---
**Author:** ![kazuke](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kazuke](https://community.gladysassistant.com/u/kazuke)\ **Post date:** [Mars 17, 2023, 9:22 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/3 "2023-03-17T21:22:39Z")
bonsoir GBoulvin. J’ai déjà une instance Gladys qui tourne sur la freebox. Pas de problème jusqu’à présent. Pour la nouvelle installation, c’est pour un ami. Oui, à tes questions. Pour les logs, je te réponds demain, ne suis pas chez moi ce soir Merci à toi ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [Mars 17, 2023, 10:56 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/4 "2023-03-17T22:56:48Z")
La nouvelle instance est sur un RPI3, et je vois qu’il y a un disque externe usb. As-tu un hub usb alimenté avec le disque dur externe? ---
**Author:** ![kazuke](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kazuke](https://community.gladysassistant.com/u/kazuke)\ **Post date:** [Mars 18, 2023, 8:41 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/5 "2023-03-18T08:41:07Z")
Bonjour Will Non pas de oas de hub alimenté. Je pensais inutile pour un disque SSD. je ferais l’essai avec hub. Comme demandé par GBoulvin : Zigbee2MQTT:info 2023-03-18 08:21:50: Logging to console and directory: ‹ /app/data/log/2023-03-18.08-21-49 › filename: log.txt Zigbee2MQTT:info 2023-03-18 08:21:50: Starting Zigbee2MQTT version 1.30.2 (commit #cdf62ea) Zigbee2MQTT:info 2023-03-18 08:21:50: Starting zigbee-herdsman (0.14.96) Zigbee2MQTT:error 2023-03-18 08:22:56: Error while starting zigbee-herdsman Zigbee2MQTT:error 2023-03-18 08:22:56: Failed to start zigbee Zigbee2MQTT:error 2023-03-18 08:22:56: Check [Zigbee2MQTT fails to start | Zigbee2MQTT](https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html) for possible solutions Zigbee2MQTT:error 2023-03-18 08:22:56: Exiting… Zigbee2MQTT:error 2023-03-18 08:22:57: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby at ZnpAdapterManager.beginCommissioning (/app/node\_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:347:23) at ZnpAdapterManager.start (/app/node\_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:92:17) at Controller.start (/app/node\_modules/zigbee-herdsman/src/controller/controller.ts:132:29) at Zigbee.start (/app/lib/zigbee.ts:58:27) at Controller.start (/app/lib/controller.ts:101:27) at start (/app/index.js:107:5) Using ‹ /app/data › as data directory Zigbee2MQTT:info 2023-03-18 08:23:06: Logging to console and directory: ‹ /app/data/log/2023-03-18.08-23-06 › filename: log.txt Zigbee2MQTT:info 2023-03-18 08:23:06: Starting Zigbee2MQTT version 1.30.2 (commit #cdf62ea) Zigbee2MQTT:info 2023-03-18 08:23:06: Starting zigbee-herdsman (0.14.96) Log suivant un peu long 2023-03-18T09:17:04+0100 job.purge.js:17 (Job.purge) Deleting all background jobs created before = Sat Mar 11 2023 09:17:04 GMT+0100 (Central European Standard Time) 2023-03-18T09:17:13+0100 index.js:14 (Object.start) starting Alexa service 2023-03-18T09:17:13+0100 index.js:21 (Object.start) Starting example service 2023-03-18T09:17:13+0100 index.js:88 (Object.start) Starting CalDAV service 2023-03-18T09:17:13+0100 index.js:18 (Object.start) Starting TP-Link service 2023-03-18T09:17:13+0100 index.js:16 (Object.start) starting Broadlink service 2023-03-18T09:17:14+0100 index.js:18 (Object.start) Starting HomeKit service 2023-03-18T09:17:14+0100 index.js:14 (Object.start) starting GoogleActions service 2023-03-18T09:17:15+0100 init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0 2023-03-18T09:17:15+0100 checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates… 2023-03-18T09:17:15+0100 installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started 2023-03-18T09:17:15+0100 installZ2mContainer.js:56 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment… 2023-03-18T09:17:15+0100 installZ2mContainer.js:75 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started 2023-03-18T09:17:15+0100 connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker… 2023-03-18T09:17:15+0100 connect.js:24 (MqttClient.) Connected to MQTT container mqtt://localhost:1884 2023-03-18T09:17:15+0100 subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/# 2023-03-18T09:17:15+0100 index.js:20 (Object.start) Starting Open Weather service 2023-03-18T09:17:15+0100 service.start.js:40 (Service.start) Service openweather is not configured, so it was not started. 2023-03-18T09:17:15+0100 index.js:17 (Object.start) Starting eWeLink service 2023-03-18T09:17:15+0100 service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started. 2023-03-18T09:17:15+0100 index.js:15 (Object.start) Starting Bluetooth service 2023-03-18T09:17:16+0100 bluetooth.initPresenceScanner.js:18 (BluetoothManager.initPresenceScanner) Bluetooth configuration: starting presence scanner 2023-03-18T09:17:16+0100 index.js:15 (Object.start) Starting Tasmota service 2023-03-18T09:17:16+0100 index.js:14 (Object.start) Starting Xiaomi service 2023-03-18T09:17:16+0100 index.js:13 (Object.start) Starting usb service 2023-03-18T09:17:16+0100 index.js:19 (Object.start) Starting Telegram service 2023-03-18T09:17:16+0100 service.start.js:40 (Service.start) Service telegram is not configured, so it was not started. 2023-03-18T09:17:16+0100 index.js:16 (Object.start) Starting RTSP service 2023-03-18T09:17:16+0100 index.js:18 (Object.start) Starting Philips Hue service 2023-03-18T09:17:16+0100 index.js:16 (Object.start) Starting MQTT service 2023-03-18T09:17:17+0100 updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes… 2023-03-18T09:17:17+0100 updateContainer.js:41 (MqttHandler.updateContainer) MQTT: no container update required 2023-03-18T09:17:17+0100 connect.js:38 (MqttClient.) Connected to MQTT server mqtt://localhost 2023-03-18T09:17:17+0100 subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic stat/+/+ 2023-03-18T09:17:17+0100 subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic tele/+/+ 2023-03-18T09:17:17+0100 subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic gladys/master/# 2023-03-18T09:17:17+0100 index.js:17 (Object.start) Starting Ecowatt service 2023-03-18T09:17:17+0100 scene.dailyUpdate.js:58 () Sunrise today is at 7:10 today, in your timezone = Europe/Paris 2023-03-18T09:17:17+0100 scene.dailyUpdate.js:59 () Sunset today is at 19:11 today, in your timezone = Europe/Paris 2023-03-18T09:17:17+0100 scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today. 2023-03-18T09:17:17+0100 scene.dailyUpdate.js:81 () Sunset is scheduled, in 10 hours. 2023-03-18T09:17:18+0100 device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval hourly 2023-03-18T09:17:18+0100 index.js:63 (Server.) Server listening on port 80 2023-03-18T09:17:22+0100 device.calculateAggregate.js:105 (ChildProcess.) device.calculateAggregate: Finishing processing for interval hourly 2023-03-18T09:17:22+0100 device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval daily 2023-03-18T09:17:26+0100 device.calculateAggregate.js:105 (ChildProcess.) device.calculateAggregate: Finishing processing for interval daily 2023-03-18T09:17:26+0100 device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval monthly 2023-03-18T09:17:30+0100 device.calculateAggregate.js:105 (ChildProcess.) device.calculateAggregate: Finishing processing for interval monthly 2023-03-18T09:18:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:18:00 GMT 2023-03-18T09:19:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:19:00 GMT 2023-03-18T09:20:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:20:00 GMT 2023-03-18T09:21:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:21:00 GMT 2023-03-18T09:22:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:22:00 GMT 2023-03-18T09:23:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:23:00 GMT 2023-03-18T09:24:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:24:00 GMT 2023-03-18T09:25:00+0100 scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:25:00 GMT 2023-03-18T09:25:55+0100 init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0 2023-03-18T09:25:55+0100 checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates… 2023-03-18T09:25:55+0100 installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started 2023-03-18T09:25:55+0100 installZ2mContainer.js:56 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment… 2023-03-18T09:25:55+0100 installZ2mContainer.js:75 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started 2023-03-18T09:25:55+0100 connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker… 2023-03-18T09:25:55+0100 connect.js:24 (MqttClient.) Connected to MQTT container mqtt://localhost:1884 2023-03-18T09:25:55+0100 subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/# ---
**Author:** ![Jluc](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/jluc/32/12397_2.png) [@Jluc](https://community.gladysassistant.com/u/Jluc)\ **Post date:** [Mars 18, 2023, 9:40 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/6 "2023-03-18T09:40:32Z")
Bonjour @kazuke, J’ai eu aussi beaucoup de difficulté à connecter le dongle modèle P (un second du fait de l’échec permanent) . Au final, - je l’ai relié au hub alimenté avec une rallonge comme un membre de la communauté l’avait suggérer - j’ai connecté directement le SSD sur le hub et, depuis ça fonctionne normalement Bon courage ---
**Author:** ![Will\_71](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/will_71/32/9582_2.png) [@Will\_71](https://community.gladysassistant.com/u/Will_71)\ **Post date:** [Mars 18, 2023, 11:19 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/7 "2023-03-18T11:19:11Z")
Oui c’est ce qu’il faut faire, quand on met un disque externe il faut l’alimenter à travers d’un hub. Dans la doc @pierre-gilles a mit une note d’info sur ce sujet > **[Installation sur un Raspberry Pi | Gladys Assistant](https://gladysassistant.com/fr/docs/installation/raspberry-pi/)** > > Ce tutoriel vous explique comment installer Gladys sur Raspberry Pi ! ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/1/160e737ab2ae6b5d9b52061fd369b8b38e5a511c.png) ---
**Author:** ![kazuke](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kazuke](https://community.gladysassistant.com/u/kazuke)\ **Post date:** [Mars 19, 2023, 11:32 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/8 "2023-03-19T11:32:34Z")
Merci pour tous vos conseils, mais après les avoir suivis scrupulement, toujours le même résultat. j’ai lancé l’instance sur RPI4, des fois que son RPI3 ait quelques bugs, mais pas mieux. J’avais une cle démo de Home Assistant, et là, la clé a été reconnue directement après l’intégration du module sans hub USB sur le RPI3. Je continue les investigations avec votre aide si vous voulez bien. Quelle autre manip à faire ? Merci ---
**Author:** ![kazuke](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kazuke](https://community.gladysassistant.com/u/kazuke)\ **Post date:** [Mars 19, 2023, 8:20 UTC](https://community.gladysassistant.com/t/dongle-zigbee-cc2652p-pas-pris-en-compte-par-gladys-resolu/8026/9 "2023-03-19T20:20:51Z")
La suite… J’ai branché cette cle, après avoir retiré celle d’origine, sur mon instance installée sur la Freebox. Surprise elle est reconnue et fonctionnelle. J’ai donc fait la même install que sur la Freebox : installer raspian64, puis les conteneurs comme décrit dans la doc Gladys et çà fonctionne. Si vous avez une explication. Merci pour votre disponibilté