Please keep us posted.  I just noticed that my Deco app has the firmware upgrade but I am hesitant to try for fear that the "upgrade" will break something.

My current firmware works but I see that v1.3.1 has some features that I could really use.

@TP-Link Still can't figure out why the only firmware reference by TP-LINK here is 1.2.8.  Was 1.3.1 pulled for problems like 1.3.0 was ?

FWIW,  I decided to try the firmware.  I have a V1 M5 Deco, one as a router with 2 mesh enabled satellites, all connected by ethernet.  The upgrade went smoothly, retaining the existing settings for my network including my custom DNS, port assignments, and port forwarding.  It appears all my devices are connected without any help from me.  So far so good.

My only complaint so far is that while they have enabled a web based front end to the Deco, there is little you can configure with it.  You will still have to rely on the phone app for set up and configuration.  I hope this is work in progress and eventually we will have full control over the Deco through a browser.

Running the official 1.3.1 now too (M5 v2)

all good so far from my end too. no more drop outs/authentication failures from the 1.2.8 nightmare

Unfortunately after installing the 1.3.1 update, one of my IOT devices (a Hunter Cavera fan) constantly disconnects from the network. Every time it is power-cycled, the device will connect and is controllable through it's App and Apple's homekit interface, but within 5 minutes it will disconnect. This behavior has persisted despite factory resetting the IOT device, the Deco M5 system, and resetting my Homekit network. Very annoying. All of my other IOT products and devices are working at this time. The fan was working with the prior firmware as intended. 

@RetiredInFl 

There were many repoted issues with the 1.2.8 with the connectivity. As far as 1.3.0 I do not believe so as we did not get word about it getting pulled. So far 1.3.1 looks to be working well.

@mloforever 

If you are having issues with just that device, get in contact with the manufacturer to see if they can find anything. As a alternative you can look to downgrade the firmware, but that can be a pain.

mloforever wrote

Unfortunately after installing the 1.3.1 update, one of my IOT devices (a Hunter Cavera fan) constantly disconnects from the network. Every time it is power-cycled, the device will connect and is controllable through it's App and Apple's homekit interface, but within 5 minutes it will disconnect. This behavior has persisted despite factory resetting the IOT device, the Deco M5 system, and resetting my Homekit network. Very annoying. All of my other IOT products and devices are working at this time. The fan was working with the prior firmware as intended. 

Same song, new verse.  I have a whole slew of products that the Deco firmware "updates" have obsoleted now.

I run a 2nd (TP-link no less) router and network to handle devices that will no longer connect to Deco. 

Each new FW version since 1.2.4, so that would be 1.2.5, a 1.2.5 beta offered me, the notorious 1.2.8, 1.3.0 that was pulled, and now a 1.3.0 beta offered me. Latest one has been the best since 1.2.4, but I still have 2 devices on my secondary network because they cannot connect.

I haven't jumped to 1.3.1 yet because after no less than 5 times having some of my devices be unable to connect, I'm just a bit gun shy.

IOT devices seem to get hit the worst on these upgrades, not sure why, or how this keeps happening over and over.

The TP-link software team must be playing fast and loose with the WIFI standards is all I can figure, and the QA department either has a completely inadequate 3rd party hardware setup, or just isn't doing their jobs.

Fast roaming and beam forming off? 

I had those problems but it all went away after disabling the 2 options 

1.3.1 is probably the way to go. No issues so far

DY-deco wrote

Fast roaming and beam forming off? 

 

I had those problems but it all went away after disabling the 2 options 

 

1.3.1 is probably the way to go. No issues so far

I would say "your mileage may vary".

With 1.2.8 and beyond I've noticed those settings stopped having an impact, which could be good or bad based on how you look at it.

I went ahead and upgraded to 1.3.1 from the 1.3.0 beta, and so far no regression, still the same 1 device won't connect (a cheap Zmodo security camera). The roaming/mesh settings have no effect, same as 1.2.8 and 1.3.0.

So 1.3.1, 2nd best release thus far. Behind 1.2.4 and a light-year ahead of 1.2.5 (which killed literally half my devices including several on Ethernet!)

Obnoxiously unless someone has a solution the TP-LINK support does not, once you upgrade to 1.2.8 (or the 1.2.7 beta I was given) you CAN'T downgrade back to 1.2.4, even with a factory reset.