Sonoff Dongle P not found

Configuration Zigbee
1

I have a Sonoff Zigbee Dongle P (TI CC2652P).

I understand it should be plugged into a USB 2.0 port and not USB 3.0 to avoid EMI intereference.

No Zigbee devices have yet been paired to the Dongle.

On my Rasp Pi 5 it is auto discovered and installed fine on the USB 3.0 port, but not when connected to the USB 2.0 port, it cannot be found.

I note this path on the Serial Port configuration setting when connected to USB 3.0 port (X’s added here to anonamise):

/dev/serial/by-id/usb ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_XXXXXXXXXXXXXXXXXXXXXXX-port0

I have tried entering the above into the device path configuration setting when trying to configure the dongle when plugged into the USB 2.0 port, but still no joy.

According to this:

The Dongle is compatible and should be auto discovered, which it is when plugged into the USB 3.0 port, but not USB 2.0 port.

This pertinent section:

Press Submit to 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 (not applicable for all radios)*

Most devices need at the very least the serial device path, like /dev/ttyUSB0, but it is recommended to use device path from /dev/serial/by-id folder, e.g., /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F003D3-if01-port0 A list of available device paths can be found in Settings > System > Hardware > dot menu > All Hardware.

When plugged into USB 3.0 the hardware settings display the unit as recognised:

ttyUSB0
/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_XXXXXXXXXXXXXXX-port0

but when plugged into USB 2.0, hardware setting display for ‘ttyUSB0’ disappears’, and device path in configuration displays: /dev/ttyAMA10

I have just bought the dongle - so cant see that the firmware would need an update, but can do that if required.

Any help appreciated.

2

And where is the problem, why not use usb 3.0 when it appears in auto discovery? Or you can try using a usb extension cable and use a dongle over cable if you are worried about signal jitter.

3

It is a well known problem that USB3 ports generate interference around 2.4GHz and it is not recommend they be used as they can interfere with zigbee packet reception. See: Zigbee network optimization: a how-to guide for avoiding radio frequency interference + adding Zigbee Router devices (repeaters/extenders) to get a stable Zigbee network mesh with best possible range and coverage by fully utilizing Zigbee mesh networking

4

If you have access to the console (or maybe your ssh will work), plug the stick into the USB2.0 port and at the console, type dmesg and see what is shows at the end.
BTW, most tty’s I’ve seen with AMA in their name are Raspi on-board serial uarts.

5

Thank you or reading my long post ! was struggling.

Dongle plugged back into other USB 2.0 on the RaspPi 5, keyboard into 1st USB 2.0

It was recognised straight away, random, tried to add it again, but got back:

‘Already configured. Only a single configuration possible.’

It has had a number of restarts since last try with the USB 2.0 Port.

Regarding your advice to run ‘dmesg’:

Presume I need to login at the console to run this, I read only developers should be doing this ??
I can install the SSH add on, but that I understand that only gives limited access to system files within the container (I understand HAOS runs inside a container).

At the console prompt:
ha > dmesg
Error: unknown
ha > sudo dmesg
Error: unknown command “sudo” for “ha”

ha > [ 806.3699771 ] cp210x cp210x ttyUSB0: failed to set request 0x12: -110

6

at the “ha >” prompt, type login and see if you now get a “#” prompt. If you do, then try the dmesg.

7

Thanks, I will check tonight when I am in front of the console and report back.

8

Yes typing ‘Login’ brought me ‘#’, I entered ‘dmesg’ which resulted in a long scrolling display, unsure how to decipher the results, or capture them.

I noticed prior to this a message that had been generated during the day sitting by a prompt:

ha > ++++++++[ 6519.5195631 cp210x ttyUSB0: failed set request 0x12 status: -110
[ 8629.473119] cp210x ttyUSB0 failed set request 0x12 status: -110

Error: unknown command “++++++++” for “ha”

Run ‘ha --help’ for usage.
FATA[0000] Error while executing rootCmd: unknown command “++++++++” for “ha”

9

This is likely the problem, but after googling around some, couldn’t find what the actual problem is.
Some were using a USB hub, and when they removed it, the problem was fixed, but like I said, no real problem identified that I could find.

FYI, To make it easier using dmesg, unplug the stick, wait a few seconds, then plug it back in, then use dmesg and at the end of the dmesg output should show the events that occurred when you plugged the stick back into the USB2.0 port

10

OK when I unplugged the dongle the console displayed this at the prompt:

[162770,775517] cp210x ttyUSB0: failed to set request 0x7 status -19

[162770,775727] cp210x ttyUSB0: failed to set request 0x12 status -19
[162770,775908] cp210x ttyUSB0: failed to set request 0x0 status -19

When I plugged it back in and ran dmesg, this was the bottom of the display:

[162964.408857] usb 1-2: USB disconnect, device number 4
[162964,xxxxxx] cp210x ttyUSB0: failed to set request 0x7 status -19
[162964,xxxxxx] cp210x ttyUSB0: failed to set request 0x12 status -19
[162964,xxxxxx] cp210x ttyUSB0: failed to set request 0x0 status -19
[162964,xxxxxx] cp210x ttyUSB0: cp210x now disconnected from ttyUSB0
[162964,xxxxxx] cp210x 1-2:1.0: device disconnected
[162964,xxxxxx] USB 1-2: new full speed USB device number 5 using xhci-hcd
[162964,xxxxxx] USB 1-2: New USB device found, idVendor=10c4, idProduct=ca60,bcdDevice= 1.00
[162964,xxxxxx] USB 1-2:New USB device strings: Mfr=1, Product=2, SerialNumber=3
[162964,xxxxxx] USB 1-2:Product: Sonoff Aigbee 3.0 USB Dongle Plus
[162964,xxxxxx] USB 1-2:: Manufacturer: ITead
[162964,xxxxxx] USB 1-2: SerialNumber: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[162964,xxxxxx] USB 1-2: cp210x 1-2:1.0 cp210x converter detected to ttyUSB0
[162964,xxxxxx] USB 1-2: usb 1-2: cp210x converter now attached

11

When it was plugged back in, the logs show that things are fine.
There should be a /dev/ttyUSB0 file present with the stick plugged in like this.