Remote Error with KL130

Remote Error with KL130
Remote Error with KL130
2019-09-14 02:51:44 - last edited 2019-09-17 23:58:24
Model: KL130
Hardware Version: V1
Firmware Version: 1.8.6

I am having issues with setting up a remote connection after I have reset my Kasa Smart bulb KL130. To begin, I found my light unresponsive so I did a master reset by turning it off and on 5 times. This resolved the connectivity issue with my network but did not clear up the Remote Access issue, I get the message, “cloud send cmd failed”. Any help is appreciated. Thanks. 

 

If you need a screenshot or further information, please let me know.

 

Tim

0
0
#1
Options
1 Accepted Solution
Re:Remote Error with KL130-Solution
2019-09-17 23:57:50 - last edited 2019-09-17 23:58:24

@Tony 

Thanks for your reply and help! 

I did what you asked by resetting the bulb, I also noticed when I was in my router settings that I had blocked an “anonymous” user, ended up matching the MAC address with the lightbulb that I was having an issue with and unblocked in my settings of my router. Everything working now.

 

Thanks again!

 

Tim

Recommended Solution
1
1
#3
Options
3 Reply
Re:Remote Error with KL130
2019-09-16 17:23:41

@TechyTim90 

 

Please remove the bulb from the Kasa app, and do the complete factory reset one more time. After setting the bulb up wait several minutes, to see if the local only is gone.

 

Do you have other TP-Link devices that work remotely?

0
0
#2
Options
Re:Remote Error with KL130-Solution
2019-09-17 23:57:50 - last edited 2019-09-17 23:58:24

@Tony 

Thanks for your reply and help! 

I did what you asked by resetting the bulb, I also noticed when I was in my router settings that I had blocked an “anonymous” user, ended up matching the MAC address with the lightbulb that I was having an issue with and unblocked in my settings of my router. Everything working now.

 

Thanks again!

 

Tim

Recommended Solution
1
1
#3
Options
Re:Remote Error with KL130
2019-09-18 15:20:58

@TechyTim90 

 

Thanks for the update.

 

Glad you were able to find the fix.

0
0
#4
Options