Best practice is to start by reading and try following all the tips here before troubleshooting any deeper → 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
It could be that you have one or two devices that are faulty or have buggy firmware, but with those symptoms the most common problems is either caused by EMI/RMI/EMF interference or by the user simply just not having enough “good” Zigbee Router devices, as well and placing those “good” Zigbee Router devices in strategic locations to spread them out to get best possible range and coverage
Suggest that you buy many more Zigbee Router devices or alternatively a few “known good” (or better make yourself a couple “known great”) dedicated Zigbee Router devices. First though, before purchasing anything I highly recommend you begin by reading my whole guide and try to follow all the best practice tips there → 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
Zigbee is both susceptible to EMI/RMI/EMF interference and more importantly Zigbee relies heavily on mesh networking so it depends on you having many Zigbee Router devices as part of its mesh network.
That linked guide includes some specific products that are good or great Zigbee Router devices, and it also include the tip to try changing to a different Zigbee channel if nothing else is helping/working (which is now even possible to change in the ZHA UI to make it easier) → https://www.home-assistant.io/integrations/zha#defining-zigbee-channel-to-use
Otherwise you would normally only need to keep adding many more Zigbee Router devices until your mesh network is built out to active good reception to the required range and coverage.
While using a USB 3.0 port might be unlikely to be the root cause for your issues it is still known to cause issues so better remove that factor if possible as USB 3.0 (really all USB 3.x and USB 3.x) is infamously known to cause serious EMI/RMI/EMF interference issues with Zigbee (as well as Bluetooth and Thread) in some circumstances, so recommend you just to be sure buy a powered USB 2.0 Hub (a USB 2.0 Hub with its own external power-supply) and connect your Zigbee Coordinator adapter dongle via it instead. That USB 2.0 hub will in practice act like a USB 3.x to USB 2.0 converter and as such at least isolate the Zigbee Coordinator adapter dongle (and can also be used with ). Such USB2 hubs usually cost less than $20(USB) and are totally worth it to eliminate that potential issue, see example → https://www.amazon.com/s?k=usb+2.0+hub+powered
Again, I highly recommend you read my whole guide regardless which among many other best practice tips also include links to and empirically documented tests that show how USB 3.0 will interfere with Zigbee signals → 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
That should not be any huge difference (as long as using a long USB extension cable to a USB 2.0 port to avoid EMI/RMI/EMF interference), becuase Zigbee relies so heavily on mesh networking so it is really all your Zigbee Router devices that should make the mesh network work, with almost just the closest Zigbee Router devices connecting directly to the Zigbee Coordinator and all the rest only connecting indirectly via other Zigbee Router devices.
However, note that EmberZNet 7.2.x.x and later firmware is yet mature enough to be well proven as stable (though the EmberZNet 7.3.x.x has so far tested very good), thus it is probably a good idea to downgrade for now, and do make sure to use the EmberZNet “NCP” (i.e. the dedicated Zigbee firmware) and not the “RCP” Multi-protocol/Multi-PAN firmware for Zigbee and Thread (as Mult-protocol/MultiPAN firmware for Zigbee is no longer maintained because it is known to have issues and not be stable Multi-protocol was always only experimental anyway), check out:
and