FYI, those type of problem symtoms normally have nothing to do with the Zigbee gateway application or its device handlers but are instead usually due to with your physical environment and setup, so highly recommend that you read and try following all the relevant best practice tips in this guide too (regardless if using ZHA or Zigbee2MQTT) → Zigbee network optimization: a how-to guide for avoiding radio frequency interference + adding Zigbee Router devices (repeaters/extenders) to get a stable Zigbee network mesh with best possible range and coverage by fully utilizing Zigbee mesh networking
Another tip that is also covered under troubleshooting is to upgrade Zigbee Coordinator firmware.
Anyway, the way to do proper troubleshooting is not to change Zigbee gateway application, and suggesting that others should just move to a different Zigbee gateway application if they experince any problem symtoms does not help the community or the long term development of those Zigbee gateway application. Better to try to work with other users/testers and the developers too find the root cause and fix the problems if they truley are related bugs in the Zigbee gateway application, (chances are that they might only need to tweak a timeout or something if the problem is not simply due to poor reception).
PS: Off-topic but for reference, but adding or modifying Zigbee device handlers (i.e. quirks for ZHA and zigbee-herdsman converters for Zigbee2MQTT) are only helpful if you are missing attributes (entities) that you expect should be there. That is explained here → Zigbee Guide: How-to add/setup local custom ZHA Device Handlers (also known as ”quirks”) in the ZHA integration