@David-TP 

( 1. This firmware CAN'T be downgraded to the previous 1.5.6 version. )

Some people already downgraded the firmware to 1.5.6 due to abandoned beta program for M9+ and I wish to do this too, but how?

If it's an official method, why you guys put this note on the first place on the main thread? 

  @MarvinZH for me, all I had to do was downgrade and they reconnected, but the one I didn't have connected to ethernet did need a reset from the button, and needed to be readded to the network before it worked :o

  @MarvinZH I downgraded due to instability issues, link is one of the earlier pages, I'd recommend using a laptop as it can be easier to set up to reset all one by one 

  @David-TP I still have the speed drop issue. Downgrading to the previous firmware is not possible. When will there be a solution?

  @Frankie_G77 

Stick with 1.5.6 or, please stop using TP-LINK shizzle.

Also have issues with download speed since installing this firmware. Basically dropped around 40%

  @xQuantum  @David-TP 

Please keep in mind that TP-Link doesn't care about his customers.

They are proud of launching new products every week, but don't serve their customers. 

It's a money making machine without customer centricity. So, please stay away from TP-LINK 

  @David-TP 

Hi David,

 This is a low priority post :-).

 I have an instance of Home Assistant (Home automation software) running on my network. It has a plug-in that interrogates UPnP devices for any information.they can supply and displays it prettily for me :-). With the v1.60 firmware, it discovers our M9+, grabs the initial upnp schema, but then doesn't pick up anything else. There's any error logged on the M9+ every time it makes a poll;

Fri Nov 25 04:33:32 2022 daemon.notice miniupnpd[22625]: SoapMethod: GetStatusInfo"
Content-Type: text/xml; charset="utf-8"
Accept: */*
Accept-Encoding: gzip, deflate
Content-Length: 267
<?xml version="1.0"?><s:Envelope s:encodingStyle="[schema URL that the forum editor can't handle]" xmlns:s="[schema URL that the forum editor can't handle]"><s:Body><u:GetStatusInfo xmlns:u="urn:schemas-upnp-org:service:WANIPConnection:1"></u:GetStatusInfo></s:Body></s:Envelope>: illegal url /oonil/ctl/IPConn

Am i safe to presume the miniupnp setup is still a "work in progress" (ie the URLs are yet to be implemented) or should I do a bit more diagnosis?

Update 01  - I've reset the plug-in a few times and it now appears to mostly work. It's just that specific part of the schema that's not implemented/working yet. As it's just a simple boolean flag indicating WAN connection status, I'm treating it as cosmetic and ignoring it :-).

Regards,

Keith