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

m4v3r1ck · August 31, 2023, 11:26am

Just installed the Python Z-Stack-firmware flashing method for the Coordinator Release (20230507) for the Sonoff ZBDongle-Plus (V1) on my macOS Monterey with this great and easy to follow tutorial made by Dennis van Dalen.

How to update Sonoff Zigbee 3.0 (ZBDongle-P) USB firmware using a Mac

In this tutorial we’ll be flashing the ZBDongle-P with the latest coordinator firmware — Without having to open the case.

❯ python3 cc2538-bsl.py -ewv -p /dev/tty.usbserial-FA420 --bootloader-sonoff-usb ./CC1352P2_CC2652P_launchpad_coordinator_20230507.hex
sonoff
Opening port /dev/tty.usbserial-FA420, baud 500000
Reading data from ./CC1352P2_CC2652P_launchpad_coordinator_20230507.hex
Your firmware looks like an Intel Hex file
Connecting to target...
CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
Primary IEEE Address: xx:xx:xx:xx:xx:xx:xx:xx
    Performing mass erase
Erasing all main bank flash sectors
    Erase done
Writing 360448 bytes starting at address 0x00000000
Write 104 bytes at 0x00057F988
    Write done
Verifying by comparing CRC32 calculations.
    Verified (match: 0xe83aa727)

Home Assistant using ZHA.

1x ZBDongle-P flashed as Coordinator:
firmware CC1352P2_CC2652P_launchpad_coordinator_20230507.hex

5x ZBDongle-P flashed as Routers
firmware CC1352P2_CC2652P_launchpad_router_20221102.hex

Home Assistant 2023.8.4
Supervisor 2023.08.1
Operating System 10.5
Frontend 20230802.1 - latest

HarvinDhillon · September 7, 2023, 9:11am

Just for anyone on ZHA who was curious like me and wants to check the version of firmware on the dongle. Just download the JSON backup and you have it at the bottom.

        "metadata": {
            "zstack": {
                "TransportRev": 2,
                "ProductId": 1,
                "MajorRel": 2,
                "MinorRel": 7,
                "MaintRel": 1,
                "CodeRevision": 20230507,
                "BootloaderBuildType": 0,
                "BootloaderRevision": null
            }
        },

HarvinDhillon · September 14, 2023, 9:33am

Just to update all, after updating the firmware to the latest version, I see far less timeout errors in logs for ZHA, just the occasional. I used to get a lot of 1byte errors, but none so far for a week.

Hedda · September 14, 2023, 10:23am

FYI, some users are having issues with the 20230507 firmware version with new problem symtoms that they did have with the 20221226 firmware version. Koenkk have therefor compiled new test firmware and is asking for updated feedback here → Z-Stack_3.x.0 coordinator 20230901/20230902 feedback · Koenkk/Z-Stack-firmware · Discussion #474 · GitHub

HarvinDhillon · September 15, 2023, 8:53am

Thanks Hedda, I will check it out.

I still have the same battery devices going unavailable but they still do work, they wake up after being pressed. There is one motion sensor though that does not. All routers are up however and stable. I replaced a bunch of Osram bulbs with IKEA bulbs, they were shit routers and the IKEA bulbs improved quite a bit the responsiveness of the network.

Just looking at the logs though, from a ZHA perspective it seems quite clean, just 3 timeouts, I am assuming those were the devices that became unavailable. Basically before my log used to be full of ZHA messages.

Hedda · September 15, 2023, 4:28pm

Regardless of the setup I highly reading and try following all these tips → Guide for Zigbee interference avoidance and network range/coverage optimization

HarvinDhillon · September 15, 2023, 5:22pm

Thanks Hedda, your writeup is indeed my gospel for Zigbee. I have done almost all the items there:-

Moved my zigbee channel to 11 (Wifi channels 1,2,3 are free in my home, all my neighbours are on wifi 11)
USB powered cable to extend the dongle to the middle of the house
Have 2 Sonoff Dongle Plus acting as routers

I am pretty much happy with the setup so far, it is rock solid, I have 140 devices on the network so it is fairly large. 50 of them are routers, the rest end devices.

It is always the same 3 end devices that go offline, might be that they arent binding correctly, 1 is a sonoff contact sensor, 1 ikea switch and 1 aqara motion sensor. I have other same devices in the network but they are rock solid. Funny thing is that even though they are unavailable, they still work if triggered.

