GTE-AXE11000 Dropping smart plugs

[Ironcobra80]

I am having constant issues with my asus router dropping my tp-link smart plugs. It seems looking at the logs that its resetting them every couple of minutes which is causing problems when I try to control them with my echo devices. I have attached a section of my logs and the whole thing over a couple of days showing the constant resets. Any ideas where to start. I did add all 3 of the plugs to the dhcp list giving them static ip addresses.

Spoiler: logs

Jul 20 11:59:37 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-62
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 11:59:37 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 11:59:38 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jul 20 12:00:13 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:0
Jul 20 12:00:13 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-75
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-63
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 12:00:15 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-65
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-66
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1F:AB, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:0
Jul 20 12:00:20 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1F:AB, status: Successful (0), rssi:-66
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-74
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:18:76, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:18:76, status: Successful (0), rssi:0
Jul 20 12:00:25 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:18:76, status: Successful (0), rssi:-73
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-77
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 70:4F:57:9C:79:0E, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 70:4F:57:9C:79:0E, status: Successful (0), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(491): eth6: Deauth_ind 40:3F:8C:E8:1C:02, status: 0, reason: Unspecified reason (1), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(527): eth6: Auth 40:3F:8C:E8:1C:02, status: Successful (0), rssi:0
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 40:3F:8C:E8:1C:02, status: Successful (0), rssi:-73
Jul 20 12:00:55 wlceventd: wlceventd_proc_event(556): eth6: Assoc 70:4F:57:9C:79:0E, status: Successful (0), rssi:-67

 

[ColinTaylor]

Try disabling Smart Connect in the Wireless settings if you haven't already done so.

 

[Ironcobra80]

Try disabling Smart Connect in the Wireless settings if you haven't already done so.

I do have tri band smart connect on, so I should separate the networks out?

 

[ColinTaylor]

I do have tri band smart connect on, so I should separate the networks out?

It's worth a try. I've never used Smart Connect myself but some people have reported problems with it enabled.

 

[Ironcobra80]

It's worth a try. I've never used Smart Connect myself but some people have reported problems with it enabled.

Factory reset and turned off smart connect with no change still disconnecting every couple of minutes.

 

[thiggins]

What standard and band do the problem devices use? I'm guessing 11n 2.4 GHz.

If you have Roaming assistance enabled, try disabling it or moving the setting down to the maximum (minimum RSSI)

 

[ColinTaylor]

In addition to @thiggins suggestion compare your settings to mine. Although I don't have your devices, your router or your problem so they may not help.

 

[Ironcobra80]

What standard and band do the problem devices use? I'm guessing 11n 2.4 GHz.

If you have Roaming assistance enabled, try disabling it or moving the setting down to the maximum (minimum RSSI)

2.4, I did disable roaming assistant.

 

[sfx2000]

The TP-Link Kasa smart plugs are 2.4GHz only...

802.11n at that.

Disable Airtime Fairness on the Asus side, and things should improve with the plugs staying connected.

 

[Ironcobra80]

The TP-Link Kasa smart plugs are 2.4GHz only...

802.11n at that.

Disable Airtime Fairness on the Asus side, and things should improve with the plugs staying connected.

thats disabled by default

 

[JokerJURY]

I have the same thing with my GT-AX11000. If I go back to Version 9.0.0.4.386.41994 Beta Version or anything released before that no issue. Don't know if there is an older firmware you can find for yours that might get rid of the issue.

 

[Ironcobra80]

3.0.0.4.386_45850-gfa0c0f9 new update finally fixed this issue and the router is running perfectly now!