Why am I Unable to Enable Remote Control in the Kasa App?
KL60B , KL130 , LB130(E27) , KL420L5 , HS107 , KL400L10 , LB230 , HS103 , KC411S , HS300 , HS105 , KL135 , LB110 , KC120 , HS200-BL , HS220 , KC200 , HS100 , KC125 , KC400 , KC401 , HS220-LA , LB100(E27) , KL50 , LB200 , LB120 , HS110 , KC411 , HS200-LA , KL50B , KC420WS , KL110 , KL400L5 , LB120(E27) , KL110B , KL130B , KL430 , KC310S2 , LB130 , KD110 , KC100 , HS200 , KC300 , KC105 , KS220M , KS200M , KL120 , LB100 , KL430E , KL125 , KC110 , KL60 , KC310 , HS210 , KC410S , KC115
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.
Why am I Unable to Enable Remote Control in the Kasa App?
If your smart device cannot be controlled remotely, or it shows “Local only” on the Kasa App, please follow the steps below to troubleshoot.
Note:
The Remote Control function of Kasa devices is enabled automatically once the device is configured and linked to the TP-Link Cloud successful. Once the setup is complete and the device is connected to the TP-Link Cloud, the Remote Control option will not be visible within the Device Settings menu in the Kasa app.
Step 1: Upgrade your Kasa device to the latest firmware
To upgrade firmware of Kasa smart devices, please refer to this FAQ.
Step 2: Turn on Remote Control
Go to the Device Settings page of your Kasa device (refer to the screenshots below). If you see a Remote Control toggle on the Device Settings page, please turn it on.
If an error message, or prompt, appears when you try to enable Remote Control, please follow the steps below to troubleshoot.
For error message: device bound to another account
This message may appear if the smart device has been bound to another Kasa account. Please verify whether have previously registered another account or bound the device to it.
If yes, please sign in with your previous Kasa account and delete the device from the list. Then, sign in to your new account and reconfigure the smart device.
If you have forgotten your previous account’s login credentials, please factory reset the device as per User Guide/Quick Installation Guide. Then configure it again with your new account.
If the issue persists, please contact TP-Link support with the MAC address of the device. You can find the MAC address of the device in the Kasa app, or printed on the label that is affixed to the smart device.
For error message: Cloud send cmd failed / Another cmd is running / other error messages
1. Please reset the Kasa device to factory default settings as per the User Guide/Quick Installation Guide, then reconfigure it.
2. Change the DNS servers of the router/gateway to 8.8.8.8 and 8.8.4.4.
Note: If you are unsure how to set custom DNS servers on your router/gateway, please consult its User Guide or contact the manufacturer for support. If it was provided by your ISP, contact your ISP.
3. Assign the smart device to the DMZ on your router using the MAC address of the smart device.
Note: If you are unsure how to assign a network device to your router’s DMZ, please consult its User Guide or contact the manufacturer for support. If the router/gateway was provided by your ISP, contact your ISP for assistance.
Step 3: Factory reset
1. Please reset the Kasa device to factory default settings as per the User Guide/Quick Installation Guide, then reconfigure it.
2. If you’re still unable to control the device remotely but are able to see the Remote Control toggle on the Device Settings menu in the app, refer to Step 2 for troubleshooting.
If the steps within this guide do not resolve your concerns, please contact TP-Link Support and one of our Support Agents will gladly assist you.
Related FAQs
Looking for More
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