Very good router setup. I was having issues with my Google supplied mesh system which is also very limited on the settings you can change. I'm on a 3Gig plan and Wifi 7 was the only option to maximize speeds, I have my gaming room setup on the complete opposite end of where my main router is and plugging in my PC and Ps5 to the ethernet of the 2nd router gives me right around 1gig speed which is great. All the connection issues I had with Google are non existent with these routers. I was able to get wifi signal across the street when helping my neighbor, although a bit slow but the signal was still there. I also setup a 2nd channel for all my smart devices and ring cameras which I know many others might not know about but definitely recommend. The networking experience can definitely be elevated if the consumer takes the time to read a little but even with just plugging it in and using it as is out the box it is still a very good network setup for most people out there. The only complaint is the price. I would only purchase these on sale and not retail, hence the reason I never see these at msrp online, everyone else also thinks they are pricey. I bought them at $599.

Very high quality router and amazing mesh WiFi setup. In the past I was using Netgear Orbi's with WiFi 6 which were great with no complaints but I wanted to upgrade to a router with faster ports and WiFi 7. I saw this Asus model and I had never tried Asus network equipment until now. I have not been disappointed one bit. Overall great area coverage and speed especially if you buy 3-4 of them. I now have wireless speeds pushing 2Gbps on my devices that have WiFi 6/6E/7 adapters. Easy to install and blazing fast performance. So far I would highly recommend the Asus ZenWiFi BT10 to anyone looking for new mesh WiFi network equipment in their home.

