@ToneAU 

Yeah I'm having the same issues with 1.2.0 beta.

I have a call scheduled for tonight at 8PM for remote assitance.

I even added my mixed mesh back in, so they can see that acting weird as well that way I don't have to do a calla gain later.

I had a call scheduled for remote support at 8PM, no one showed up. Then scheduled a second call at 1AM and again no one has shown up. I sent follow up emails and no responses. This is ridiculous. I should not have to go through all this after unboxing a brand new purchased product! How can TP-Link sell a product that does not function?

Edit:

Also, I'm now having a new problem. All of my wifi cameras fail to load through Apple Home Kit while on wifi, but they load just fine when connecting on cellular. Additionally, when viewing ethernet cameras they work fine on a wired device. And on top of that, all the cameras native apps work properly wifi or not. 

  @David-TP 

I appreciate it.  I just want to know if i can get this to work before my return window closes. 

  @Murtaza911 this is terrible!! I'm seeing more people with same or similar issues now in this support community.
 

TP Link, are you taking these concerns seriously? I'd suggest you pull that firmware from your product download page until you sort this mess out. 
 

@Murtaza911 please keep this forum posted with any developments. 

They finally joined around 2AM, and went right at it. Spent about 3 hours trying to figure out whats going on. They SSHd into the routers running a bunch of commands.

It looked like everything was fixed, connection was very stable nothing was offline. Even the issue where some devices wouldn't adhere to the connection prefernce of thier ssigned node seems to have been fixed.

They also tried to sort out my camera issue. They were able to get the camers to stream again, but said it was only a temporary fix and if i reset the deco it would be undone. Need to wait for a response for the R&D team for a solution.

However, I woke up today to a bunch of disconnecting and reconnecting again. It seems to be much more stable than it was. But the problem still isn't fixed :(.

Not sure how how much more time to invest in this set up.

  @Murtaza911 Appreciate the update to this tread. If a Senior Engineer isnt able to identify or offer solutions to reolve these critical bugs, this is concerning, and I'm not so sure what a Research & Devleopment function could offer.

The suggestion about switching off MLO and 6GHz I wouldn't even be entertaining, as the Senior Engineer would have suggested this, if it were a viable, if only temporary solution.

What is very odd, firmware 1.1.7, whilst has some bugs, is nowhere near the critical mess of 1.2.0 that some of us are experiencing. I'm not sure why TP Link wouldnt compare the change log between those two versions.. that may lead them to why some of these issues are occuring.

@David_TP-Link will you be kind enough to please keep this thread updated, and I'm sure you are now seeing more people adding threads in your community forum highlighting concerns with this firmware, and those like it.

  @ARGamingPK1 

Yes it has been off since day one.