@Kev7312 If you are referring to the coverage signature (red circle) for the individual APs that used to be shown on the map in the old software, I agree it should be put back in. 

I have the same issue. I really need the coverage estimator to help ball park the signal strength I need to cover areas. Can't get the EAP-225 icons to stay put. I get them all in the correct place and the next time I open the map they're all stacked on top of each other in the top left corner of the map.

LV1, Yes, the heat mapping feature was very useful to ballpark coverage for new and additional locations without the need to rely on third party tools. Invariably all of which bears additional cost.

My motivation to upgrade to SDN was to leverage the new ax speed AP products and to prepare to leverage the new routing and switching products too. I just was unaware that the SDN feature broke the older critical features and dashboarding (no chart split between SSID's, heat mapping..etc).

Given that TP-Link has not to date released ANY new SDN products for I think a year since advertising "comming soon" in my country, that is was not worth the loss and I have sucessfully downgraded back to pre-sdn version 1.2.3 Build 20200430 Rel 52621 on my OC200 and corresponding versions 2.4.0 xxx on my eap 225, 225 outdoor and eap245 v3 products.

I recommend mamuallu downloading the older firmware versions from tp-link and manually "upgrading" using the file method under the firmware upgrade of each product.

First "forget" each AP on your controller. Then downgrade the OC 200 , then manually downgrade each AP directly, then adopt each AP back to the OC200 controller.

If your network is live and you don't want interruptions then setup a second OC200 with WLAN, SSID etc. with the older firmware then as you forget each AP, manually downgrade each AP , and adopt them to the OC200 running the older firmware one at a time.

This will transition your network while it is live.

I can confirm that the downgrade does not brick the products.

I am just thankful that tp link still allows this method, however as a precaution make sure you have a copy of all the firmwares for your product just in case tp link closes this door to force sdn adoption and do it sooner rather than later.

Tp-link updates have always been reliable and fairly bug free, however in this case the features broken when migrating to SDN are just not acceptable for me to move right now and especially if they have not released any new products supporting sdn to market yet.

Same issues have.

When are they will be fixed

Any idea if the coverage feature is coming back? My daughter and the X are building 2 houses and associated structures on 3 acres of land and I'm on the hook for the design and install. Daughter wants the whole thing covered and while I can wing it.  For those with X wives I don't have to explain why I'd rather not take that approach.

@JFND  my only suggestion , until such time as the heatmap is fixed on 1.7x is to downgrade to 1.2.x, complete your design and heat mapping, then if SDN is a big win for you (although SDN products are still not available in my country) upgrade back to 1.7x and wait out the fix from tp-link.

@Kev7312 

Kev7312 wrote

@JFND  my only suggestion , until such time as the heatmap is fixed on 1.7x is to downgrade to 1.2.x, complete your design and heat mapping, then if SDN is a big win for you (although SDN products are still not available in my country) upgrade back to 1.7x and wait out the fix from tp-link.

Thanks for your reply Kev.

That is what I had figured I'd wind up having to do.  In one way I'm lucky.  They were going to build 6 months ago but had to postpone construction and I believe the OC200 I purchased then may 1.2x on it.  

@JFND OC200 can be upgraded and downgrade between 1.7x and 1.2x without issues.