PS, check your logfiles , and try to describe your use-case
I.e i have my Aquara Sensors in Aqara M2 , i have never had any issues, when others had issues with i.e MQTT or Red-Node
Beside batteries tend to get weaker faster, the colder in environment they are in ( Very common ) so if on have a weak-signal, and cold environment, one can be sure that this particular sensor P1 needs frequent battery change and/or need a reset and re-install, only solution for this is another type/brand , for concrete-basement sensors, ive change to Tapo 868MHz
FYI, all Zigbee radios and are very susceptible to interference from strong or close sources of EMF (electromagnetic fields) + have relatively poor range and building material penetration (i.e. bad non-line-of-sight propagation), so you should follow the advice in that guide and take some basic actions to avoid EMF interference by connecting the Zigbee Coordinator USB adapter via a long USB extension cable (preferably one with good shielding) as well as connecting it to a USB 2.0 port or a USB 2.0 hub (and not a USB 3.0 port/hub). The best practice is therefore to make sure that you start by adding many mains-powered Zigbee Router devices (to extend the range and coverage of your Zigbee network mesh) before adding any Zigbee End Devices (i.e. non-routers like for example battery-operated Zigbee devices) → https://www.home-assistant.io/integrations/zha#best-practices-to-avoid-pairingconnection-difficulties
I have my SkyConnect on a long-ish USB cable near the ceiling. When It was close to the PC, there were occasional log messages about RF channel congestion but these have gone away.
I am using a USB3 port - could that be my problem? Why is USB2 preferred?