Hi  @DFSR 

Thank you for reaching out to us. I understand that you are experiencing issues with the "HeartBeat Missed" error and roaming problems in your TP-Link network setup. Here are some steps and insights to help you resolve these issues:
HeartBeat Missed Error
The "HeartBeat Missed" error indicates that your device is losing connection to the controller for more than 5 mins. This can be due to several reasons, including physical connection issues, network congestion, or configuration problems. Here are some troubleshooting steps you can follow:
Check Physical Connections: Ensure that all cables are securely connected and that there are no loose connections.
Verify Controller and Device Compatibility: Make sure that your TP-Link devices and the Omada Controller are running the latest firmware and software versions.
Check Network Congestion: Ensure that your network is not overloaded. High traffic can cause the controller to miss heartbeats from devices.

Roaming Issues
Roaming issues can be caused by various factors, including signal strength, channel overlap, and client device settings. Here are some steps to improve roaming performance:
Signal Strength: Ensure that all access points have sufficient signal strength to cover the areas where clients will be moving. You may need to adjust the placement or power levels of your access points.
Channel Planning: Avoid channel overlap between access points. Use non-overlapping channels to reduce interference and improve roaming performance.
Client Settings: Some client devices have settings that can affect roaming behavior. Check the roaming aggressiveness settings on your client devices and adjust them if necessary.
Omada Controller Settings: Ensure that the Omada Controller is configured to support seamless roaming. Check the roaming settings and make sure they are optimized for your network.
Additional Tips
Firmware Updates: Regularly update the firmware of your TP-Link devices and the Omada Controller to ensure you have the latest features.
 

Side note:  You are not requesting a feature, and this was posted on a wrong block. Next time you are seeking for help, please go to the correct block to get a timely help.