@David-TP 

Hi David,

For information : "Deco connection preferences not working on IoT network is not a bug, it is designed in this way by default, we are considering allowing the IoT network to use connection preferences as well. This should be release in the future, on new firmware."

I took the opportunity to suggest adding other functions :

- option to disable automatic WAN port mode on BE85 and BE25 as it is on others Deco (https://www.tp-link.com/ae/support/faq/4252)

- WiFi Access Control (currently you can block equipment, but not only allow certain clients and block all others) (https://www.tp-link.com/en/support/faq/3833)

- Internet Backup (especially hotspot backup mode) (https://www.tp-link.com/en/support/faq/4246)

- Eco mode V2 for BE25 (OK on BE85) (https://community.tp-link.com/en/home/forum/topic/667592)

- DoH/DoT would be good too but it doesn't seem like a priority to me... (https://www.tp-link.com/en/support/faq/4254)

It's crazy that the new top-of-the-range models don't have the features already added to older models...

Adding new features is fine, but waiting for what already exists to come out...

  @David-TP 

"Yes, the fixed WAN port feature should be available on Deco BE85 and BE25, it is planned but not release yet.

Wi-Fi Access Control would be available in the future.

Internet Backup is not going to be available on standard Deco modes, only available on Deco 4G/5G models (with SIM card as backup connection)

Eco Mode V2 will be available for EU customers.

DoH/DoT is planned."

  @David-TP 

preferred AP function to work under IOT network should be perfect feature for next firmware 

  @jlambert Agreed! 1000%

The top of the line models should be the priority for everything. We spent a lot of money on these things and the fact that they are so far behind on the dev cycle is wild.

jlambert wrote

  @David-TP 

 

Hi David,

 

For information : "Deco connection preferences not working on IoT network is not a bug, it is designed in this way by default, we are considering allowing the IoT network to use connection preferences as well. This should be release in the future, on new firmware."

 

I took the opportunity to suggest adding other functions :

- option to disable automatic WAN port mode on BE85 and BE25 as it is on others Deco (https://www.tp-link.com/ae/support/faq/4252)

- WiFi Access Control (currently you can block equipment, but not only allow certain clients and block all others) (https://www.tp-link.com/en/support/faq/3833)

- Internet Backup (especially hotspot backup mode) (https://www.tp-link.com/en/support/faq/4246)

- Eco mode V2 for BE25 (OK on BE85) (https://community.tp-link.com/en/home/forum/topic/667592)

- DoH/DoT would be good too but it doesn't seem like a priority to me... (https://www.tp-link.com/en/support/faq/4254)

 

It's crazy that the new top-of-the-range models don't have the features already added to older models...

Adding new features is fine, but waiting for what already exists to come out...

  @XWEBNetwork 

I 100% agree with you, the flagship models should obviously get the features first, otherwise the ones who buy them will be discouraged and when they replace their routers/access points they will simply go elsewhere, to Unifi for example where, firmware updates and features are updated/introduced regularly. 
I am impressed with the hardware on the BE85, but the lack of firmware updates does concern me. Especially with so many zero day exploits being discovered. 

  @David-TP 

Hi David

I am a Japanese who recently purchased a Deco BE85 V2.
I emailed Tpkink support and was presented with a lame firmware (v1.0.22) and have not been able to contact them since.
I could not downgrade as it is already v1.1.1.
I want to use Deco BE85 as my main router, but it has various bugs and I use it in bridge mode.
I would like to have this addressed in the new firmware.
The following is a description of the problem.
The internet connection method is v6 plus.
Main router is an Archer AX73, which does not support L2TP/IPsec VPN connections for v6 plus connections, but everything else works.
Why such an expensive router Deco BE85 does not support it is a mystery.
I translated Japanese into English at DeepL. Sorry if it's hard to read.

The firmware is 1.0.15 (version at the time of purchase) 
- VPN connection OK with L2TP/IPsec 
- Pairing OK with old wifi child device (WLI-UTX-AG300) using WPS button 
- Real-time battle of app games OK 
- PS5 APEX continuous combat NG (you must leave the room once to play again.)

Firmware is 1.1.1 (current version after update) 
・VPN connection NG with L2TP/IPsec (connection error to company VPN on windows PC) 
・Pairing NG with WPS button on old wifi child device (WLI-UTX-AG300) (Child device seems to be recognized but internet connection is not possible) 
・Real time battle of app games OK 
・PS5 APEX continuous combat unconfirmed (need to have child try).

Firmware is 1.1.2 (confirm if it is cured) 
・VPN connection NG with L2TP/IPsec (connection error to company VPN on windows PC) 
・Pairing NG with WPS button on old wifi child device (WLI-UTX-AG300) (Child device seems to be recognized but internet connection is not possible) 
・Real time battle of app games OK 
・PS5 APEX continuous combat unconfirmed (need to have child try).

Firmware is 1.1.3 (check if it is fixed) 
・VPN connection OK with L2TP/IPsec (fixed?)
・Pairing NG with WPS button on old wifi child device (WLI-UTX-AG300) (Child device seems to be recognized but internet connection is not possible) 
・Real time game NG for app game (Cannot play real time game and app freezes) 
・PS5 APEX continuous combat unconfirmed (need to have child try).

  @David-TP 

Thanks for the reply. David 

Firmware is updated to 1.1.3 at the time of operation check.
I am now back to 1.1.1 and using it in bridge mode.
Once the problem is completely resolved, I will switch to the main router and use it.
I am checking the operation of each firmware by switching to the main router.

The VPN is connected to the company's VPN (L2TP/IPsec connection method) instead of building a VPN in my environment.
Firmware 1.0.15 was able to connect, but with other firmware it was not able to connect, and now with this firmware 1.1.3 it is able to connect again, so the problem is solved.
I thought this would be useful information for other users.

App game freezes during matching in ffbe war of the visions free match.
This bug occurred only with this firmware 1.1.3.
Firmware 1.1.2 did not have this problem, so it is reasonable to assume that it went wrong with the 1.1.3 support.

I would like to pair the WLI-UTX-AG300 with the Deco BE85.
This one supports 802.11n and with firmware 1.0.15 I was able to pair and connect to the internet.

firmware 1.1.1 or later, when paired using the WPS button, the Child device side recognizes the Deco BE85, but the Deco BE85 side does not recognize the Child device.

I cannot connect to the Internet.
The Deco BE85 is recognized by the child device, but it is not registered as a client device on the Deco BE85 side.
Of course, I have tried connecting manually and the same thing happens.
With firmware 1.0.15, I was able to pair the WLI-UTX-AG300 with the Deco BE85 using the WPS button and connect to the Internet.
Since the WLI-UTX-AG300 supports 802.11n, we cannot afford not to address this bug.
I am wondering why this expensive router does not support WPS button pairing when other routers have no problem.

We would also like you to confirm the issue of PS5's APEX not being able to continuously fight.
The Archer AX73 can do continuous combat even with a v6plus connection, so not being able to do it with the Deco BE85 is a big problem.

Best regards.

  @David-TP 

Any word when this update my be officially released?  Be in preview for months now. Thanks!

  @David-TP 

Hi,

I have a Deco BE85 configured as AP mode, with version 1.1.1, it seems have a bug that WiFi upload caps at 100M when using iPhone 16 Pro or newest iPad pro, when using old ax device like M1 MacBook pro(802.11AX), it's tested fine at 600M/600M. I have seems other people reporting similar issue, sometimes the speed is ok but most of the time it's capped at 100M. (I have tested multiple times and can confirms it)

When the issues happens, I always seeing the error log like this, it seems a driver issue where the nrd having issue mapping the phy mode under AP mode:

Mon Jun 23 21:35:49 2025 daemon.err nrd[15350]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0

Mon Jun 23 21:35:49 2025 daemon.err nrd[15350]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0

Mon Jun 23 21:35:49 2025 daemon.err nrd[15350]: wlanifMapToPhyMode: Invalid PHY mode from driver: 0

Mon Jun 23 21:35:49 2025 daemon.err nrd[15350]: wlanifConvertToSingleStreamMCSIndex: Invalid PHY mode from driver: 0

M1 Macbook Pro:

iPhone 16 Pro: