As mentioned there in that issue by zha devs, that is not a ZHA application-level wrror but instead a low-level error that comes from the Zigbee Coordinator stack which manages your Zigbee network the root cause must be enviromental, meaning interference or other which is best resolved by following best practices which includes taking actions to avoid interference and also adding many more Zigbee Router devices to strengthen your overall Zigbee network mesh (because Zigbee is very sensitive to interference and depend/relies heavily on mesh networking so need loads of Zigbee Routers) → Zigbee networks: how to guide for avoiding interference + optimize using Zigbee Router devices (repeaters/extenders) to get a stable mesh network with best possible range and coverage