Deco M9 Plus firmware release with similar features like M5 1.3.1

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Deco M9 Plus firmware release with similar features like M5 1.3.1

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
70 Reply
Re:Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-12 01:54:23

@JLG 

 

Hello, like @PitoGanzado said, the username and password are listed as example on the PDF file, enter your own one to give it a shot. 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#32
Options
Re:Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-12 09:16:57

@Kevin_Z where we can find the version 1.3.1? The link provided is for the version 1.3.0.

regards,

  0  
  0  
#33
Options
Re:Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-12 10:38:59

@PitoGanzado 

 

 

Pito ganzado,  rge ..31 was not released ...

  0  
  0  
#34
Options
Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-13 20:23:44

@s_rosenthaler 

I have upgraded to this version (1.3.0 Build 20190821 Rel. 54023)    It has nice features but I am getting lots of entries on the log file.   

 

Here are the entries - (Duplicates removed)

user.err csrMeshGw[4748]: MSGQ :: CsrMeshAddMsgToTxQueue idx: 0x0, Msg Len: 30, Repeat: 2
user.err csrMeshGw[4748]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 2, length : 30
user.err csrMeshGw[4748]: MSGQ :: CsrMeshGetMsgFromTxQueue curTxIndex : 0, tag count : 1, length : 30
user.err csrMeshGw[4748]: 
CsrMeshMsgQRead: qId=0 errno=42, No message of desired type!!!!
CsrMeshMuxDemuxFindModelRes : Event : 0xef01, Response Event : 0xffff
daemon.err nrd[7125]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for B8:5D:0A:A6:69:F6
daemon.notice nrd[7125]: estimatorPerformMeasurement: Do 11k measuremrent for B8:5D:0A:A6:69:F6 on channel 36 from serving BSS APId 255 ChanId 36  ESSId 0  
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -69
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -79
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -75
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 17 | RCPI: -69 | threshold RSSI: 24
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -71
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -76
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -88
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -87
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 20 | RCPI: -71 | threshold RSSI: 29
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -76
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 11 | RCPI: -76 | threshold RSSI: 25
daemon.err nrd[7125]: estimatorDot11kIterateCB: Timeout waiting for 802.11k response from B8:5D:0A:A6:69:F6
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -75
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 14 | RCPI: -75 | threshold RSSI: 27
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -78
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -81
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -66
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -68
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -66
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -73
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 23 | RCPI: -66 | threshold RSSI: 27
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -65
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -76
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -68
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 23 | RCPI: -65 | threshold RSSI: 26
authpriv.notice dropbear[3631]: Pubkey auth succeeded for 'root' with key md5 a4:25:f2:21:43:6a:61:7f:77:d4:2d:55:68:85:ce:37 from 192.168.1.233:59050
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -72
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 19 | RCPI: -69 | threshold RSSI: 26
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -67
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -70
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -69
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -80
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 19 | RCPI: -67 | threshold RSSI: 24
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 3   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:E3 rcpi: -84
daemon.err nrd[7125]: estimatorCmnHandleBeaconReportEvent: Beacon report for STA B8:5D:0A:A6:69:F6 in unexpected state 2
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -70
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -66
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -68
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 19 | RCPI: -68 | threshold RSSI: 25
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 3   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:E3 rcpi: -83
authpriv.notice dropbear[3849]: Pubkey auth succeeded for 'root' with key md5 a4:25:f2:21:43:6a:61:7f:77:d4:2d:55:68:85:ce:37 from 192.168.1.233:59052
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -63
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -71
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -74
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 24 | RCPI: -63 | threshold RSSI: 25
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -78
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -64
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 23 | RCPI: -64 | threshold RSSI: 25
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 1   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1D:0B rcpi: -69
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -60
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -82
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 24 | RCPI: -60 | threshold RSSI: 22
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -76
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 21 | RCPI: -64 | threshold RSSI: 23
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -83
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -77
daemon.err uhttpd[3362]: iptables: No chain/target/match by that name.
daemon.err uhttpd[3362]: iptables v1.4.21: Couldn't load target `domain_login_rule':No such file or directory
daemon.err uhttpd[3362]: 
daemon.err uhttpd[3362]: Try `iptables -h' or 'iptables --help' for more information.
user.emerg syslog: tp215,22[8660]:
authpriv.notice dropbear[11765]: Pubkey auth succeeded for 'root' with key md5 a4:25:f2:21:43:6a:61:7f:77:d4:2d:55:68:85:ce:37 from 192.168.1.227:34964
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 255 ChanId 36  ESSId 0   rcpi: -70
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 3   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:E3 rcpi: -88
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -81
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 15 | RCPI: -70 | threshold RSSI: 23
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -88
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 2   ChanId 36  ESSId 0  bssid 6E:FF:7B:AE:3C:2D rcpi: -86
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -80
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 17 | RCPI: -70 | threshold RSSI: 25
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 3   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:E3 rcpi: -87
daemon.notice nrd[7125]: stadbEntry_modifyTriggerThreshold: For client B8:5D:0A:A6:69:F6 RSSI: 19 | RCPI: -71 | threshold RSSI: 28
daemon.notice nrd[7125]: wlanifBSteerEventsHandleBeaconReport: Beacon report from B8:5D:0A:A6:69:F6: APId 0   ChanId 36  ESSId 0  bssid 68:FF:7B:7E:1C:D3 rcpi: -77
  0  
  0  
#35
Options
Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-13 20:36:06

@s_rosenthaler 

I tried to revert to the old firmware and I can't see how to do this......the loader supplied with 1.30 does not work with the old firmware and the web page also does not work

 

Any suggestions?

  0  
  0  
#36
Options
Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-14 17:38:27

Hey there,

 

I'd like to say that there are also some people out there that care for stability, so please take your time with that upgrade ;-)

 

From the feature set, I'd be happy from the broader support for zigbee devices, integration with home-assistant would be simply awesome.

 

Cheers!

  1  
  1  
#37
Options
Re:Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-14 17:56:45

@Kevin_Z   Can you advise how we can 'undo' this and revert to the production firmware?   See posts of logs with errors

  0  
  0  
#38
Options
Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-15 06:23:42

@Davec1001 

 

Hello, from the system log you provided, it indicates that the Apple device has weak network connection with Deco. You can forget the network on this device and reconnect to the Deco; and does it affect the actual performance? Is there any specific symptom? 

 

For the firmware 1.3.1, the firmware versioin does not always simultaneous released, and the number is different. 

 

For the official firmware for Deco M9 plus, it is coming soon. 

 

And once you updated to 1.3.0 or above, we need use the firmware recovery to flash back the original firmware. 

 

Good day. 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#39
Options
Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-23 08:00:26

@Kevin_Z Hello again. Sorry but the beta firmware from this forum thread 1.30 is very unstable. The Deco units drops the connection to our MacBoos every few minutes for a second or two. Also the certificate for the Web GUI has been revoked. When can we expect a public release? Soon, seems to be a very stretchable sentence at TP-Link. If you offer different products which can be combined together the firmware development should be focused to release features at the same time. For example a customer of mine uses M5 together with M3Ws. The M5s offer the functionallty to see which clients are connected to which mesh point, the M3W doesn't. This all feels very half baked.

  0  
  0  
#40
Options
Re:Deco M9 Plus firmware release with similar features like M5 1.3.1
2019-10-24 07:15:48

@s_rosenthaler 

 

Thanks for your updates. Sorry for the inconvenience caused here.   We pushed the product engineer again and make them release the firmware as soon as possible,

 

Please wait for a while for the updates. 

 

Thanks for your support in advance, and have a good day. 

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#41
Options