sapstar · September 18, 2023, 8:39am

Hi, I have been a smartthings user for 7 years switching to home assistant. New to the community. Can you please let me know if I should buy a sonoff E or P dongle. Also looking for a z-wave dongle as I have a few z-wave devices too. Thanks

mhoogenbosch · September 18, 2023, 9:09am

At this community we assume you are able to use the search function. This thread is specifically for the p version. Advice on what to buy can be found on lots and lots of other threads.

HarvinDhillon · September 18, 2023, 10:17am

TLDR
Both can be used for ZHA, E is never and there pairing issues reported, not so much for P but E is the same chip as Home Assistant is using natively in the yellow and the new skynet connect dongle

Z2MQTT only option is P for stability, E is experimental

But use the search for more detailed info, I have both dongles but havent tested the E (dreading the repairing so leaving it when the wife is out for a while )yet but might move to it soon as I am predominantly ZHA user and would be good to have a native HA dongle.

HarvinDhillon · September 18, 2023, 10:19am

Just a follow on from this comment, I finally rollback to the 221226 release. Even though the 20230507 release seemed snappier in the beginning, but after a few days, everything seemed very slow. I had a bunch of lights not changing state in HA, started to be annoying as I had to press battery buttons multiple times for it to respond as it didnt have the correct state in HA.

221226 has issues too but seemed more stable

Hedda · September 18, 2023, 11:27am

@sapstar While better if you search or start a new thread for more opinions, I would advise that you buy one of each, or even multiple of each, as you can reflash either of those to a dedicated Zigbee Router device by using USB-changer(s) for powering them, and it is highly recommended to have a few “known good” Zigbee Router devices. Read and follow these tips → https://community.home-assistant.io/t/guide-for-zigbee-interference-avoidance-and-network-range-coverage-optimization/515752

As mentioned, if ever going to use Zigbee2MQTT/Z2M then using a ZNP radio like the CC2652 based ZBDongle-P is the only recommended way to go today, (because EZSP radios like the ZBDongle-E support is still missing a couple of key features Zigbee2MQTT/Z2M to be in feature parity with ZNP).

ZBDongle-E can be reflashed to support Thread (for Matter support) or even Multi-PAN RPC for running Zigbee and Thread at the same time, but personally I recommend only using one protocol per dongle, so the best will be to use two separate radio dongles for Zigbee and Thread regardless of radio type used.

If using the ZHA integration then migrating radio type from one type to another type is very easy to migrate and no repair is required if going between ezsp, znp, and deconz radios → https://www.home-assistant.io/integrations/zha#migrating-to-a-new-zigbee-coordinator-adapter-inside-zha

joaopequeno · October 5, 2023, 7:19pm

Hello all,

Since the last update i got my zigbee pen not working:
imagem

The HA can find it since when i reset the integration and remake it again it detectes it and the sensors.
But have no data all the devices are disconected, even the coordinator.

Can anyone help me out?

The log info is:

