ITead's "Sonoff Zigbee 3.0 USB Dongle Plus" (model "ZBDongle-P") based on Texas Instruments CC2652P +20dBm radio SoC/MCU

Open Supervisor → System → Hardware

In my case it is ttyUSB0 -

1 Like

Ahhh, I thought it could be that. Thanks so much.

Not sure what I am doing wrong, hopefully someone here can point out what’s wrong as after 20 minutes on the new coordinator the devices still aren’t connected.
I am coming from a CC2531 running 1.2 firmware and going to the sonoff zibgee stick 3.0, which I have flashed with CC1352P2_CC2652P_launchpad_coordinator_20210708. Z2M is running version 1.22 and there are no errors in the log other than when I try to turn a light off and it times out on receiving a signal. I stopped z2m unplug old coordinator, plug in new coordinator. Put the new serial id in (see below) and start up z2m. I have given up twice now and put in the old coordinator and everything just works still. Any pointers would be appreciated.

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
  base_topic: zigbee2mqtt
  server: mqtt://##########
  user: #####
  password: ##########
  port: >-
  log_level: warn
  pan_id: 6754
  channel: 25
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
  report: false
device_options: {}
blocklist: []
passlist: []
queue: {}
  port: 8099
  new_api: true
  enabled: false
  master: pty,raw,echo=0,link=/dev/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false
  restartdelay: 1
  initialdelay: 1

Did you try to re-pair ?

Thanks for the reply, do you mean re-pair each device or is there some global re-pair?

FYI, Everything Smart Home channel on YouTube posted a guide about ZHA backup and migrations.

He explain why backups are important and shortly how to migrate to ITead’s Sonoff Zigbee 3.0 USB Dongle Plus from another Zigbee dongle/stick/adapter using a hacked Sonoff ZBBridge as an example:

Other than talking to ZHA decs I guess that much of the information comes from these other threads:

PS: Also check out this request/suggestion to add backup features to ZHA’s UI and do nightly backups:

1 Like

I just realised I may have missed a step when flashing the Sonoff stick, did you copy over your original IEEE mac address onto the new stick? It says optional in the Z2M instructions.

1 Like

FYI, Koenkk made a “dev” pre-release of Z-Stack_3.x.0 20211114 community version for this as others:

Note! CC1352P2_CC2652P_launchpad_coordinator_20211114 is a pre-releaser so not fully tested yet!

Z-Stack_3.x.0 20211114 community firmware is based on latest SDK which contains many bug-fixes:

20 dBm output power still not enabled so CC2652P will perform as 5 dBM CC2652R/CC2652RB, see:

Also, FYI, there is no real news on community firmware with Hardware Flow Control enabled, see:

1 Like

I’ve tried Z-Stack_3.x.0 20211114 on this adapter and I had a hard time getting connections to my Zigbee devices. I am on ZHA though, not sure if that makes a difference. I had to fall back to CC1352P2_CC2652P_launchpad_coordinator_20210708. Hopefully someone else can try and perhaps it was just user error.

FYI, there are known issues with connection and joining using Zigbee router devices from some brands.

If possible start by upgrade the firmware on all your Zigbee devices that acts as Zigbee routers (usually mains-powered devices), and when troubleshooting see if Zigbee end-devices (usually battery-powered devices) with connection issues are connected to Zigbee Zigbee router(s) of the same type and brand or the same manufacturer. The issue could be that one or more of your Zigbee router devices is not properly routing all messages that should be routed through it.

Best practices for avoiding pairing difficulties and connection issues

  • If possible try to pair your Zigbee devices in their intended final location, (and not pair it next to the Zigbee coordinator and then need to move it after).
    • Pairing a Zigbee device next to the Zigbee coordinator and then moving it later can result in dropped/lost connections or other issues.
      • If the device you want to add is not brand new and as such never paired before then you always have to make sure to first manually reset the device to its factory default settings before you will be able to add/pair it.
  • Some battery-operated Zigbee devices are known to have problems with pairing if they have Low battery voltage.
    • Some people have reported replacing the battery on their newly received Xiaomi/Aqara devices solved pairing issues.
  • Check that you have enough Zigbee router devices (also known as Zigbee signal repeaters or range extenders) and if you do not have any, invest and add some mains-powered devices that will work as Zigbee routers and make sure that you upgrade the firmware on those devices if possible.
    • Aim to start out with mains-powered devices before adding battery-operated devices as a “weak” Zigbee network mesh (e.g., the device is too far from the Zigbee coordinator or a Zigbee router) may prevent some devices from being paired. Zigbee router devices are also needed to increase the maximum of devices that can be connected to your Zigbee mesh network.
    • Note that some Zigbee devices are not fully compatible with all brands of Zigbee router devices. Xiaomi/Aqara devices are for example known not to work with Zigbee router devices from Centralite, General Electrics, Iris, Ledvance/OSRAM/ LIGHTIFY/Sylvania, Orvibo, PEQ, Securifi, and SmartThings/Samsung. Better results can usually be achieved by using mains-powered devices IKEA and Nue/3A Home or dedicated DIY routing devices based on Texas Instruments CC253x/CC26x2 and XBee Series 2/3 Zigbee radios, (again make sure that try to upgrade to the latest firmware on any and all Zigbee router devices).
  • Be patient as the pairing of some Zigbee devices may require multiple attempts and you may sometimes need to try again and again.
    • Some devices, like example those from Xiaomi/Aqara, are known to not be 100% compliant with the standard Zigbee specifications and may therefore require many paring attempts over 10-20 minutes or longer.
1 Like

Recently I had the opportunity to test the new Zigbee usb dongle from Sonoff ( Two main reasons to do this: a remarkable solid build device at an attractive price based on TI CC2652P + CP2102N chipset.

The usb dongle comes with a good quality usb extension cable. This is no luxury since the dongle is quite ‘fat’ and will block the adjacent usb ports easily. Placing the dongle away from for example a raspberry pi will also reduce any interference.

I have tested the Sonoff Zigbee dongle on a virgin RPI-4 HA installation.

version: core-2021.11.1
installation_type: Home Assistant OS
dev: false
hassio: true
docker: true
user: root
virtualenv: false
python_version: 3.9.7
os_name: Linux
os_version: 5.10.17-v8
arch: aarch64
timezone: UTC

logged_in: false
can_reach_cert_server: ok
can_reach_cloud_auth: ok
can_reach_cloud: ok

host_os: Home Assistant OS 6.6
update_channel: stable
supervisor_version: supervisor-2021.10.8
docker_version: 20.10.8
disk_total: 109.3 GB
disk_used: 2.8 GB
healthy: true
supported: true
board: rpi4-64
supervisor_api: ok
version_api: ok

Now let’s plug it in and see what’s happening:
Ai, I was expecting something else, better ignore. Apparently HA is recognising this as a ZWave device.

Let’s now install ZHA (Zigbee Home Automation) and select the Zigbee radio from the integration:

This feels good:

How powerful is this device? I am going to try pair a couple of zigbee units at 15 m from the dongle and with a few concrete walls and ceilings in between the dongle and the zigbee units.

Two devices on main-power: Muller light switch and a Ikea TRADFRI bulb E27. Both paired immediately.
Of course after having paired one, I disconnected it since these devices also act as a router.
Next was the TRADFRI motion sensor E1745, battery powered. I had to try two times but even the E1745 got paired with no issues. This device was paired with the Muller light and Ikea bulb disconnected.

My first conclusion: a solid device at a competitive price with a good range for home zigbee appliances.


Can you compare LQI values for motion sensor with sonoff and pre-sonoff?

Good idea, will do.

Very well documented review, I still have mine in the drawer though. I got it during the first batch and took just 4days to arrive in the uk after dispatch.

I have mine installed for 2 weeks. Has been rock solid with no issues at this stage.

I have recorded the lqi of two devices separately with the Sonoff dongle:

Screen Shot 2021-11-11 at 21.32.41
Screen Shot 2021-11-11 at 21.30.24

Then I have removed the Sonoff Dongle and replaced it with the old fashioned CC2531… I could not pair the devices at 15 meter distance…

I rest my case

@Doublet , Do you recommend the sonoff 3.0 dongle plus? I am currently using CC2531 but I am having occasional device dropping . I have the sonoff dongle but want to know if it is reliable before I start the tedious pairing.

I had similar issues with the CC2531, especially if you are expanding your network with more than 20 Zigbee devices. The chipset in the Sonoff is lot more powerfull.

I’m still confused by the specification of this device. It states its pre flashed with Z-Stack_3.0.x and supports 20 direct devices up to a maximum of 40 per mesh? However Z2M shows this firmware as Z-Stack_3.x.0 which should support 100-200 devices. Itead/sonoff have failed to answer this question.

states its preflashed with 3.x.0 according to website

and an old post from october on the web mentions it always was using 3.x.0