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

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?

ajohn · October 26, 2023, 7:04pm

Never mind, I finally got it to pair. I pressed the reset button multiple times (I think 5 times) while it was at 2 meters from the SkyConnect. Shortly after that it was detected by Home Assistant. This wasn’t a smooth experience at all, hopefully it will work well as a router.

GH2user · October 26, 2023, 7:36pm

Indeed that matched. Just found out I had to put “port:” before it.
Now back to getting my HUE lights transferred from the bridge.

Chris1989 · October 26, 2023, 8:11pm

My zigbee is conected here:

ttyACM0
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158-if00
Subsystem:
tty
Device path:
/dev/ttyACM0
ID:
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158-if00
Attributes:
DEVLINKS: >-
  /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158-if00
  /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
DEVNAME: /dev/ttyACM0
DEVPATH: >-
  /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/tty/ttyACM0
ID_BUS: usb
ID_MM_CANDIDATE: '1'
ID_MODEL: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
ID_MODEL_ENC: SONOFF\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus\x20V2
ID_MODEL_ID: 55d4
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.1:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_1_1_0
ID_REVISION: '0442'
ID_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158
ID_SERIAL_SHORT: '20230324194158'
ID_TYPE: generic
ID_USB_CLASS_FROM_DATABASE: Communications
ID_USB_DRIVER: cdc_acm
ID_USB_INTERFACES: ':020201:0a0000:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
ID_USB_MODEL_ENC: SONOFF\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus\x20V2
ID_USB_MODEL_ID: 55d4
ID_USB_REVISION: '0442'
ID_USB_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158
ID_USB_SERIAL_SHORT: '20230324194158'
ID_USB_TYPE: generic
ID_USB_VENDOR: ITEAD
ID_USB_VENDOR_ENC: ITEAD
ID_USB_VENDOR_ID: 1a86
ID_VENDOR: ITEAD
ID_VENDOR_ENC: ITEAD
ID_VENDOR_FROM_DATABASE: QinHeng Electronics
ID_VENDOR_ID: 1a86
MAJOR: '166'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '13462801'

also
the configuration:

Zigbee2MQTT
Options
 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:
  base_topic: zigbee2mqtt
  user: mqtt-user
  password: xxxx
  server: mqtt://192.168.1.15:1883
serial:
  port: /dev/ttyACM0

also the log doesnt say anything only that:

info  2023-10-26 23:03:56: Logging to console and directory: '/config/zigbee2mqtt/log/2023-10-26.23-03-56' filename: log.txt
info  2023-10-26 23:03:56: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
info  2023-10-26 23:03:56: Starting zigbee-herdsman (0.19.0)
error 2023-10-26 23:04:06: Error while starting zigbee-herdsman
error 2023-10-26 23:04:06: Failed to start zigbee
error 2023-10-26 23:04:06: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
error 2023-10-26 23:04:06: Exiting...
error 2023-10-26 23:04:06: undefined

The link has some general aproach of fixes …

jerrm · October 26, 2023, 9:04pm

Thant’s not a Dongle-P. It is a Dongle-E.

You need:

serial:
  port: /dev/ttyACM0
  adapter: ezsp

But I would use:

serial:
  port: /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158-if00
  adapter: ezsp

Chris1989 · October 26, 2023, 9:33pm

@jerrm
You’re right! However, I supposedly bought the “p” so now I have to deal with it, that’s why I have connectivity issues…
Anyway, it now gives me an error, and after searching I found out that I need to completely uninstall ZHA. I did, but it’s still the same. Also, I have the Mosquitto broker enabled; should it be active?

[00:27:33] INFO: Preparing to start...
[00:27:34] INFO: Socat not enabled
[00:27:36] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-10-27 00:27:42: Logging to console and directory: '/config/zigbee2mqtt/log/2023-10-27.00-27-42' filename: log.txt
Zigbee2MQTT:info  2023-10-27 00:27:42: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-10-27 00:27:42: Starting zigbee-herdsman (0.19.0)
Error: Reset error: Error: {"sequence":-1} after 10000ms
    at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:299:23
    at Queue.executeNext (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:32:32)

setup

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

server: mqtt://core-mosquitto:1883
user: mqtt-user
password: xxxx

serial
port: >-
  /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230324194158-if00
adapter: ezsp

Chris1989 · October 26, 2023, 10:04pm

