If you prefer to have a Zigbee gateway that does not depend on the cloud there are some options:
USB dongles supported by ZigBee - Bindings | openHAB You should pay attention to the coordinator limits (# of devices) range (CC253x is known to have a weak antenna) and placement (zigbee can interfere with wifi, so proximity with AP’s should be avoided and this often requires a usb extension cable)
Build a MQTT network and use a Tasmotized coordinator. MQTT is more complex than using the zigbee binding. I use a Sonoff ZBBridge and I’m very happy. It can be installed anywhere 5VDC is available (which can be supplied by a mobile charger)
For larger distances (>5m) you may need zigbee routers (which are similar to wifi extenders). Some zigbee devices (such as lamps and sockets) can act as routers.
My objective was to get rid of the Sonoff cloud. I’ve
tasmotized with tasmota-zbbridge.bin.gz followed by ncp-uart-sw_6.7.6_115200.ota
used tasmota commands SetOption83 1, SetOption89 1 and SetOption112 1
parametrized MQTT credentials
paired my zigbee devices with the ZBBridge
And, because my IoT wlan has no internet access, I had to create a NTP server elsewhere (I have a OpenWrt router that also runs a MQTT broker and a NTP service) and parametrize tasmota accordingly (otherwise zigbee stack does not work)
I want to set up my PI3 with Openhabian3 so that I do not have to use the gateway from Xiaomi.
Unfortunately, according to Internet analysis, the Openhabian3 system does not support the Xiaomi Gateway3.
I have a ZigBee stick CC2531 connected to the PI.
When I call lsusb in Putty I get 4 devices
Bus 001 Device 005: ID 0451:16a8 Texas Instruments, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub