@dipalomeri as mentioned, if using Home Assistant’s ZHA integration then you can “Download diagnostics” from the Zigbee Coordinator adapter entity and there for the “energy_scan” entry which shows a snapshot of the Zigbee channels that had the most noise at that specific time. Check out this post → I tracked channel utilization with ZHA to find the best Zigbee channel
If not using the ZHA integration then you can still perform a Zigbee energy scan with zigpy-cli → https://github.com/zigpy/zigpy-cli (zigpy-cli is a Python tool that should already be installed as part of Home Assistant’s ZHA component, so believe you only need to gain access to the correct Docker container and temporarily disable ZHA to run any of the tools, via for example the “Advanced SSH & Web Terminal” addon, but you must temporarily disable the ZHA integration if using that).
While you should try changing the Zigbee channel, you more importantly also need to be sure to always connect at least a few good Zigbee Router devices before connecting any Zigbee End Devices as they should preferably connect indirectly through Zigbee routers instead of directly.
Regardless of what Zigbee gateway solution and Zigbee Controller adapter using you should follow Zigbee best practices which involves both trying to avoid having possible sources of EMF/EMI/RMI close to any Zigbee devices and adding enough Zigbee Router devices to work around the limited range and coverage of Zigbee radios, as they all have short range and very poor wall penetration and as such rely on you having many Zigbee Router on the same network.
I highly recommend that read and try to follow this which includes taking some active actions → Zigbee networks: how to guide for avoiding interference and optimize for getting better range + coverage
Personally, I suggest buying at least three or more dedicated Zigbee Router devices that are always powered and connected. To get the “best-of-the” Zigbee Router devices today it is recommended to buy a few Silicon Labs EFR32MG21 based USB radio dongles with an external antenna (like for example ITead’s Sonoff ZBDongle-E (based on Silicon Labs EFR32MG21 radio SoC) and convert/repurpose them by flashing over USB with a Zigbee Router firmware image, after than you can simply power them via USB-changers and pair to have them work as stand-alone dedicated Zigbee Router devices. An alternative is ITead’s Sonoff ZBDongle-P (based on Texas Instruments CC2652P radio SoC) which also can be reflashed with Zigbee Router firmware and repurposed as a stand-alone dedicated Zigbee signal repeater and range extender devices. Alternatively, for all-in-one dedicated Zigbee Router products that work very well out-of-the-box, it is recommended to buy a few of IKEA’s Trådfri Signal Repeater devices and/or Aeotec’s Range Extender Zi producs. Both of those devices are based on Silicon Labs EFR32MG21 radio SoC, and many people have reported that Silabs EFR32MG21 based products with slightly better as dedicated Zigbee Router devices than TI CC2652 based producs.
Simply adding more “known good” Zigbee Router devices will make any Zigbee setup much more stable, (when in doubt, add more Zigbee Router devices). The reasons for buying and using those specific products as Zigbee Router devices are that having a few “great” Zigbee Routers (a.k.a. Zigbee signal repeaters / Zigbee range extenders) with better radios and antennas for better reception can affect Zigbee network mesh range and coverage performance positively as communication signals in Zigbee do not have to be resent. Acting as a stable backbone in your Zigbee network mesh.
Still, your first action should be to physically move the Zigbee gateway and/or the Zigbee Coordinator away from all possible sources of EMF/EMI/RMI and then do an RF scan before switching to the Zigbee channel that has the least amount of noise for your specific environment. Note that after you added more Zigbee Router devices you might as a last step also have to re-pair the devices in their final location as some devices have issues moving to a better route on their own due to crappy firmware → https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties
You have to understand and remember that each Zigbee device by itself has very limited coverage, short range and their weak signals have poor wall penetration, so to workaround this a Zigbee network relies on mesh networking (a type of network topology/technology/architecture), which means that a Zigbee network heavily depends on having a swarm of mains-powered devices are a “Zigbee Router” that are always-on so they can act as a signal repeater and range extended by transmitting data over long distances by passing data messages through the Zigbee network mesh of intermediate devices to reach more distant Zigbee devices. So while having a Zigbee Coordinator with good radio and antenna away from any EMF sources can have similar benefits, Zigbee signals have such poor range and bad wall penetration power so having many good Zigbee Router devices is a must.
Anyway, those relatively simple actions will usually resolve a majority of all Zigbee connectivity, however, there are always exceptions with bad devices and bad firmware. Crap in, crap out!
PS: Again, also note that while they are fully supported in Home Assistant’s built-in ZHA integration, Silicon Labs EmberZNet (EZSP) based Zigbee Coordinator adapters only have experimental support in Zigbee2MQTT → https://www.zigbee2mqtt.io/guide/adapters/#experimental (more information about ezsp adapter alpha status here → https://github.com/Koenkk/zigbee-herdsman/issues/319). So it is less than an optimal solution to use an experimental adapter in Z2M in combination with an unofficial and experimental installation of Home Assistant OS 
