Rog Rapture GT-AX6000: IoT devices continuosly disconnected

[kaiserxol]

Hello everyone,
First post here, but I've read a lot of this forum over the last 3 years.

I'm having a problem with my Rog Rapture GT-AX6000 (latest Merlin firmware 3004.388.8_2, but also with previous firmware the behaviour was the same), with some of my IoT devices: Amazon Blink Cam (2 mini and one external with sync module 2) and a Somfy-Tahoma for all my shutters. I've searched a lot here, on Reddit and Google, but I'm stuck with my problems and out of ideas.

Behaviour: after a few hours or days (random), these devices stop working simultaneously. Rebooting the devices doesn't work, rebooting the router brings them back to normal for a while, but after hours or days they disconnect again. These devices are ONLY connected to a 2.4Ghz network, but other devices on both 2.4Ghz and 5Ghz work fine: 4 laptops, Brother printer, 3 smartphones, ipad, Raspberry, 3 Amazon Echo Dot, 2 Meross smart plugs, 2 Tapo smart plugs, Philips Hue lights and switch, Marshall Woburn, Denon amplifier... everything works fine. My Asus was configured as a router in cascade, but I've also tried changing it to just AP to simplify my network. I've also created a guest network dedicated to these devices, using #1 guest, #2 guest and #3 guest, but the problem persists. I'm using Cloudfare DNS 1.1.1.1 and 1.0.0.1. Amazon Sync Module 2 and a camera are quite close to the router, so it can't be a signal problem. I've disabled all wifi on my main ISP router.

I've found some interesting logs, but searching about it I've only found some posts here that ONLY relate to guest network and some problem with intranet access, that's not my case (I think, but please correct me if I'm wrong) as the problem is also present with standard 2.4 Ghz ethernet with all standard access. I've read about YazFi, but I think it's useless for my scenario.

Here is the log:

Sep 11 21:18:36 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 74:AB:93:F3:BE:93, status: 0, reason: Unspecified reason (1), rssi:-46
Sep 11 21:18:36 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 74:AB:93:F3:BE:93, status: Successful (0), rssi:-46
Sep 11 21:18:36 wlceventd: wlceventd_proc_event(695): wl0.1: ReAssoc 74:AB:93:F3:BE:93, status: Successful (0), rssi:-46
Sep 11 21:18:36 hostapd: wl0.1: STA 74:ab:93:f3:be:93 IEEE 802.11: associated
Sep 11 21:18:36 hostapd: wl0.1: STA 0c:43:f9:e2:f4:d8 RADIUS: starting accounting session 3FF1479591B5258F
Sep 11 21:18:36 hostapd: wl0.1: STA 0c:43:f9:e2:f4:d8 WPA: pairwise key handshake completed (RSN)
Sep 11 21:18:36 hostapd: wl0.1: STA 74:ab:93:f3:be:93 RADIUS: starting accounting session E8BCF4139C8E08ED
Sep 11 21:18:36 hostapd: wl0.1: STA 74:ab:93:f3:be:93 WPA: pairwise key handshake completed (RSN)
Sep 11 21:18:39 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind 94:3A:91:D7:83:3C, status: 0, reason: Unspecified reason (1), rssi:0
Sep 11 21:18:39 wlceventd: wlceventd_proc_event(685): eth6: Auth 94:3A:91:D7:83:3C, status: Successful (0), rssi:0
Sep 11 21:18:39 wlceventd: wlceventd_proc_event(695): eth6: ReAssoc 94:3A:91:D7:83:3C, status: Successful (0), rssi:-63
Sep 11 21:18:39 hostapd: eth6: STA 94:3a:91:d7:83:3c IEEE 802.11: associated
Sep 11 21:18:39 hostapd: eth6: STA 94:3a:91:d7:83:3c RADIUS: starting accounting session B974614AF90DC404
Sep 11 21:18:39 hostapd: eth6: STA 94:3a:91:d7:83:3c WPA: pairwise key handshake completed (RSN)
Sep 11 21:18:40 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 74:AB:93:F3:BE:93, status: 0, reason: Unspecified reason (1), rssi:-45
Sep 11 21:18:40 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 74:AB:93:F3:BE:93, status: Successful (0), rssi:-45
Sep 11 21:18:40 wlceventd: wlceventd_proc_event(695): wl0.1: ReAssoc 74:AB:93:F3:BE:93, status: Successful (0), rssi:-45
Sep 11 21:18:40 hostapd: wl0.1: STA 74:ab:93:f3:be:93 IEEE 802.11: associated
Sep 11 21:18:40 hostapd: wl0.1: STA 74:ab:93:f3:be:93 RADIUS: starting accounting session E8BCF4139C8E08ED
Sep 11 21:18:40 hostapd: wl0.1: STA 74:ab:93:f3:be:93 WPA: pairwise key handshake completed (RSN)
Sep 11 21:18:40 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 0C:43:F9:E2:F4:D8, status: 0, reason: Unspecified reason (1), rssi:0
Sep 11 21:18:40 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 0C:43:F9:E2:F4:D8, status: Successful (0), rssi:0
Sep 11 21:18:40 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 0C:43:F9:E2:F4:D8, status: Successful (0), rssi:-51
Sep 11 21:18:40 hostapd: wl0.1: STA 0c:43:f9:e2:f4:d8 IEEE 802.11: associated
Sep 11 21:18:40 hostapd: wl0.1: STA 0c:43:f9:e2:f4:d8 RADIUS: starting accounting session 3FF1479591B5258F
Sep 11 21:18:40 hostapd: wl0.1: STA 0c:43:f9:e2:f4:d8 WPA: pairwise key handshake completed (RSN)

