@bobbin1410 

Hi,

Like you already mentioned, the IoT network is just another Wi-Fi network (i.e. SSID) that allows you to set a different network name, security protocol and password. That's it.

Device Isolation isolates the devices in the "Isolated Devices" list from other devices on the router's network.

On most network cameras designed for home use the communication between the camera app and the camera happens through a server on the Internet (i.e. the "cloud"), so that you can access the camera located at your home from anywhere in the world. That's most likely the reason why you think the Device Isolation feature doesn't work.

Also, setting up a second Wi-Fi network (SSID) on the same physical Wi-Fi radio (i.e. hardware) as the "main" Wi-Fi network doesn't help your main Wi-Fi network's traffic.

TP-Link's Archer routers don't support setting up VLANs.

  @woozle 

thanks on info re iot ssid That clarifies things,   I like being able to change guest password w/o reprogramming all my iot stuff.

But ill have to investigate the isolation more,   
 

  @woozle 

thanks very much for the helpful info :-)

I think what you say makes sense about putting devices into the 'Device Isolation' pool - I have tried this with 2 cameras and 3 smart plugs.  Whilst I can indeed use the native software to control the devices, I cannot use the Apple 'Homekit / Home' feature to control these devices like I normally do presumably because this relies on local LAN communication rather than using the cloud.  If I remove the devices from isolation, then Apple Home works fine again.

Seems tricky to have a secure way of segregating IoT devices like plugs/lights/cameras (for security aswell as protocol/wifi network maangement) in a way that allows you to operate them conveniently using 'one' platform like Apple HomeKit rather then having to switch to potentially multiple 'cloud' based native control devices...one for cameras...another for lights...another for plugs etc.

Any ideas?

Many thanks