Devices identified as having an older Zigbee revision. These can be the source of problems, especially if `pre-21`.
Failed to set a configuration parameter. Usually when the coordinator has lower memory than others. In-firmware value will be used instead.
Conflicting device IDs. Two devices cannot have the same ID on the same network. The involved devices are kicked off the network then should rejoin (may need to re-pair them if not).
Network/Route errors. These are accompanied by a status that describes in more details the source of the error. A few of these over time is expected (or on Zigbee2MQTT start), too many, too often, is indicative of a problem in your network.
`NOT READY - Signaling NCP`: `ember` driver is temporarily overloaded. The coordinator is made aware and processing is deferred for a short period.