Does anyone have any ideas as to what my problem might be or what test I can do now?
Thank you

 

[jaizan]

I hope you get some answers !
I've noticed my previously reliable ESP8266 devices have been disconnecting ever since I switched to the GT-AX6000.

Internet searches haven't found a solution for me. There's a suggestion that it's a known issue.
I've tried various settings.

I'm now contacting Asus customer support. I I don't find a solution, the router is going back under warranty.

 

[kaiserxol]

I hope so, I love this router :-(

Are you running stock or Merlin's firmware? I'm also thinking of flashing stock firmware and test it again, if it makes sense..

 

[fryedchikin]

Try setting Wireless Mode to Legacy if you haven't tested this yet.

 

[Kingp1n]

I was having similar issues with a Dyson device that would always disconnect on 2.4. Try the following and see it makes any improvements:

On the 2.4ghz:

Under the Wireless tab --> Professional tab

Disable the following:

1. Airtime Fairness
2. Multi-user MIMO
3. Universal Beamforming
4. Reboot router and disconnect/turn off for 30 sec the affected devices

If this doesn't work go ahead and disable 802.11ax MU-MIMO as well.

Hope this helps.

 

[Tech9]

Does anyone have any ideas

Yes, try this first:

[Wireless Router] How to improve compatibility of IoT device with ASUS WiFi 6(802.11 ax) router? | Official Support | ASUS Global

...and perhaps this after:

AX86U Check my settings please

Can anyone chime in on these settings AX86U Merlin 388.1_0

www.snbforums.com

 

[Ripshod]

Just disable 802.11ax/wifi6 on the 2.4 band.

 

[kaiserxol]

What a wonderful community, thanks to everyone who is trying to support me, much appreciated!

I've made a few changes:
@Kingp1n : I've disabled multi-user MIMO, the other settings were already disabled.

@Tech9 : I’ve configured the wifi following the Asus suggestions for IoT and the sub post that you have shared, I’ve only keep Channel Bandwidth to 20/40 Mhz and the Group Key Rotation Interval to 3600. I'll change those 2 settings too if the problem persists.

@fryedchikin : If the above changes don't work, I'll switch to legacy as well.

@Ripshod : 802.11ax/wifi6 on the 2.4 band is also disabled.

Thanks to all, I'll update you...hopefully in 14 days without any problems in the meantime, fingers crossed!

 

[Tech9]

Leave Key Rotation to default 3600 for now, but lock channels and bandwidth. Devices will be disconnected on Auto changes and some may not reconnect. This is the most common issue. Also look at signal levels in Wireless Log . Devices below -80dBm won't have stable connection.

 

[kaiserxol]

Leave Key Rotation to default 3600 for now, but lock channels and bandwidth. Devices will be disconnected on Auto changes and some may not reconnect. This is the most common issue. Also look at signal levels in Wireless Log . Devices below -80dBm won't have stable connection.

Ok, thanks, I've changed that setting now too.

 

[jaizan]

Ok, thanks, I've changed that setting now too.

I look forward to hearing your result.
As far as I can tell, I've tried most of these settings on my GT-AX6000 & it does not fix my problem with ESP8266 devices on 2.4 GHz.

 

[128bit]

selecting "legacy" made a huge difference for me some years back on 2 IoT 802.11n weather devices. also, if you have no b/g devices, you can leave that protection unchecked. in doing so, i got a slightly faster speed test result.

 

[jaizan]

I've set it to 802.11.n and again it was unreliable. Run for a while then dropped 1 out of 2 devices.
On a router reboot, neither 2.4 GHz device would reconnect.

I think I've tried all the ideas from the multiple threads on Asus AX 2.4 GHz problems.

So I have now removed the Asus GT-AX6000 router & have boxed it up for return to Amazon, as recommended by Asus.

 

[jaizan]

Here's the data. On the 15th of Sept, I switched from the Asus router back to the Vodafone.
I also increased the delay time on one of the 4 ESP devices, to cut the total message count to around 6960 per day.
Just look at the consistency with the Vodafone router. Whereas the Asus had lots of dropped messages almost every day.

 

[Tech9]

Share the results with the eventual replacement router, please. Asus or other brand.

 

[jaizan]

Share the results with the eventual replacement router, please. Asus or other brand.

I will do, IF there is an eventual replacement router.
Currently, the Vodafone router has kept stable 2.4 GHz connections since I switched back to it. 11 days.

As it stands, I haven't identified an obvious replacement & I'm busy on other things, so the next router is on hold.

Given the paucity of good non-Asus candidates, I don't rule out eventually trying a different Asus model. Next time around, I won't be wasting time trying all the settings changes. Either 2.4 GHz is stable immediately or it goes straight back to the retailer.

 

[kaiserxol]

Hello everyone,
I'm here to thank you all. After 2 weeks, all my problems with my wifi are solved. All devices are online without any problem, no issues at all.

Thank you all for your very very valuable help!!

 

[RMinNJ]

Interested in this thread now... second time my Mysa Threromstats dropped off the IoT network and restarting them did not help.. Saw constant dhcp requests from them.. Had to restart the IoT network and they reconnected. Other devces on the IoT network were fine...just Mysas .

 

[Tech9]

Either 2.4 GHz is stable immediately or it goes straight back to the retailer.

Wi-Fi settings are there for a reason. Most routers come on Auto, not ideal for everyone. Asus default settings are not the best in all cases either and the GUI exposes too many settings adding to the confusion.

 

[jaizan]

Wi-Fi settings are there for a reason. Most routers come on Auto, not ideal for everyone. Asus default settings are not the best in all cases either and the GUI exposes too many settings adding to the confusion.

A fair observation, however:
1 On the now returned router, I've already tried every single setting recommendation I could find to fix the 2.4 Ghz connection issue. That included searching the many threads on Asus 2.4 GHz issues & trying every idea there.
2 It just works out of the box with the ISP router.

Having tried many different settings on the first Asus router, I'm not going to repeat that process. If I buy another Asus router, either the 2.4 GHz works straight away, or it goes back.