Should we be switching hardware flow control on? Or do we not care about that?
If so does the latest z2m firmware enable hardware flow control?
Did it work with the original firmware? (the one when the stick was shipped to you)
Yes. Only tried a bulb and sensor. Figured Id start fresh with upgraded firmware.
According to Koenkk his came with C1352P2_CC2652P_launchpad_coordinator_20210120 firmware.
So that should be coordinator/Z-Stack_3.x.0/bin/CC1352P2_CC2652P_launchpad_20210120.zip here:
All of Koenkk’s older firmware that has been uploaded can be found in the commit history on GitHub:
https://github.com/Koenkk/Z-Stack-firmware/commits/master/coordinator/Z-Stack_3.x.0/bin
1 Like
I am using the original firmware - some devices pair but not all. It seems to ignore all my aqara temp sensors.
Has anybody had success creating groups? I’m trying to add 2 hue bulbs to a group via the zigbee2mqtt UI and they just wont show up despite getting the green ‘ok’ dialog after adding.
I understand switching to hardware flow control mode on this ITead Sonoff Zigbee 3.0 USB Dongle Plus adapter is done via the dip-switch on the board, so not by using a different firmware (like more usual).
You then need to enable hardware flow control in the software application like Zigbee2MQTT or ZHA:
https://www.zigbee2mqtt.io/information/configuration.html
# Optional: RTS / CTS Hardware Flow Control for serial port (default: false) rtscts: true
https://www.home-assistant.io/integrations/zha/#configuration—gui
Press
Submitto save radio type and you will get a new form asking for port settings specific for this radio type. In the pop-up:
- Serial device path
- port speed (not applicable for all radios)
- data flow control (set to “software” or “hardware” ´for software/hardware flow control)
Hardware flow control should make for more stable serial communication in theory since flow control is off-loaded from the application and the system CPU to the MCU, but not sure if it will be more stable in the real world. Know I read that openHAB’s Zigbee developer recommended it for commercial use.
1 Like
As noted before, please read + follow these docs tips on best practices for avoiding pairing difficulties:
For unique device-specific pairing tips also check out individual blakadder and Zigbee2MQTT pages:
https://zigbee.blakadder.com/search.html
https://www.zigbee2mqtt.io/information/supported_devices.html
However before that I recommend following my general tips here on improving Zigbee network range:
https://github.com/home-assistant/home-assistant.io/pull/18864
Note that those tips are really generic Zigbee best-practice guidelines so applies to all Zigbee solutions.
1 Like
Did you try the firmware that is linked on the Zigbee2mqtt website? This one:
CC1352P2_CC2652P_launchpad_coordinator_20210708.zip
I’m considering ordering one, but if the firmware is as buggy as mentioned in this review. I’d rather pay a bit more.
Be carefull, the firmware he flashed was the wrong one - and the sonoff sensors he tried to pair are know to have issues with zigbee2mqtt.
Problem is : a lot of CC2625P sticks use the same firmware, including TubeZ, ZigStar, TI LAUNCHXL-CC1352P-2, CircuitSetup.us Zigbee Stick, Egony Stick V4 (RFSTAR ver.), cod.m Zigbee CC2652P RPi Module, cyijun OpenZ3Gateway
and about the review , read his github issue :
Might be confusing since several different versions of firmware but the README.md state which to use:
| Adapter | TI Chip/Module Used | Firmware to Flash | BSL Trigger Pin (1) | Auto-BSL (2) | RF Switch Control Pins (3) | LED(s) |
|---|---|---|---|---|---|---|
| SONOFF Zigbee 3.0 USB Dongle Plus | CC2652P | CC1352P2_CC2652P_launchpad_*.zip | ? | No | ? | N/A |
https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_3.x.0/bin
Koenkk have now even specifically added “SONOFF Zigbee 3.0 USB Dongle Plus” to README.md
Tried to install my Sonoff dongle
I had just the same problem this evening using Zigbee2mqtt.
Always error could not open serialport
/dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0edf89633693eb118b6b214f3d98b6d1-if00-port0
Then I tried simply /dev/ttyUSB0 and Zigbee2mqtt started ?
Is the description too long ?
Running good here with /dev/serial/by-id/
Maybe a “supervisor” issue?
Install on bare metal on Raspbian Bullseye on a Pi1. No Home Assistant on that Pi.
Bare metal here, no issues. 
Firmware must support hardware flow control. Currently, we don’t have that.
Section 2 explains
https://sonoff.tech/wp-content/uploads/2021/09/Zigbee-3.0-USB-dongle-plus-firmware-flashing-1-1.docx
Is this issue affecting only zigbee2mqtt and can someone explain what flow control is and it’s use?
I just ordered the stick and now I’m wondering if that was a bad idea lol. I only use zha.
This is one of the best zigbee coordinators that I’ve used. Stable and good LQI’s
As far as flow control, zha and z2m has always used software vs hardware AFAIK. SZD 3.0+ is the only coordinator that I’ve seen with a switchable option. As for a bad idea purchasing, I don’t think so.
Read this post ITead Sonoff Zigbee 3.0 USB Dongle Plus adapter based on Texas Instruments CC2652P - #61 by Hedda
My network (80 devices)
1 Like
Did you flash it with a specific firmware or the one that came with the stick? i have this stick sitting in my drawer based on a review i saw on YouTube .
I flashed it with the new CC1352P2_CC2652P_launchpad_coordinator_20210708 firmware.
It came with CC1352P2_CC2652P_launchpad_20210120 firmware, and worked.