What to do if the Omada App Can’t Find my AP
EAP680 HD , EAP620-Outdoor HD , EAP670-Outdoor HD , EAP245 , EAP683 , EAP673-Extender , EAP230-Wall , EAP680 , Omada EAP770 , EAP215-Bridge KIT , EAP235 , EAP650-Outdoor , EAP610 HD , EAP653 UR , EAP660 HD , EAP625-Outdoor HD , EAP670-Outdoor , Omada EAP780 , EAP673 , EAP670 , EAP115-Bridge , EAP235-Wall , EAP215-Bridge , EAP610-Outdoor , EAP115-Wall , EAP610GP-Desktop , EAP683 UR , EAP225-Wall , EAP655-WE-AC , EAP211-Bridge , EAP225-Outdoor , EAP223 , EAP783 , EAP265 HD , EAP115-Bridge KIT , EAP620 HD , EAP613 , EAP615-WE , EAP610 , EAP653 , EAP211-Bridge KIT , EAP655-Wall , EAP615-Wall , EAP773 , EAP772 , EAP650 , EAP683 LR , EAP770 , EAP690E HD , EAP615GP-Wall , EAP723 , EAP623-Outdoor HD , EAP110-Outdoor , EAP650-Wall
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Contents
This article will cover various troubleshooting methods when the Omada App can’t find your AP.
- Omada App
- Omada AP
The suggestions below will help you troubleshoot when the Omada App can’t find your AP.
Step 1. If, when you install the AP for the first time, the AP is broadcasting Wi-Fi and working correctly, but you are unable to find the AP on the Omada App:
- Login to the Omada App and go to Standalone Mode.
- If you have not connected to an SSID, the error will be “No WLAN Connection.” Like in the screenshot below, you can click “How do I connect to an EAP” to guide you to connect to the AP wirelessly.
- If you have connected to an SSID that is not configured on the standalone Omada AP, the error will be “No EAPs Found in the LAN,” like the screenshot below:
Please check the AP's LED status and ensure you’ve connected to the standalone Omada AP’s Wi-Fi and that the Internet from the AP is working. If not, please contact TP-Link Technical Support for further troubleshooting.
Step 2. If the LED on AP is solid ON and the Internet is working fine, please try the troubleshooting steps:
- Make sure your AP model supports the Omada App. For further information, you can refer to the Omada Compatibility List
- Move your phone or tablet closer to AP and try again.
- Turn off your phone’s mobile data and VPN, then try again.
- If your phone or tablet is an iOS system, please go to Settings->Omada->Enable “Local Network.”
- Check the connectivity between the AP and the Phone or Tablet. Check whether the phone or tablet associated with the AP's SSID can ping the AP successfully. If not, ensure that Guest Network/Portal/other network access control functions are not configured on this AP.
- APs managed by the Controller cannot be discovered by the App.
- Try another phone or tablet and see if the AP can be detected.
- If you have multiple APs, please try other APs and see if the Omada app can find them.
- Please connect to AP’s SSID and see if you can launch AP’s Web UI by entering http://tplinkeap.net or its IP address via a browser.
- Force to stop the Omada App and relaunch it.
- Reboot and reset AP, then try again.
The above suggestions will help you to find your AP on the Omada App. If the above suggestions still can’t help you, please contact TP-Link Technical Support with the following information:
- The specific model of your AP.
- The hardware and software version of your AP.
- The Omada App version.
- All the troubleshooting steps you’ve done.
To learn more about each function and configuration, please go to the Download Center to download the manual of your product.
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or