Maybe you have not used all fatures, but you can follow links in latest Zigbee2MQTT documentation:
ATTENTION
Various features are not supported by this adapter, in case you depend on these features, consider a different adapter.
- Changing the channel, changing requires re-pairing all devices.
- Adding install codes, which is required to pair some devices.
- Backups
- Inter-PAN, which is required for touchlink
- Changing the transmit power
Previously those “limitations” with the ConBee/RaspBee firmware and deCONZ Serial Protocol is was only indirectly mentioned in Zigee2MQTT’s FAQ and in troubleshooting section of the ZHA docs:
While you can ignore or workaround some of those but sucks not having a backup or install code support and then needing them, so those two are why I think ConBee should not be recommended to new users:
Note that the “no backups” is a Zigbee2MQTT issue (due to lack of deconz developers in the Z2M project) but the lack of install code support affect both ZHA and Zigbee2MQTT is there is no support from dresden-elektronik as of yet:
While I can only speak for myself, think I can still say that as it stands right now many of us who are a part of the overall ZHA and Zigbee2MQTT communities can no longer not with good conscience recommend ConBee II or ConBee III to new end-users that want to begin using ZHA and Zigbee2MQTT. Hence my recommendation in that Zigbee buyers guide:
It also seems to be that Zigbee2MQTT’s zigbee-herdsman project (the Zigbee library that Z2M depends on) currently only has one lead developer who is focusing on the “zstack” driver (Texas Instruments Z-Stack ZNP adapters) and another lead developer who is focusing on “ember” driver (Silicon Labs EmberZNet Serial Protocol adapters), but it currently has no developers that are focusing on their “deconz” driver (Dresden-Elektronik’s deCONZ adapters like ConBee and RaspBee) so it only gets minor break-fix patches or generic patches that applies to all their drivers and not major new features like backups for deconz adapters: