Zigbee2MQTT with CC2652BLE SimpleLink dongle - It works!

Configuration
41

I returned the Aqara E1 Door & Window Sensor (MCCGQ14LM) sensors.
I bought Sonoff SNZB-04 sensors compatible with Zigbee2MQTT which arrived today.

I put Gladys in Association mode, I pressed the button for 5s with a small object (the LED flashed 3 times) but the sensor did not appear in the Gladys interface.
I opened the Zigbee2MQTT interface on port 8080, I activated pairing and the sensor was discovered immediately. It then appeared in Gladys.
Moreover, when I activate the association in Gladys, it does not activate it in the Zigbee2MQTT 8080 interface, but the opposite works.
Any ideas to solve the problem?
Thanks in advance

Today (22/01/2022) I dive back into Zigbee2MQTT:

  • when I activate or deactivate the association in Gladys, it does the same thing in the Zigbee2MQTT interface
 Cool!
  • when I activate the association in Gladys and press the pairing button, the device is well discovered
 Cool!
    So, my problems are solved :grin:
42

I’ve made the choice to invest as much as possible in the Zigbee protocol, especially given the prices. So I equipped myself with a good Zigbee2mqtt dongle and I use the list of supported hardware before each purchase
 Even if it slightly reduces the possibilities!

43

Hello

Which dongle do you use that works well?

44

I replied to you on the other topic (I put it here for those who would find this topic):

https://community.gladysassistant.com/t/v4-nouvelle-installation-choix-techno/5467/20?u=pierre-gilles

45

Hello the community,

I have an issue with the Sonoff dongle. It is properly connected and seems to be detected by Gladys (it appears in the list of attached USB devices), but it never goes to the « configured Â» status when I click on « Save Settings Â».

Do you have any idea what could be blocking it? How can I investigate the issue?

I am on the latest version of Gladys (4.8) deployed manually on docker. However, I specify that I am on a 64-bit version of raspiOS. I don’t know if this can have an impact.

Cyril

Screenshot from 2022-03-14 10-10-24
Screenshot from 2022-03-14 10-10-241297×776 74.8 KB

46

Are you sure which version of Raspberry Pi OS? We do not support Bullseye for now. Debian 10 maximum, I think the issue comes from there.

The development of this Debian 11/Ubuntu > 20.04 compatibility is my current priority :slight_smile:

47

There you go, no need to look any further. Thanks @pierre-gilles, so I’ll wait for the compatibility update to be released :slight_smile:

By the way, I’ll be able to test it if needed when it’s available, since I’m already installed on bullseye.

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

And I got the image from here: Index of /raspios_lite_arm64/images

48

Bullseye

Eventually, everyone gets confused :wink:

49

Oops, well spotted @GBoulvin! Indeed :slight_smile: I’ve corrected my message

50

For information, we are now compatible with Debian 11 Bullseye: