Contradiction between TP-Link standard support page and official response from TP-Link support
Contradiction between TP-Link standard support page and official response from TP-Link support
The generic TP-Link documentation (standard support page) states that isolated devices can communicate with each other - only the "rest of the network" (non-isolated devices) is blocked.
The official response I received, in point 2, states verbatim that isolation "prevents communication between the main network, the guest network, and other devices within the IoT network itself."
This would imply that communication between two isolated devices (including my smartphone, if it is also isolated) would be blocked.
Which of the two explanations is correct?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
The standard TP-Link documentation is correct. Isolated devices can communicate with each other.
tp-link.com
Official behavior of Device Isolation on Deco (including XE75 Pro)
From TP-Link’s support FAQ and related official explanations:
- Isolated devices can still access the internet.
- Isolated devices can communicate with other isolated devices (they are effectively placed in the same isolated group/pool).
- Isolated devices cannot communicate with non-isolated devices on the main/home network (or transfer data with them, manage the gateway, access USB shares, etc.).
This is stated explicitly in the Device Isolation setup guide:
“While isolated, the devices can still access the internet and are able to communicate with other isolated devices. However, isolated devices cannot transfer data with devices on your home network…”
tp-link.com
The same point appears in TP-Link community knowledge-base material and multiple staff-confirmed explanations: isolated devices form their own group and can talk to one another, regardless of whether they are on the main SSID or the IoT SSID.
community.tp-link.com
Why the support reply contradicts this
The reply you received (“prevents communication between the main network, the guest network, and other devices within the IoT network itself”) is inaccurate or poorly worded.
- The IoT Network itself is not isolated from the main network by default.
- Device Isolation is a separate feature that puts selected devices into an isolated group.
- Within that group, inter-device communication is allowed (this is intentional so that smart-home hubs, controllers, and related IoT devices can still talk to each other locally).
Guest Network isolation works differently (devices on Guest are separated from the main/IoT networks and, depending on settings, often from each other). Device Isolation does not work the same way.
Practical takeaway for your Deco XE75 Pro (V3, firmware 1.5.0 Build 20260603)
If you put Device A and Device B (and your phone, if needed) into the Isolated Devices list, they should be able to communicate with each other while remaining blocked from everything that is not isolated.
If local control between specific devices is broken after enabling isolation, the usual cause is that one of the devices (or a required hub/controller) was left non-isolated.
You can safely rely on the published support documentation rather than the conflicting support reply. If the feature is not behaving as documented on your unit, it would be worth opening a new support ticket and linking the official FAQ.
Thanks
- Copy Link
- Report Inappropriate Content
The standard TP-Link documentation is correct. Isolated devices can communicate with each other.
tp-link.com
Official behavior of Device Isolation on Deco (including XE75 Pro)
From TP-Link’s support FAQ and related official explanations:
- Isolated devices can still access the internet.
- Isolated devices can communicate with other isolated devices (they are effectively placed in the same isolated group/pool).
- Isolated devices cannot communicate with non-isolated devices on the main/home network (or transfer data with them, manage the gateway, access USB shares, etc.).
This is stated explicitly in the Device Isolation setup guide:
“While isolated, the devices can still access the internet and are able to communicate with other isolated devices. However, isolated devices cannot transfer data with devices on your home network…”
tp-link.com
The same point appears in TP-Link community knowledge-base material and multiple staff-confirmed explanations: isolated devices form their own group and can talk to one another, regardless of whether they are on the main SSID or the IoT SSID.
community.tp-link.com
Why the support reply contradicts this
The reply you received (“prevents communication between the main network, the guest network, and other devices within the IoT network itself”) is inaccurate or poorly worded.
- The IoT Network itself is not isolated from the main network by default.
- Device Isolation is a separate feature that puts selected devices into an isolated group.
- Within that group, inter-device communication is allowed (this is intentional so that smart-home hubs, controllers, and related IoT devices can still talk to each other locally).
Guest Network isolation works differently (devices on Guest are separated from the main/IoT networks and, depending on settings, often from each other). Device Isolation does not work the same way.
Practical takeaway for your Deco XE75 Pro (V3, firmware 1.5.0 Build 20260603)
If you put Device A and Device B (and your phone, if needed) into the Isolated Devices list, they should be able to communicate with each other while remaining blocked from everything that is not isolated.
If local control between specific devices is broken after enabling isolation, the usual cause is that one of the devices (or a required hub/controller) was left non-isolated.
You can safely rely on the published support documentation rather than the conflicting support reply. If the feature is not behaving as documented on your unit, it would be worth opening a new support ticket and linking the official FAQ.
Thanks
- Copy Link
- Report Inappropriate Content
I isolated most of the home automation.
Also taking into account that some of the home automation has its own external communication channels, separate and outside of its own network.
---
But I have several webcams that - in addition to transmitting videos to the proprietary apps installed on smartphones/tablets - upload the videos via FTP to local storage devices like NAS and then to the cloud.
Among various tests, I attempted to "isolate" these webcams in the iOT Deco subnet, but the result was that for a few sessions, the videos were visible from the respective apps on the mobile devices, but then became inaccessible, even though the FTP upload always worked.
When the isolation was removed, the webcams were visible again from their mobile apps as well.
What I'm wondering is how the mobile isolation setting affects this.
Perhaps by also activating the mobile isolation (which is normally not isolated), the video viewing returns?
Thanks . .
- Copy Link
- Report Inappropriate Content
Try the following and see if it helps.
- Put the cameras and the phones/tablets that need to view them into the Isolated Devices list.
- That way the cameras and phones can still talk to each other (as isolated devices are allowed to communicate among themselves), while remaining blocked from the rest of the non-isolated network.
Thanks
- Copy Link
- Report Inappropriate Content
HelpFixDecoApp wrote
Try the following and see if it helps.
- Put the cameras and the phones/tablets that need to view them into the Isolated Devices list.
- That way the cameras and phones can still talk to each other (as isolated devices are allowed to communicate among themselves), while remaining blocked from the rest of the non-isolated network.
Thanks
@HelpFixDecoApp
As I wrote in the post above, shortly after enabling webcam isolation, the webcam video stream became inaccessible.
It seems that the specific isolation of the webcams makes them unusable.
Tks
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
To help us investigate further, please confirm whether the following information is correct.
Case 1: The webcams are added to the Device Isolation page, while the mobile devices are not. In this setup, the app installed on the mobile devices cannot access the camera; however, FTP uploads continue to function properly, and recordings can still be saved to the NAS(non-isolation device) connected to Deco.
Case 2: Both the webcams and the mobile devices are added to the Device Isolation page. In this setup, the app on the mobile devices still cannot access the camera, but recordings can still be saved to the NAS (non-isolation device).
In both cases, could you please verify whether the mobile devices and the NAS can successfully ping the webcam's IP address?
How to Use the Ping Command
Best Regards
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi,
To create a second network to separate IoT devices and other sensitive devices, you may create a guest network for IoT devices to connect to. When Deco works in Router mode, the guest network is isolated from the main network. When Deco works in AP mode, disable the Allow Local Access option in Guest Network > Advanced Settings; the guest network is isolated from the main network.
Regarding the isolated webcam continuing to transmit the video feed via FTP, if the NAS is not isolated, it may be accessing the webcam via the internet rather than a local connection. If you would like us to investigate further, please provide the following information.
1. Are the webcam and NAS connected to the Deco's main Wi-Fi network? What are their IP addresses? What is the Deco's WAN IP address?
2. Please provide the specific FTP access path, such as ftp://IP or domain: port number.
Best Regards
- Copy Link
- Report Inappropriate Content
@Solla-topee
When setting up the Deco units, I didn't consciously use the "Guest" network—partly out of ignorance—but instead created a dedicated IoT subnet.
I understand that the Guest network offers greater device isolation, but I had read - perhaps in this very forum - that the isolation of the Guest network is not absolute. That’s why I chose to create an IoT subnet rather than using the Guest network.
---
Regarding the isolated webcam that keeps transmitting its video feed via FTP: the stream travels through the Deco to the router, and—using the FTP settings—writes the video data to specific folders on the NAS.
"Are the webcam and NAS connected to the Deco's main Wi-Fi network?" The webcam(s) are connected to the Deco (which performs NAT), while the NAS is on the network of the router/access point that handles NAT for all network devices—including the Deco.
Sorry, but I prefer not to share my network data. It’s a security matter.
Thanks..
- Copy Link
- Report Inappropriate Content
Hi,
Thank you for the information; it confirms the Deco works as expected.
1. When you create an IoT network and the webcam is connected to the IoT network, the phone connected to the Deco's main Wi-Fi network/IoT network can access the webcam; this is normal. After you isolate the webcam, the phone can't access it; this is also normal.
2. Please note that when Deco works in Router mode, the guest network and the main network/IoT network are isolated by default. When Deco works in AP mode, if the "Allow Local Access" option is enabled, the guest network and the main network/IoT network are not isolated.
3. Deco can't manage the devices connected to the front router, if your NAS is connected to the front router rather than Deco, even if the webcam is isolated, it's video can still be stored on the NAS. To prevent the video from being stored on the NAS, you need to isolate the NAS and main Deco on your front router.
Best Regards
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 574
Replies: 12
Voters 0
No one has voted for it yet.