2023-10-05 00:09:32.848 INFO (MainThread) [zigpy.device] [0x0000] Requesting 'Node Descriptor'
2023-10-05 00:09:32.967 INFO (MainThread) [zigpy.device] [0x0000] Got Node Descriptor: NodeDescriptor(logical_type=<LogicalType.Coordinator: 0>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AlternatePanCoordinator|FullFunctionDevice|MainsPowered|RxOnWhenIdle|AllocateAddress: 143>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfer_size=160, server_mask=11265, maximum_outgoing_transfer_size=160, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=True, *is_coordinator=True, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=False, *is_security_capable=False)
2023-10-05 00:09:32.969 INFO (MainThread) [zigpy.device] [0x0000] Discovering endpoints
2023-10-05 00:09:32.994 INFO (MainThread) [zigpy.device] [0x0000] Discovered endpoints: [2, 1]
2023-10-05 00:09:32.995 INFO (MainThread) [zigpy.device] [0x0000] Initializing endpoints [<Endpoint id=2 in=[] out=[] status=<Status.NEW: 0>>, <Endpoint id=1 in=[] out=[] status=<Status.NEW: 0>>]
2023-10-05 00:09:32.997 INFO (MainThread) [zigpy.endpoint] [0x0000:2] Discovering endpoint information
2023-10-05 00:09:33.026 INFO (MainThread) [zigpy.endpoint] [0x0000:2] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=2, profile=49246, device_type=2080, device_version=0, input_clusters=[0], output_clusters=[])
2023-10-05 00:09:33.027 INFO (MainThread) [zigpy.endpoint] [0x0000:1] Discovering endpoint information
2023-10-05 00:09:33.058 INFO (MainThread) [zigpy.endpoint] [0x0000:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=260, device_type=1024, device_version=0, input_clusters=[0, 6, 10, 25, 1281], output_clusters=[1, 32, 1280, 1282])
2023-10-05 00:09:33.061 INFO (MainThread) [zigpy.device] [0x0000] Already have model and manufacturer info
2023-10-05 00:09:33.061 INFO (MainThread) [zigpy.device] [0x0000] Discovered basic device information for <ZNPCoordinator model='CC1352/CC2652, Z-Stack 3.30+ (build 20210708)' manuf='Texas Instruments' nwk=0x0000 ieee=00:12:4b:00:2a:2e:8a:3f is_initialized=True>
2023-10-05 00:09:33.073 INFO (MainThread) [zigpy_znp.zigbee.application] Permitting joins for 0 seconds
2023-10-05 00:09:37.986 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 0 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.BasicClusterHandler'>
2023-10-05 00:09:37.996 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 0 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.BasicClusterHandler'>
2023-10-05 00:09:37.998 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 6 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.OnOffClusterHandler'>
2023-10-05 00:09:38.001 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 10 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.Time'>
2023-10-05 00:09:38.002 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 25 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.Ota'>
2023-10-05 00:09:38.005 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1281 class: <class 'homeassistant.components.zha.core.cluster_handlers.security.IasAce'>
2023-10-05 00:09:38.015 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 0 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.BasicClusterHandler'>
2023-10-05 00:09:38.016 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 3 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.Identify'>
2023-10-05 00:09:38.017 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.PowerConfigurationClusterHandler'>
2023-10-05 00:09:38.022 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 2 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.DeviceTemperature'>
2023-10-05 00:09:38.023 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 65535 class: <class 'homeassistant.components.zha.core.cluster_handlers.ClusterHandler'>
2023-10-05 00:09:38.100 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 0 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.BasicClusterHandler'>
2023-10-05 00:09:38.102 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.PowerConfigurationClusterHandler'>
2023-10-05 00:09:38.103 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 3 class: <class 'homeassistant.components.zha.core.cluster_handlers.general.Identify'>
2023-10-05 00:09:38.104 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1026 class: <class 'homeassistant.components.zha.core.cluster_handlers.measurement.TemperatureMeasurement'>
2023-10-05 00:09:38.108 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1027 class: <class 'homeassistant.components.zha.core.cluster_handlers.measurement.PressureMeasurement'>
2023-10-05 00:09:38.110 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 1029 class: <class 'homeassistant.components.zha.core.cluster_handlers.measurement.RelativeHumidity'>
2023-10-05 00:09:38.111 INFO (MainThread) [homeassistant.components.zha.core.endpoint] Creating cluster handler for cluster id: 65535 class: <class 'homeassistant.components.zha.core.cluster_handlers.ClusterHandler'>

Logger: homeassistant.helpers.integration_platform
Source: helpers/integration_platform.py:61
First occurred: 21:51:38 (1 occurrences)
Last logged: 21:51:38

Error processing platform zha.repairs
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/integration_platform.py", line 61, in _async_process_single_integration_platform_component
    await integration_platform.process_platform(hass, component_name, platform)
  File "/usr/src/homeassistant/homeassistant/components/repairs/issue_handler.py", line 113, in _register_repairs_platform
    raise HomeAssistantError(f"Invalid repairs platform {platform}")
homeassistant.exceptions.HomeAssistantError: Invalid repairs platform <module 'homeassistant.components.zha.repairs' from '/usr/src/homeassistant/homeassistant/components/zha/repairs.py'>

Thank

pdionisis · October 23, 2023, 6:47pm

Any news for a firmware with more than 5db transmit power and hardware flow control ?

Hedda · October 24, 2023, 9:41am

Those are both old news and discussed much earlier in this thread above. Here is a short summary:

You can configure transmit power via the configuration parameters for the gateway host application (e.i. TX power can changed via the advanced configuration files for the ZHA integration and Zigbee2MQTT). Later firmware images for ZBDongle-P has 9dBm tx power set as default and you can set it to max 20dBm (see https://github.com/zigpy/zigpy-znp/issues/119 and https://github.com/Koenkk/Z-Stack-firmware/issues/323 and )

ZBDongle-P does support hardware flow control, (but the “ZBDongle-E”) does not. For the ZBDongle-P hardware flow control is disabled by default and to enable it you need to remove the enclosure and manually flip theDIP-switch for it (see https://github.com/Koenkk/Z-Stack-firmware/issues/324)

Chris1989 · October 26, 2023, 12:23pm

Good evening,
I finally purchased the ZBDongle-P for optimal compatibility, but I am unable to connect it to Home Assistant. I followed a tutorial video:

However, no matter what I do, I encounter an error with the Zigbee2MQTT addon.

[14:00:48] INFO: Preparing to start...
[14:00:49] INFO: Socat not enabled
[14:00:51] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-10-26 14:00:57: Logging to console and directory: '/config/zigbee2mqtt/log/2023-10-26.14-00-57' filename: log.txt
Zigbee2MQTT:info  2023-10-26 14:00:57: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-10-26 14:00:57: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:error 2023-10-26 14:01:08: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2023-10-26 14:01:08: Failed to start zigbee
Zigbee2MQTT:error 2023-10-26 14:01:08: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2023-10-26 14:01:08: Exiting...
Zigbee2MQTT:error 2023-10-26 14:01:08: undefined

GH2user · October 26, 2023, 12:44pm

Running HAOS 11.0 / HA 2023-10-5 / Supervisor 2023.10.0
I have installed the Mosquitto addon, z2m addon.
I inserted the Sonoff P-dongle and it is visible on the usb-bus as well as ZHA showing up in the 'found integrations" with the dongle. I did do nothing with ZHA further.
When filling out the z2m configuration I get an error on the serial value as follows;

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt: {}
serial: >-
  /dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0

Failed to save add-on configuration, Invalid dict for option ‘serial’ in Zigbee2MQTT (45df7312_zigbee2mqtt). Got {‘data_path’: ‘/config/zigbee2mqtt’, ‘socat’: {‘enabled’: False, ‘master’: ‘pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777’, ‘slave’: ‘tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5’, ‘options’: ‘-d -d’, ‘log’: False}, ‘mqtt’: {}, ‘serial’: ‘/dev/serial/by-id/usb-Silicon_Labs_Sonoff_Zigbee_3.0_USB_Dongle_Plus_0001-if00-port0’}

Which is something in the path of the dongle I suppose.
Has anyone an idea what goes wrong here?

k8gg · October 26, 2023, 4:11pm

When you go to HAOS → Settings → System → Hardware → All Hardware
and then search “by-id”
What do you get?

k8gg · October 26, 2023, 4:15pm

What have you checked / tried? Please help share the results that you saw/got, on each of those checks?

ajohn · October 26, 2023, 6:37pm

Hi, I’ve read through most of this thread. I am using HA with SkyConnect and ZHA as Coordinator. I’ve bought a new Dongle Plus (P). I used a raspberry pi to flash it immediately with router firmware, which went fine thanks to all the information here:

> python cc2538-bsl.py -p /dev/ttyUSB0 -e -v -w --bootloader-sonoff-usb CC1352P2_CC2652P_launchpad_router_20221102.hex
> sonoff
> Opening port /dev/ttyUSB0, baud 500000
> Reading data from CC1352P2_CC2652P_launchpad_router_20221102.hex
> Firmware file: Intel Hex
> Connecting to target...
> CC1350 PG2.0 (7x7mm): 352KB Flash, 20KB SRAM, CCFG.BL_CONFIG at 0x00057FD8
> Primary IEEE Address: 00:12:4B:00:2A:4F:4A:21
>     Performing mass erase
> Erasing all main bank flash sectors
>     Erase done
> Writing 360448 bytes starting at address 0x00000000
> Write 104 bytes at 0x00057F988
>     Write done
> Verifying by comparing CRC32 calculations.
>     Verified (match: 0x9877ee56)

So everthing went fine, but it doesn’t pair to my HA zigbee network. I’m using a usb charger to power it and have tried it at different locations, even 2m from the SkyConnect and still it doesn’t pair. I have opened it and tried pushing the reset button, holding the reset button, but no pairing takes place. I have tried an older router firmware but no difference. I have no clue how to troubleshoot it. Any tips?