I had some initial concerns changing to this Asus BT10 router from a HomeKit-compatible Linksys Velop router, but it actually worked out almost as well I had hoped. When I installed the old Linksys router, I used the same WiFi SSID and password from the previous (Netgear) router, and the HomeKit devices switched over with only minor issues. This didn’t work when I tried the same thing with the Asus router. Any device I added with the Linksys router did not transfer. (With the HomeKit Linksys router, I did not have to be on only a 2.4 GHz SSID to install the IoT (internet of things) devices, which was convenient.) Only devices that were installed prior to the Linksys (and Thread devices) transferred to the Asus.I also could not install any new devices to my “Home” with the Asus. I ended up creating a new Home and reinstalling all of my devices to this new Home. I think if I had used a non-HomeKit router before the Asus, and used the same SSID/password combination, this would not have been in issue. Also, I have not switched over to the new Matter-based architecture for HomeKit when I installed the Asus.The documentation for the BT10 (and some other Asus routers) talk about creating an SSID for IoT devices on the 2.4 GHz frequency. I couldn’t find any information on how this was set up, which is partly why I had initial concerns. This actually worked really well. The BT10 lets you create SSIDs on different frequencies using the same subnet. (The default subnet was 192.168.50.1, which I changed to 192.168.1.1.)What this means is you can set up an SSID for your IoT/HomeKit devices on 2.4 GHz, and a *different* SSID for your main WiFi using 2.4/5/6 GHz, and they would all be on the same subnet (e.g., 192.168.1.x). So when I had to re-install my HomeKit devices, I just pointed my phone on the 2.4 GHz SSID and had no issues (I decided to use only the 5 and 6 GHz frequencies on my main WiFi network). No more turning the 5 GHz on and off to install devices.Being on the same subnet means I can control the devices locally on my LAN. I cannot see my HomeKit devices when on a different subnet.The Guest SSID used a different subnet (192.168.52.x was the default). Virtual LANs also seem to use a different subnet, so users on these subnets can’t see or control the HomeKit devices.A nice touch is you can list the devices by the network/SSID (i.e., Ethernet, Wireless SSIDs) they’re on using a browser interface. Normally you get the one list of wireless devices which makes it hard to distinguish all of the IoT devices. So as I added my HomeKit devices, I checked the 2.4 GHz device list so I can rename them on the list instead of using the generic manufacturer name so I can keep tabs on them. I generally used the browser interface for all of the setup instead of the iOS app. It also shows the transmission rates to each device which tells me how good the signals are to my devices outside.So far I haven’t seen any “no response” errors from the devices on the Home app with no difference in performance to the old Linksys (e.g., turning devices ON/OFF.)(I’ve since switched to the new Matter architecture for the Home app without any issues. I had to unplug/plug a few old devices, but otherwise it was fine.)(Random Router Ruminations)A couple of reasons why we switched from the Linksys was because of some WiFi dead spots where I think it was switching nodes. The WiFi would also hang for a bit while the Ethernet was totally fine. So far we have not encountered such issues with the Asus. The speeds are about what I would expect (we have no WiFi7 devices, just 6/6E, but now ready for the next upgrade cycle).I run 10Gb Ethernet among my desktops, and although I didn’t need 10Gb from the router, it’s nice knowing that it’s there if I ever get >1Gb/s internet connection. I’m not running an Ethernet backhaul between the nodes, but I get close to 1Gb Ethernet speed (~700Mb/s) with my WiFi 6 laptop next to the satellite. On an iPad Pro M2 running WiFi 6E I get over 800 Mb/s.For fun, using a 10Gbps Thunderbolt Ethernet dongle, I connected my laptop to the 10G port of the satellite node and got 1700 Mbps, almost double of gigabit Ethernet. Obviously the speed will depend on the placement of the nodes, but that’s not bad for magic wires.All of this was on the Dec 2024 firmware, which it automagically updated itself to as I was setting it up.It’s a bit expensive ($650), but that’s what I get for wanting the 10Gb ports (actually, one of the cheaper 10Gb Ethernet mesh routers, probably because it's only a tri-band wireless device). So far no issues using it with HomeKit (or Home, whatever Apple is calling it now), and it’s been pretty solid overall. I’m very happy with this router. Of the many, many routers I’ve had over the years (D-Link, Netgear, Linksys, Apple), the Apple routers have been the most stable and consistent. The Asus has been just as stable, with the benefit of newer tech and therefore faster speeds.

Recently I had some issues with my fiber line so I wanted to get a second ISP as a backup, and keep it as failover if my primary fiber line is down.So I learned about BT10 specs, learned that it supports dual WAN and thought it would be a perfect solution for me, and a nice upgrade to my current Google Nest mesh.I've had other Asus routers in the past and always loved them and I thought I couldn't go wrong with this one. So I ordered a 2-pack.Setup was fairly straightforward. Although the first time I didn't notice one is labeled as a primary.I set them up, using the same WiFi SSD and password I've used for my previous routers but found that most of my devices had a lot of issues reconnecting to the new WiFi. So I figured I'd do a full reset and give it another try in the right order. Things went better this time. Most of my devices reconnected, with the exception of a few that only work on 2.4 GHz. I did those manually, no big deal.I'm using a wired backhaul btw.One of the first things I did was update firmware.Things were running pretty good with my backup cable ISP. I set dual WAN settings to get things ready when my fiber is fixed.10G WAN/LAN2 as primary and 1G WAN/LAN1 as secondary.Failover and allow fallback. Basic failover setup that you would expect.Cloned MACs used to setup both modems in bridge mode. Everything was prepped.Then my fiber was restored and I started this journey down the dual WAN rabbit hole … boy I was in for a surprise.No matter which ISP I connected to 10G WAN/LAN2 I could not get an IP.It would always give me an error “Your ISP's DHCP does not function properly.”I tried different combinations of primary/secondary, but it was always that port.WAN/LAN1 works every time.So I gave up on that port and decided to give 10G LAN3 port a try in dual WAN mode.10G LAN3 primary and WAN/LAN1 as secondary.Finally I'm getting IPs on both ports – great. I am very hopeful.But for some reason primary shows disconnected even though it gets IP and connection works.Then I tried testing failover … it just does not work, it never switches to the secondary WAN.Tried different combinations of primary/secondary … switched ISP cables … no difference.If I ever get it to actually switch it's after me manually toggling the "Internet Connection" switch, but it never does it on its own.So one of the main features for which I bought this router simply DOES NOT WORK.There were many other bugs at this point … I was getting less than half a WAN speed on WiFi or hardwired to the primary node, even though I'm getting over 500/500 Mbps connected directly to the modem.... WAN showing disconnected forever, when it isn't … When it does show connected in the Network Map tab, it shows disconnected in the AiMesh tab.LED light on the primary node stayed red even when it has a WAN connection and secondary node is connected via backhaul. Then if I turn LED off and turn it right back on – it's white.It was really a mess at this point so I decided to give it one last chance and do one more full reset and start from scratch.This time I won't even bother with a dual WAN. Btw I ended up buying tp-link ER605 in the meantime to handle WAN failover and imagine that - works like a charm.After reset and trying to make things simpler Asus seemed to run better and more reliable.Then after 2 days, without any changes being made to it, I started noticing my phone getting disconnected and my wife's phone and laptop also started acting up, a bunch of smart plugs and switches were flashing too, like everything was getting disconnected.I ended up disabling MLO on my primary WiFi and that seems to have fixed it, for now.I blame myself for not reading more detailed reviews about this router, and dual WAN on Asus routers in general because issues seem to be going back for years.They might as well just scrap it because it's useless, it's a gimmick to check a box on the spec sheet.It's a shame, because I really wanted to love it.It might still be ok if you have a single ISP (which I understand most people will) but during this frustrating journey I've discovered way too many bugs that I'm not sure I can live with because it doesn't give me much confidence something new won't come up at the worst possible time.You will find that most YouTube reviews are very positive because they emphasize one thing – speed. Yes, it's fast when it works.And it still might work just fine for you … and they might iron out some of these bugs with future firmware updates, but with my current experience I would not recommend it.

BLOT: I sent the BT10 back after a couple of days of painful struggle. At this price, I expected to get improved performance and ease-of-use... I got no major performance improvements over Wifi 6 and many new bugs and compatibility issues.I was excited to get the ZT10 2-pack: it checks all the big features you could want from Wifi7 like MLO, 2.5Gb ports and design and price seemed much improved over earlier options. This is replacing a ~4 yr old Asus Mesh 6 setup for me which was good, but suffered from ping spikes, required 3 units to cover the house and could never handle 160GHz channels or DFS properly.What Worked: The design is good and blends in nicely. The Wi-Fi signal was strong enough where 2 units cover a 3-level home that previously required 3-nodes. The extra 2.5G port on the back was very handy for attaching a NAS or other high-speed devices. The units feel well-built.What Failed: The setup/app/firmware is extremely buggy with one of the worst config layouts. I setup my mesh as access points with ethernet backend which should be trivial to switch to (even automatic on other brands) but with this unit I had to fight it every step of the way. Changes would often take many minutes to take into effect or cascade to other mesh unit which made things extra confusing -- ex. Changing an SSID or disabling a Guest Wifi -- the old SSID is still visible or broadcasting from the other unit many minutes later. The Asus config interface is very poorly laid out -- with many settings like band steerage, MLO and Roaming Assist that often interact or conflict with each other scattered across different screens. The settings in the Phone App vs Web Interface also did not match up well either. The Mesh units would refuse to go ethernet backhaul using the 2.5G port, but insisted on the 1G port for backhaul. What a mess -- this feels like it was rushed to market with buggy firmware. I am sure the major issues will be ironed out over time, but the overall mess of a UI will likely take a major overhaul and my prior ZenWifi system quickly stopped getting updates after initial bugs settled.Beyond the bugs, what made me put this back in the box: 1) A number of 5GHz IoT devices refused to connect after many different attempts and setting up a dedicated SSID for them. 2) The 6GHz performed worse than 5GHz 160Ghz channel for me under nearly all conditions. As soon as you put a wall between you and the unit, 5GHz trumped the 6Ghz band performance by a big margin. Ping and jitter were both slightly worse on 6GHz, speed was similar under ideal conditions -- overall not worth the huge premium and compatibility issues by adding a third band.