Issues with Zigbee2MQTT setup

[Mauriced]

Hi,

I don't know if this is the right location for my issue, but I don't really know what to try next.

I have a zigbee USB stick/dongel and think that is related to missing FTDI drivers in Linux, but on how to do that is hard to find... The drivers are included in Ubuntu 21.10 in the extra kernel modules, but that release has the python 3.9 which Domoticz cannot handle. Debian 10 has Python 3.7, but is missing the FTDI_SIO driver/module(all standard server installs with the raspberry pi imager). I tried the MQTT Autodiscover first, but the add hardware page gives the same information as the MQTT client gateway hardware (and misses the autodiscover prefix), which I think could be related to the Python 3.9 issues?

In short my question is: has anyone made it work, did anyone have the same issues and how did you get it to work?

Regards,
Maurice

[HansOtten]

On what hardware? Since you talk about Raspberry Pi Imager may I assume a Raspberry.

It works fine on Raspberry PI OS Buster Lite (long term support version now) with the Electrolama zig-a-zig-ah! (zzh!) CC2652R stick .
I have also good results with (non-zigbee) FTDI based RS232 dongles on Raspberry PI OS working out of the box.

Any special reason to use these other OS'es? Lite is fine for me as server OS. Stable (Buster!) made for the Raspberry Pi hardware and has all I and Zigbee2MQTT and MQTT and Domoticz need.

[Mauriced]

Yes, my apologies. It is on a Raspberry pi 3b+ if I remembered correctly (I do not have it nearby a.t.m.).
And I tried Raspbian 10 (which is Debian, but with raspberry customizations), the reason I started with Ubuntu is that it has build-in automatic update capability.

I tried several OS's and versions, but it seems like the only working OS with the Zigbee stick is Ubuntu 21.10 with the extra kernel modules. Otherwise there are no ttyUSB* or ttyACM*devices created (also not with the udev rules). I will try to get the information about the specific Zigbee stick and firmware, because I have not ordered and flashed it myself.

The data I got when I plugged it into another Raspbian installation was:

Code: Select all

Jan 20 22:30:21  kernel: [688900.396019] usb 1-1.2: new full-speed USB device number 5 using dwc_otg
Jan 20 22:30:21  kernel: [688900.543983] usb 1-1.2: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
Jan 20 22:30:21  kernel: [688900.544008] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 20 22:30:21  kernel: [688900.544022] usb 1-1.2: Product: TI CC2531 USB CDC
Jan 20 22:30:21  kernel: [688900.544034] usb 1-1.2: Manufacturer: Texas Instruments
Jan 20 22:30:21  kernel: [688900.544046] usb 1-1.2: SerialNumber: __0X00124B0018E27405

[HansOtten]

The TI CC2531 USB stick is working fine in Zigbee2MQTT for many . Not the best solution nowadays it seems (range, limitations) but cheap, and if it works it works.
What is Raspbian 10 ? On Raspberry Pi OS, use Buster Lite, that is the name and version that works fine with Domotzicz.

Did you perform the firmware (ccordinator) flashing of the stick (see https://www.zigbee2mqtt.io/guide/adapte ... c2531.html)
before inserting the stick? Otherwise Zigbee2MQTT will not see it of course.

I have the impression you are into an OS and Python version war, instead of getting the low level working: flash the stick with the right firmware!

[Mauriced]

Raspbian is the previous name of Raspberry Pi OS, 10 stands for the release version with codename Buster.

Like I said, I did not order and flash the stick. I got it from a friend who had successfully flashed and tested the device before handed it to me. And the weird part is that with Ubuntu 21.10 with the extra kernel modules I can see the device and I can pair devices in Zigbee2MQTT, but because that version has python 3.9 Domoticz crashes with every plugin I try, like described in one of the issues on github.

[EddyG]

On a test system Raspberry Pi 4B I have running: Linux raspberryubuntu 5.4.0-1047-raspi #52-Ubuntu SMP PREEMPT Wed Nov 24 08:16:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
When I insert the CC2531 USB stick I get:

Code: Select all

[21612.614194] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd
[21612.728694] usb 1-1.1: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[21612.728710] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21612.728722] usb 1-1.1: Product: CC2531 USB CDC
[21612.728733] usb 1-1.1: Manufacturer: Texas Instruments
[21612.728743] usb 1-1.1: SerialNumber: 001
[21612.732170] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device

and the cdc_acm module is loaded. Could you manual insmod that module?

[Mauriced]

On a test system Raspberry Pi 4B I have running: Linux raspberryubuntu 5.4.0-1047-raspi #52-Ubuntu SMP PREEMPT Wed Nov 24 08:16:38 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
When I insert the CC2531 USB stick I get:

Code: Select all

[21612.614194] usb 1-1.1: new full-speed USB device number 6 using xhci_hcd
[21612.728694] usb 1-1.1: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09
[21612.728710] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[21612.728722] usb 1-1.1: Product: CC2531 USB CDC
[21612.728733] usb 1-1.1: Manufacturer: Texas Instruments
[21612.728743] usb 1-1.1: SerialNumber: 001
[21612.732170] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device

and the cdc_acm module is loaded. Could you manual insmod that module?

Thank you very much for sharing your working environment, it had send me back on the sort of right track
Unfortunately the insmod does not recognize the specific modules, the files simply are not there...

I will share my experience further with the more troubleshooting I will do, but it is indeed working on a Raspberry Pi 4 (8GB) with Ubuntu 20.04LTS 64bit installed on a 16GB micro SD card. The last one is I think the most important one. All my previous tries are with an external USB SSD drive and I think the boot partition I used for booting to the USB SSD is the culprit of my FTDI curse. After copying the current boot partition from the SSD (which is apparently used by the updater in the OS, but not for booting) the boot sequence to the SSD breaks, so no successful test there.

With the Raspberry Pi 4 I have installed the latest Beta release from Domoticz and Zigbee2MQTT python plugin, this because the Autodiscover MQTT in the beta still does nothing and gives me no autodiscover prefix.

[EddyG]

I used this image: https://ubuntu.com/download/raspberry-p ... rm64+raspi
It is a Raspberry Pi 20.04.3 LTS image (5.4.0-1047-raspi)

[Mauriced]

Ok, my next experience is as follows on a raspberry pi 4 with Ubuntu 20.04 LTS:

When I run domoticz with the zigbee stick on a SD card and connect a USB 2.0 external HDD/SSD no problems, when I boot from the external USB 2.0 drive only network leave messaged are being received/processed in zigbee2mqtt.

When I run domoticz with the zigbee stick on a SD card and connect a USB 3.0 external HDD/SSD and when I boot from the external USB 3.0 drive only network leave messaged are being received/processed in zigbee2mqtt.

For some reason with the latest beta I got the autodiscover prefix in the MQTT autodiscover plugin, but still not got it to work.

[waltervl]

Please also clear your browser cache (mostly CTRL-F5 will do the trick). That MQTT AutoDiscover field is not shown as in the wiki https://www.domoticz.com/wiki/MQTT#Add_ ... Gateway.22 is probably related to caching issue.
And also update to the latest Domoticz beta version.

I have a Zigate V1 and have no issues running this on an Ubunto 20.04LTS so do not know where you connection issues are coming from.
Else try the Zigate Forum on https://zigate.fr/forum/ (scroll down....)