@Zurler 

Yes, as long as the device is bound to the same TP-Link Cloud account it does not matter if they are local or remote.

@Tony But it won't let me connect at the second location, because your app keeps searching for my network at the first location. I set up another TP-Link account using my wife's name, then the switch was recognized on my local network at the second location.  However, Alexa won't connect with the switch in my wife's Tp-Link account.  Alexa of both locations are under one account.

Tony wrote

@Zurler 

 

Yes, as long as the device is bound to the same TP-Link Cloud account it does not matter if they are local or remote.

@STC0922 

You need to physically be at the second location or alternatively, you can have someone who is already at house 2 log into Kasa with the same account you set up the plugs in house 1.

So for example, you are at house 1, and you just set up all the plug switch your TP-Link ID named myID. You then physically go to the second house with your smartphone, then begin the setup for the plug at house 2 while still logged in with the same myID account. 

You can not stay at house 1 and set up the plugs at house 2 or set them up remotely.

As long as both houses use different account that will not work. When authorizing the Kasa skill that needs to be the same Kasa account, just like how you used the same Alexa account for your houses, it is the same concept.

@Tony 

I have been dealing with this a bit recently. It's pretty clear that Echo/Alexa has no idea about homes. That makes dealing with multiple homes a problem. 

I set up my primary home with primarily Zigbee and Z-Wave home automation, though a hub, and with Echos for voice control. All good. But I did have a Nest thermostat, eventually got a Nest doorbell, and a Google device for control as well. 

When setting up the second house, I found that Google understands houses and rooms. And of course, Google has pretty reasonable IoT support for WiFi devices -- not as robust as the Wink hub I have at the other house, but I figured I'd give it a go. The Kasa switches were the fastest IoT setup I've done, they work great with Google, no problems at all. But the Google voice interface really makes it. I can say "turn on kitchen lights" in either house, and the correct lights come on. That's impossible with Amazon, at least on one account. I've only set up basic things on the Kasa app itself, light scenes, timers, and sunset-based control. I'd be able to program everything I need in that along if it only had some kind of "home" and "away" mode, to change between timers I use when I'm at the beach vs. those I want running when I'm away. 

@DaveHaynie 

A response I can think of would be to create groups? However, I don't think that is fully what you described. I'll forward that as a feature request for consideration.

@Tony 

please put in a feature request to allow "homes" like so many other smart home products. I have a vacation rental and it's hard to keep them straight when they all blend together in the app even though they are in different houses. Very important feature that's missing. With that, Kasa is 5 stars. 

I second that. 

When managing two homes it's heard to deal with it from the same account. 

I considered making a seconf account but it's really kind of inconvenient to logout, remember the password, and log in again.

Yes. While you're setting up the products in the Kasa app, you will get the opportunity to set a custom name and icon for each smart device. When you pair them to Alexa or Google Assistant, you can also divide the Smart Home products into groups to control them.

Removal of curse

Thanks for the update. vashikaran specialist near me Al Ain