Update made restart and now get that errror:

[01:03:17] INFO: Preparing to start...
[01:03:18] INFO: Socat not enabled
[01:03:20] INFO: Starting Zigbee2MQTT...
Zigbee2MQTT:info  2023-10-27 01:03:27: Logging to console and directory: '/config/zigbee2mqtt/log/2023-10-27.01-03-27' filename: log.txt
Zigbee2MQTT:info  2023-10-27 01:03:27: Starting Zigbee2MQTT version 1.33.1 (commit #unknown)
Zigbee2MQTT:info  2023-10-27 01:03:27: Starting zigbee-herdsman (0.19.0)
Zigbee2MQTT:info  2023-10-27 01:03:33: zigbee-herdsman started (resumed)
Zigbee2MQTT:info  2023-10-27 01:03:33: Coordinator firmware version: '{"meta":{"maintrel":"3 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.3.0 build 297"},"type":"EZSP v8"}'
Zigbee2MQTT:info  2023-10-27 01:03:33: Currently 0 devices are joined:
Zigbee2MQTT:info  2023-10-27 01:03:33: Zigbee: disabling joining new devices.
Zigbee2MQTT:info  2023-10-27 01:03:33: Connecting to MQTT server at mqtt://192.168.1.15:1883
Zigbee2MQTT:error 2023-10-27 01:03:33: MQTT error: Connection refused: Not authorized
Zigbee2MQTT:error 2023-10-27 01:03:33: MQTT failed to connect, exiting...
Zigbee2MQTT:info  2023-10-27 01:03:33: Stopping zigbee-herdsman...

Chris1989 · October 26, 2023, 10:07pm

Finally! Workerd, for those has same problem :
mqtt:
base_topic: zigbee2mqtt
user: mqtt-user
pass: mqtt-pass
server: mqtt://core-mosquitto:1883

And changed it to

mqtt:
base_topic: zigbee2mqtt
user: “mqtt-user”
password: “mqtt-pass”
server: mqtt://core-mosquitto:1883

that worked for me.

Hedda · October 27, 2023, 9:03am

@Chris1989 @GH2user @k8gg Guys, please do not start troubleshooting individual connection issues in this thread, such discussions should be posted in separate thread and not spam this thread.

If you guys are going to use Zigbee2MQTT then make sure you have not installed or disabled the Zigbee Home Automation (ZHA) integration, or at least make sure that the ZHA integration is not connected to the ZBDongle-P serial device. ZBDongle-P is a serial device so the Zigbee gateway application connected to it (e.i. Zigbee2MQTT or the ZHA integration) needs exclusive access to it, meaning that you can not have two applications connected to the same serial device

Other than that, you could check that CP210x USB to UART Bridge VCP Drivers for CP2102/CP2102N have been installed correctly and that the operating system can actually see it as a serial device

Otherwise, the only general advice we can give here if the operating system is not seeing it is to note that you need to make sure that you are connecting it via USB extension cable, because the physical USB male plug on this adapter is extremely short, so depending on your computer enclosure/chassis this adapter might not make a proper physical USB connection, so using a USB extension cable which has a longer physical USB male plug and better USB female port will sort out that specific problem.

Regardless, believe it or not, your question about getting this ZBDongle-P to be seen by the Zigbee gateway application does otherwise not really belong in this general thread about the ZBDongle-P and you should instead post that to a new thread with your specific question where you first need to better describe your exact individual setup and installation environment (both hardware, OS and software).

The reason for that is that this is really just a thread about ZBDongle-P hardware and firmware, so do not want to spam this thread with long back and forth about individual USB-passthrough configuration as that answer will need be very specific depending on your unique setup and installation environment.

As noted by @Chris1989 posts, that should been posted to Zigbee2MQTT discussions instead as such issues are more than likely application configuration → Koenkk/zigbee2mqtt · Discussions · GitHub

In conclusion, better if you guys create your own new threads that is only for you and only for one issue.

If using Zigbee2MQTT then create new post to https://github.com/Koenkk/zigbee2mqtt/discussions/ and if using the ZHA then create new post here → https://community.home-assistant.io/c/configuration/zigbee/39

GH2user · October 28, 2023, 11:20am

@Hedda Sorry for that, blame it on the title of the topic which seems to be a general discussion on this type of dongle which will attract all kind of problems. Thanks anyhow for the general tips, will try to do better in the future.