@TP-Link 

Do you some kind of ETA? Are we expecting it to be released in days? Weeks? Months?

@TP-Link since the decos are now breaking people's networks, are you prepared to offer refunds? As a result of your negligence, the Deco line of products are now defective as they no longer serve their primary purpose. 

@TP-Link  to be clear: you don't need to say thank you, almost no one here is giving you any understanding or support. You are simple thieves and scammers. Solving the problem is as easy as commenting on the source code some lines of the "smart dhcp" and upload the new compiled firmware for updating the decos.
 

@TP-Link Ya, there's no way that this should take that long to implement! I've told lots of people about this "feature" and lots of people haven't bought TP-Link because of it. This should definitely be of higher priority. I can guarantee that I've cost TP-Link more in sales because of this than it would have cost them to get their programmer to add this in.

@Darkstar 

To be fair, the majority of people affected are those who run what can hardly be called "your average home network," which is just an ISP router and bunch of wireless devices accessing Internet individually.

It is going to be small vocal minority. Emphasis on small. I suspect Deco software development project manager(s) prioritize it considering this.

I agree TP-Link should fix this but also accept that "regular people" (people not running their own modem, router, etc.) won't be impacted by this.

Until a fix is available one mitigation is to set up your home network subnetting such that even in the event the Deco decides to start serving DHCP, your traffic can still be routed to the internet. This isn't ideal, as things like DNS names for internal hosts won't work, but it's better than taking everything offline. Some ways back in the thread I have a post with details about how I did this. I will say I've had the Deco since November and other than my initial setup nightmare, everything has been working OK.

@Alexandre. sorry, but I disagree.

If someone has a "regular home network" will be affected too but the repairing method consisting of unplugging and plugging is enough in many cases.

Unfortunately, the industry made the "unplug and replug" a standard repair and maintenance procedure, despite it's unacceptable.
The people here in this thread don't want or simply can't restart the system this way and this makes a difference, that makes a huge difference.