@Solla-topee, it’s early days but after 48 hours of testing the 1.3.2 firmware my Deco’s seem stable. There are no more connection issues occasional buffering DNS problems or reboots.

I agree, having tested the 1.3.2 for a few days now, much more stable; this is a great improvement! thank you!

@Solla-topee I am pleased to report that the 1.3.2 version has offered me the best connection for my IoT devices than any previous one since trying it out over past couple of days. I have three BE65 V2 units functioning in AP mode with wireless backhaul in between them.

All that is missing now is offering client/network isolation for the IoT network (similar to guest one) which will be the icing on the cake.

  @Aiadi I agree ;)

Aiadi wrote

All that is missing now is offering client/network isolation for the IoT network (similar to guest one) which will be the icing on the cake.

  
Total isolation of the IoT network may not be desirable. Many IoT devices need to communicate with a hub which would sit in the main network.  For these the ideal would be some NAC rules to provide limited access between the IoT network and the hub.

You can of course isolate any client device you are concerned about. So that will work for IoT devices which only need Internet access.

I've gone ahead and installed the beta as I really want DoH & DoT and the fix for NAT loopback. I've been watching this thread for almost 4 months and an official release date still appears to be allusive. 

  @ittroll  Total isolation of the IoT network may not be desirable?! Not sure how you can make such a bold statement and ascertion when this is a bog standard feature on things UniFi, Asus, Gl.iNET...etc. I have 70+ IoT devices (including many TP-Link, Kasa and Tapo devices amongst others) and none of them have any business in accesing the main network or any of the other clients. Isolation should be the rule and clients optionally excluded from this feature should only be the exception. This is just a very basic security requirement in any half-decent networking strategy.

@Solla-topee I think I have found a bug in the latest 1.3.2 firmware...

The "Speed Limit" doesn't appear to work. I set a download speed limit of 100Mbps for my iPhone and a upload limit of 25Mbps. However, when I tun a speed test on my iPhone it reaches 1GB speeds (I have a 1GB FTTP connection).

I have randomised MAC disabled on my iPhone and the QOS settings match tthe max speeds set by my ISP.

  @WelshPaul 

How are you running your speed test? If you're running it via the Deco app, I believe that speedtest is run via the main Deco unit, and not the client.

I'd suggest trying opening your client browser and running a speedtest there, and hopefully this will produce a different result.

@ToneAU I'm running the speed test via my iPhone's web browser and not the Deco itself. It's set a download speed of 100Mbps and 25Mbps up. Speed test returns almost 1Gbps. It definitely doesn't work!