Zigbee cc2652P dongle not recognized by Gladys [Resolved]

Hello,

After a fresh install, an issue connecting a Zigbee dongle: « ZBDongle Zigbee 3.0 USB Dongle Plus »
purchase link : SONOFF ZigBee 3.0 USB Dongle Plus, TI CC2652P Coordinator, Universelle USB ZigBee Hub, Passerelle ZigBee pour Home Assistant : Amazon.fr: Informatique
Is the CC2652P chip compatible?
In the Zigbee2MQTT service configuration a red cross after MQTT
the results in the 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

Should I return this dongle?

Thanks for your replies
Edit: Gladys 32-bit image on Raspberry Pi 3 B+

Hi!
When you go to the service configuration

Good evening GBoulvin.
I already have a Gladys instance running on the Freebox. No problems so far.
For the new installation, it’s for a friend.
Yes, regarding your questions.
I’ll get back to you about the logs tomorrow; I’m not at home this evening.
Thanks

The new instance is on a Raspberry Pi 3, and I see there is an external USB drive.
Do you have a powered USB hub with the external hard drive?

Hello Will
No, not a powered hub. I thought it unnecessary for an SSD. I will try with a hub.
As requested by 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 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)

The following log is a bit long
2023-03-18T09:17:04+0100 \u003cinfo\u003e 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 \u003cinfo\u003e index.js:14 (Object.start) starting Alexa service
2023-03-18T09:17:13+0100 \u003cinfo\u003e index.js:21 (Object.start) Starting example service
2023-03-18T09:17:13+0100 \u003cinfo\u003e index.js:88 (Object.start) Starting CalDAV service
2023-03-18T09:17:13+0100 \u003cinfo\u003e index.js:18 (Object.start) Starting TP-Link service
2023-03-18T09:17:13+0100 \u003cinfo\u003e index.js:16 (Object.start) starting Broadlink service
2023-03-18T09:17:14+0100 \u003cinfo\u003e index.js:18 (Object.start) Starting HomeKit service
2023-03-18T09:17:14+0100 \u003cinfo\u003e index.js:14 (Object.start) starting GoogleActions service
2023-03-18T09:17:15+0100 \u003cinfo\u003e init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2023-03-18T09:17:15+0100 \u003cinfo\u003e checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates…
2023-03-18T09:17:15+0100 \u003cinfo\u003e installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2023-03-18T09:17:15+0100 \u003cinfo\u003e installZ2mContainer.js:56 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment…
2023-03-18T09:17:15+0100 \u003cinfo\u003e installZ2mContainer.js:75 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2023-03-18T09:17:15+0100 \u003cinfo\u003e connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker…
2023-03-18T09:17:15+0100 \u003cinfo\u003e connect.js:24 (MqttClient.\u003canonymous\u003e) Connected to MQTT container mqtt://localhost:1884
2023-03-18T09:17:15+0100 \u003cinfo\u003e subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2023-03-18T09:17:15+0100 \u003cinfo\u003e index.js:20 (Object.start) Starting Open Weather service
2023-03-18T09:17:15+0100 \u003cinfo\u003e service.start.js:40 (Service.start) Service openweather is not configured, so it was not started.
2023-03-18T09:17:15+0100 \u003cinfo\u003e index.js:17 (Object.start) Starting eWeLink service
2023-03-18T09:17:15+0100 \u003cinfo\u003e service.start.js:40 (Service.start) Service ewelink is not configured, so it was not started.
2023-03-18T09:17:15+0100 \u003cinfo\u003e index.js:15 (Object.start) Starting Bluetooth service
2023-03-18T09:17:16+0100 \u003cinfo\u003e bluetooth.initPresenceScanner.js:18 (BluetoothManager.initPresenceScanner) Bluetooth configuration: starting presence scanner
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:15 (Object.start) Starting Tasmota service
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:14 (Object.start) Starting Xiaomi service
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:13 (Object.start) Starting usb service
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:19 (Object.start) Starting Telegram service
2023-03-18T09:17:16+0100 \u003cinfo\u003e service.start.js:40 (Service.start) Service telegram is not configured, so it was not started.
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:16 (Object.start) Starting RTSP service
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:18 (Object.start) Starting Philips Hue service
2023-03-18T09:17:16+0100 \u003cinfo\u003e index.js:16 (Object.start) Starting MQTT service
2023-03-18T09:17:17+0100 \u003cinfo\u003e updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes…
2023-03-18T09:17:17+0100 \u003cinfo\u003e updateContainer.js:41 (MqttHandler.updateContainer) MQTT: no container update required
2023-03-18T09:17:17+0100 \u003cinfo\u003e connect.js:38 (MqttClient.\u003canonymous\u003e) Connected to MQTT server mqtt://localhost
2023-03-18T09:17:17+0100 \u003cinfo\u003e subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic stat/+/+
2023-03-18T09:17:17+0100 \u003cinfo\u003e subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic tele/+/+
2023-03-18T09:17:17+0100 \u003cinfo\u003e subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic gladys/master/#
2023-03-18T09:17:17+0100 \u003cinfo\u003e index.js:17 (Object.start) Starting Ecowatt service
2023-03-18T09:17:17+0100 \u003cinfo\u003e scene.dailyUpdate.js:58 () Sunrise today is at 7:10 today, in your timezone = Europe/Paris
2023-03-18T09:17:17+0100 \u003cinfo\u003e scene.dailyUpdate.js:59 () Sunset today is at 19:11 today, in your timezone = Europe/Paris
2023-03-18T09:17:17+0100 \u003cinfo\u003e scene.dailyUpdate.js:70 () The sun rose this morning. Not scheduling for today.
2023-03-18T09:17:17+0100 \u003cinfo\u003e scene.dailyUpdate.js:81 () Sunset is scheduled, in 10 hours.
2023-03-18T09:17:18+0100 \u003cinfo\u003e device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval hourly
2023-03-18T09:17:18+0100 \u003cinfo\u003e index.js:63 (Server.\u003canonymous\u003e) Server listening on port 80
2023-03-18T09:17:22+0100 \u003cinfo\u003e device.calculateAggregate.js:105 (ChildProcess.\u003canonymous\u003e) device.calculateAggregate: Finishing processing for interval hourly
2023-03-18T09:17:22+0100 \u003cinfo\u003e device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval daily
2023-03-18T09:17:26+0100 \u003cinfo\u003e device.calculateAggregate.js:105 (ChildProcess.\u003canonymous\u003e) device.calculateAggregate: Finishing processing for interval daily
2023-03-18T09:17:26+0100 \u003cinfo\u003e device.calculateAggregate.js:38 (DeviceManager.calculateAggregate) Calculating aggregates device feature state for interval monthly
2023-03-18T09:17:30+0100 \u003cinfo\u003e device.calculateAggregate.js:105 (ChildProcess.\u003canonymous\u003e) device.calculateAggregate: Finishing processing for interval monthly
2023-03-18T09:18:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:18:00 GMT
2023-03-18T09:19:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:19:00 GMT
2023-03-18T09:20:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:20:00 GMT
2023-03-18T09:21:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:21:00 GMT
2023-03-18T09:22:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:22:00 GMT
2023-03-18T09:23:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:23:00 GMT
2023-03-18T09:24:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:24:00 GMT
2023-03-18T09:25:00+0100 \u003cinfo\u003e scene.checkCalendarTriggers.js:24 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Sat, 18 Mar 2023 08:25:00 GMT
2023-03-18T09:25:55+0100 \u003cinfo\u003e init.js:38 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2023-03-18T09:25:55+0100 \u003cinfo\u003e checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates…
2023-03-18T09:25:55+0100 \u003cinfo\u003e installMqttContainer.js:104 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2023-03-18T09:25:55+0100 \u003cinfo\u003e installZ2mContainer.js:56 (Zigbee2mqttManager.installZ2mContainer) Preparing Zigbee2mqtt environment…
2023-03-18T09:25:55+0100 \u003cinfo\u003e installZ2mContainer.js:75 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2023-03-18T09:25:55+0100 \u003cinfo\u003e connect.js:14 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker…
2023-03-18T09:25:55+0100 \u003cinfo\u003e connect.js:24 (MqttClient.\u003canonymous\u003e) Connected to MQTT container mqtt://localhost:1884
2023-03-18T09:25:55+0100 \u003cinfo\u003e subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#

Hello @kazuke,
I also had a lot of difficulty connecting the model P dongle (a second one because of the permanent failure). In the end,

  • I connected it to the powered hub with an extension cable as a member of the community had suggested
  • I connected the SSD directly to the hub and,
    since then it has been working normally
    Good luck

Yes, that’s what you should do, when you connect an external drive you need to power it through a hub.

In the docs @pierre-gilles added an informational note on this topic

Thank you for all your advice, but after following it scrupulously, I still get the same result.
I launched the instance on the RPI4, in case its RPI3 had some bugs, but no better.
I had a Home Assistant demo key, and there the key was recognized immediately after integrating the module without a USB hub on the RPI3.
I’ll continue the investigations with your help if you don’t mind. What else should I try?
Thank you

The rest…
I plugged this key, after removing the original one, into my instance installed on the Freebox.
Surprisingly it is recognized and functional.
So I did the same install as on the Freebox: install raspbian64, then the containers as described in the Gladys docs and it works.
If you have an explanation.

Thank you for your availability