@knowledgeseeker 

Hi

Currently, OneMesh and EasyMesh are designed to only support the expansion of the main network and do not support the expansion of IoT and guest network. However, we have indeed received requests from other customers that they hope mesh can also be extended to IoT network and guest network, so our engineers are continuing to evaluate its feasibility.

Since you also have this demand, we hope you can provide more details for the reference:
1. Why do you want to connect smart home devices to the IoT network? Does it need to be used in isolation from the main network? If so, since mesh currently does not support the expansion of the IoT network, please try to connect the smart home device to the main network and set device isolation to check if it can meet the need. The device isolation configuration method is as follows:

https://www.tp-link.com/support/faq/3968/
2. What are your true needs for the mesh IoT network, if you are not attempting to isolate devices? We would be grateful if you could describe it in detail.

  @Joseph-TP 

I'll answer your questions in the order asked.

1. The reason for connecting IoT devices to a dedicated IoT network is in order to keep them all on a separate network, but still to be able to communicate with them via the likes of Homeassistant.

My IoT network is almost entirely made up of Tapo devices which I went for because of their ease in setting up, however I also have other devices such as Shelly and Eufy and while it would be nice to stick owith one eco system such as your own one, the Homeassistant offer more flexibilty, if I place devices on the device isolation list then they are no longer accessible via Homeassistant.

2. The true needs for an IoT network are to be able to prevent the devices from trying to gain access to a 5G network as most don't support that and also control who they are chatting to outside the network.

I live on a rural property and I have a separate guest house which is out of range of any wifi router, this is connected via Cat6 cable and two Ubiquiti long range bridges as well as a TP-Link EAP, curently with the new BE19000 I can only see the main network and have lost the ability to use the IoT network and Guest network in this separate abode. This was working fine with the previous ASUS TUF router.

But the thing that irks me the most about these restrictions is your very own sales blurb says you can eliminate dead spots in a house using a mesh system, it also offers an IoT network by default and nowhere does it say this doesn't function over the mesh system, so what you say you are offering is not correct! If IoT devices need to be connected to the main wifi network then they are cluttering up the bandwidth, and there's no point in even offering a dedicatded IoT network in the first place if it can only be used within close proximity to the router. Given that most houses suffer from deadspots and some form of mesh system is the best option to eliminate these issues, one would thing that an separate guest and or IoT network would be carried over by default with the mesh, especially when the network devices have all in all cost in excess of >$2K to purchase.

You also don't offer a VLAN option other than the IPTV/VLAN which as far as I can tell isn't really a dedicated VLAN, so I feel like perhaps I have wasted my money and should ditch all the TP-Link gear in favour of Ubiquiti which seems to offer more options.

  @David-TP 

Thanks for the response.

Given that I've just dropped $1k on a router and probably close to that for the various extenders that I've purchased in order to use the Tp_link eco system what are the chances orf you recycling my current hoard of plastic and part exchanging them for the mentioned Deco kit? I imagine this will be close to zero.

Shame, more plastic polution in the World and less money in my pocket.

  @David-TP 

The BE19000 was purcahsed from PB tech here in New Zealand and was on special at $1049 NZ$, unfortuantley the various RE605X and RE305's have been purchased over time from various retailers and as such ar unlikely to ba accepted back as returns, which leads me to having to shell out more cash for another lot of gear. There is a saying in finance that you don'ty throw good money after bad money, and so I don't think I will be spending more money on your systems at this time.

Further more the WiFi 7 items you listed are not available in NZ at this time.

Thanks for your responses though, it looks like I am stuck with this for now.

Perhaps when you get all your gear communicating with each other as advertised I will revisit the system.

  @Joseph-TP 

To echo knowledgeseeker's commentary... it's rediculous that you all don't support IoT OR guest networks within the EasyMesh environment.  Your competitors do and moreso, those making lower cost versions do including Reyee, which all support it within their E5 and E6 routers and quite well.  It's astonishing that you all would think to offer an IoT network option without thinking the need to have it across a mesh environment.  

To echo that as per your first question... do you not think that a person whom has a need for a mesh in the first place might need ALL of their networks to have the same extension, or do you believe that everyone keeps all of their IoT devices within a small usable margin within the range of one router (be it a multi-story or large/expanded house)?  The answer is ALWAYS, if one needs a meshed network in the first place, and also needs a guest network, IoT, or other different SSID network...they most definitely need those SSIDs also a part of that mesh, especially when wire-backhauled. 

To expand on the second question, with a question, why would anyone need an IoT network in the first place?  Most likely, to relieve congestion from other wireless devices on their main network...seems pretty simple.  Same with guest networks...I may want to keep my visitors off the main network, while giving them access to the internet.  That would be pretty stupid to only give them access around the main router, instead of in the guest bedroom where they are sleeping, or rather, what we EXPECT...THROUGHOUT OUR DEPLOYED NETWORK RANGE.  Pretty simple.  

I myself, literally went from you all with a set of wired AX1500s meshed to your competitors to have a dedicated IoT network and have it meshed as part of a deployment within my house so that I could have all of my IoT devices (smart lights, switches, security cameras, thermostats, garage door openers, etc) on their own network without signal loss.  I went with Reyee's E5s and E6s, which did great, outside of their WAN side issues.  I literally came back to you all with the BE3600s as a remedy for that...to just be disappointed with buyer's remorse that I'm not getting what I paid for.  

The ultimate kicker here is that to get what is advertised...IoT networking and mesh...I have to buy the Deco Mesh system...talk about bait and switch.  It's time to get to the R&D tables and get what we are asking for here...as in yesterday.  Or at least, open your firmware up so that the kind folks with DD-WRT/Open-WRT can do the job right.  

  @knowledgeseeker 

As said above, its crazy you seem to be not only so far detached from the needs of your customers but the details on your website are abmbiguous at best abnd mis-leading at worst.

You really need to think about how your developers interact with the feedback from your customers.

If the DECO system is so good, why not use this as the basic for all of your router/extender/mesh platform instead of having all these different ranges that from reading the forums, actually never meet all of anyones expectations let alone needs.