Early Access Deco BE85_1.1.3 New firmware with Optimized System Stability and Network Performance

This Article Applied to
Deco BE85_V1/V2
Modifications and Bug Fixes
- Added the HomeShield APP block features.
- Added more supported Kasa/Tapo smart devices under Smart Home.
- Improved stability and security of the system.
- Improved the QoS features.
- Fixed the issue that the NordVPN client doesn't work in some cases.
- Fixed the issue that the 240MHz channel width option disappears in some cases.
- Fixed the issue that the IPTV client connected to the satellite Deco couldn't play multicast streams in some cases.
- Fixed the issue that the wireless channel or channel width couldn't be modified in some cases.
- Fixed the issue that the main Deco incorrectly identified the Internet port in some cases.
Download Link:
Deco BE85_V1/V2 | Deco BE85 1.2.0 Enhanced Mesh Backhaul Stability and Device Roaming Experience |
Related Articles
Deco BE65_V1_1.1.0 Supported WireGuard VPN, Channel Selection and Matter
Deco BE65_V2_1.1.4 Further Optimized Client Connection Status and Network Stability
Deco BE85_1.1.2 New firmware with Optimized System Stability and Network Performance
Deco BE95_1.1.0 Added WireGuard VPN, Channel Selection And Matter
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@raven-au What model Sony TVs are they?
- Copy Link
- Report Inappropriate Content
David-TP wrote
Hi, does your Sony TVs support 5 GHz? Would there be any error message when they can't connect to the main Network?
Compared with the main WiFi network, I wonder if the smart TVs might prefer the 2.4GHz-only IoT network.
@David-TP none of my Sony TVs have never preferred the 2.4Ghz and I have had many over the years, they always connect to the 5GHz band.
Both of the SSIDs (main and IoT) provide both the 2.4 and 5GHz bands on the BE85 (and the TVs connected fine before installing 1.1.3) and quite a few other routers,
including two other WiFi 7 brand routers and Archer WiFi 7 routers.
- Copy Link
- Report Inappropriate Content
@XWEBNetwork there are 2 x A90Ks, one connects and one not.
3 x A80Ks can't remember but one off these wouldn't connect.
1 x X80J and 1 x X90K neither would connect.
- Copy Link
- Report Inappropriate Content
Edit : this seems normal... When you choose "set mode for all Decos", nothing says that the BE25 do not support Smart Eco. When you choose to set the mode for each Deco individually, you get the list of Deco with it specified that the BE25 do not support Eco mode. Too bad, I thought it would disable the 5 GHz of the BE25
Hi
There seems to be a problem with the eco mode on my setup (2 BE85 (the main one with fiber optics and the second one WiFi) and 2 BE25 (Ethernet, using a switch between the main BE85 and the two BE25)
When I activate total standby mode (only the 2.4 GHz band is active), the 5 GHz band remains active on the BE25 (MLO network or 2.4/5 GHz network)
Example : my PC (or TV) has deco auto conf and preferred band auto conf, on the MLO network. It connects to the BE25 at 5 GHz. If I force it to the other BE25, it's also 5 GHz. If I force it to the main BE85, it doesn't even connect to the MLO network (it should only be on 2.4 GHz). It connects fine to the non-MLO network at 2.4 GHz.
I also have equipment in total eco standby mode which no longer appears (not in offline mode either) even though it is accessible (example: Tapo P115)
I can't say if it was the same on the previous firmware, I hadn't tested the eco mode before today...
Sorry for my english, I'm french
Thanks
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the update. Deco BE25 is also planned to support ECO Mode_V2, like other WiFi 7 models. You can pay attention to the official firmware release notes.
Best regards.
- Copy Link
- Report Inappropriate Content
Edit : it's seems to be a bug with MLO network and IoT network... I just tested it with my WiFi 6 PC (6 only, not 6E) on the normal network without MLO mesh off, it switches to the selected preferred Deco without even disconnecting/reconnecting afer a few seconds. On 6GHz network, OK too. Same with my Samsung Fold 5. Same with my Archer TBE400UH.
Another strange thing, my Fold 5 still appears connected on the Deco app even though I have disabled WiFi on it (tested for 3 minutes)
With the guest network (2.4/5GHz network and 6GHz network), it's impossible to choose a favorite Deco. Why anyway ?
Thanks.
Hi,
BE85_1.1.3 on 2 BE85 (one main, second WiFi) and 2 BE25 (BE25_V1_1.0.17) backhaul ethernet with switch keepLiNK "KP-9000-6XHML-X2" (IEEE 1905.1 OK)
--> Preferred Deco don't work. Same with WiFi 7 client (Archer TBE400UH, so not only with old equipment with old WiFi standard). Tested on MLO network and IoT. For the IoT network, it seems that the problem is known... (see here on reddit)
The Deco app says that the client will only connect to te selected Deco, this is not the case.
I know that in mesh systems there is a choice of the best "AP" according to different criteria, but here it does not work at all on any of my clients and the Deco application clearly says that it will force the client on the selected "AP". Also, when I restart a Deco, the clients switch to another Deco (logical), but once the Deco is restarted, the clients remain on the other Deco. Is it not possible to make the Deco system disconnect the clients so that they reconnect to the correct Deco ?
Thanks.
- Copy Link
- Report Inappropriate Content

Hi, thank you very much for your time and patience.
The 1.1.3 beta for Deco BE85 and 1.0.17 for Deco BE25 are meant to improve the Mesh roaming performance. However, it didn't seem helpful for your case.
Apart from the WiFi 6 PC/Samsung Fold 5/Archer TBE400UH, can I have other model numbers of the smart home/network devices that failed to connect to the closet Deco when connected to the MLO or IOT networks?
-If they can't connect to the closest Deco, would they always tend to connect to the main Deco BE85?
By the way, can you constantly reproduce this issue?
Wait for your reply.
Best regards.
- Copy Link
- Report Inappropriate Content
Hi David
This morning I tested with 2 Redmi Pad Pro tablet and strangely it worked every time without needing to disconnect/reconnect the WiFi on the tablets. However, the switch seems a little longer on the MLO network compared to the classic network (or you have to disconnect/reconnect the client for an immediate effect). Yesterday it didn't work at all for the MLO network I just updated the Deco application this morning (beta 3.9.42). Could this have been fixed just by updating the Deco app ?
It also works on an Asus PC with a B560-PLUS WIFI motherboard (Intel WiFi 6 AX201) and 1 laptop equipped with Intel AX201 too. I'm getting an Archer TBE550E at the end of the week, I'll test it with it...
It seems to be working on the MLO network now ! The only thing is that when I switch back to automatic, I have the impression that it doesn't pick up the best Deco on its own... It remains on the last selected Deco...
Fold5 : need to disconnect/reconnect the WiFi (or it takes much longer, I didn't really wait...). And above all, moving to the preferred Deco doesn't work if I leave the preferred frequency in Automatic mode. If I force it to 5GHz or 2.4GHz, it switches fine, after manually disconnecting/reconnecting the Fold's WiFi. It seems that the Fold prefers to keep the Deco that emits 6GHz...
However, I still have a problem with the Archer TBE400UH. It only connects to the nearest Deco (BE85 main). I will have to test by moving the Archer TBE further away... And, another problem, the Archer TBE connects perfectly well to the MLO network, but, if I force a frequency in the Deco application, it can no longer connect (6GHz, 5GHz, and 2.4GHz), it must be left in automatic. There is no real point in forcing the frequency, but this is not normal behavior... It looks more like a problem with the Archer USB
"By the way, can you constantly reproduce this issue?" --> hard to say, it didn't work at all yesterday and today it seems to work except for example if I leave the 6GHz forced in the Deco application for the Fold, or for the TBE400UH...
IoT Network (forcing still doesn't work) :
- Tapo C220 (2 cam tested)
- Tapo P115 (4 smart plug)
- Meross ms600 (1 smart presence sensor)
- Meross mss310 (3 smart plug)
- Meross mss315 (1 smart plug)
- Meross mss210 (1 smart plug)
- Meross mss305 (2 smart plug)
- Meross msh300hk hub
- Tapo H100 hub (2 hub)
- Google Nest Mini
- Delonghi PrimaDonna Soul
"By the way, can you constantly reproduce this issue?" --> yes for the IoT network.
I hope my English is not too bad
Have a good day
- Copy Link
- Report Inappropriate Content
Thanks for the feedback.
I'll escalate the case to the senior engineers and check whether they have any other suggestions about the "Connection Preference" issue over IOT Network.
Could you please give an update to #TKID250514495 so that I know you have received the email.
Best regards.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content

Information
Helpful: 1
Views: 23289
Replies: 126
Voters 1
