Problem With Single Device on my GS-AX3000

[dwp]

For the most part, my GS-AX3000 is doing the job. But for the last several days, I have been having trouble with a single device. It connects on the 2.4 GHz wifi and seems fine. But it doesn't last long - maybe a couple minutes. Then it drops and re-connects. I can watch the device in the connected devices page and see the time connected reach somewhat less than 2 minutes and then drop to 0 and start counting again. The odd thing is that this has not always been the case. I am not quite sure what, if anything, may have changed to cause this. When it is connected, the connected devices page shows 3 bars - not unlike other devices located nearby that are having no problems at all.

In an effort to try and isolate the cause, I first replaced the power supply to the device thinking it may suddenly be under-powered. That made no difference. Even though signal strength did not appear to the issue when looking at the connected devices page, I then installed an old Asus RT-N10 configured as a 2.4 GHz repeater using its stock firmware in a location nearby. Interestingly, this seemed to make a big improvement for this device. But overnight after doing this, the repeater's presence seemed to totally hose up the rest of my 2.4 GHz LAN. As soon as I removed the RT-N10 repeater, the rest of the 2.4 GHz LAN returned rapidly to normal and then this device started up this same problem again.

When I look at the log, it is full of entries like those below. The device ending in XX:YY is the one behaving so strangely. I really do not know what this means or what causes it. I cannot tell if the issue is on the router or the device. Can anyone suggest? Thanks

Feb 4 08:05:03 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Feb 4 08:05:08 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:05:08 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:06:15 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 4 08:06:15 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:06:15 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 4 08:06:20 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:06:20 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:07:27 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 4 08:07:27 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:07:27 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 4 08:07:32 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:07:32 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:08:39 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 4 08:08:39 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:08:39 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:08:39 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Feb 4 08:08:44 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:08:44 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-63
Feb 4 08:09:47 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Feb 4 08:09:47 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:09:47 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:09:47 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-64
Feb 4 08:09:52 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:09:56 wlceventd: wlceventd_proc_event(491): eth5: Deauth_ind 70:03:9F:9A:XX:YY, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Feb 4 08:09:56 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:09:56 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-64
Feb 4 08:10:14 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 70:03:9F:9A:XX:YY, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 4 08:10:14 wlceventd: wlceventd_proc_event(508): eth5: Disassoc 70:03:9F:9A:XX:YY, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Feb 4 08:10:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 70:03:9F:9A:XX:YY, status: Successful (0), rssi:0
Feb 4 08:10:17 wlceventd: wlceventd_proc_event(556): eth5: Assoc 70:03:9F:9A:XX:YY, status: Successful (0), rssi:-62

 

[Tech9]

Seems like some IoT device with Espressif chip. Thanks for not sharing what device is this and I had to look the vendor by needlessly obscured MAC address. Do you have your 2.4GHz radio set as per ASUS IoT compatibility FAQ recommendations? If you bring this device closer to the router does the issue go away?

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

 

[degrub]

Given that the rest of your IOTs are doing fine, either 1) new interference source on 2.4 GHz , 2) weak radio on the IOT device from age - clearly a weak/marginal RSSI value (-64 dB ) . Don't know if the IOT device can provide the RSSI value seen from its location, but worth a look.
May just be time to replace it.

2,4 GHz - 20 MHz channel width ( not 20/40), fixed control channel, WPA or WPA2 ( not 2/3)

 

[dwp]

Thanks to all for comments. Sorry to have caused frustration. The device is indeed ESP-based.

Meanwhile, I MAY have discovered I have lied earlier when I wrote "I am not quite sure what, if anything, may have changed to cause this." I realize now that for the last couple weeks, I enabled the traffic analyzer on the router. I can see when disabling it that the RAM usage went down from 78% to 66%.

In the past, I have seen many posts saying to not really worry about the RAM as it contains re-usable cache. Still I wonder if this is the source of my grief?

I was not aware that a IoT radio could really just go bad from age. But all things die, no? I hope not in this case as it is an expensive but important device - a water valve shutoff robot.

Finally, I do use only a 20 MHz width with fixed channels and no WPA 2/3.

I am hoping that it is just me shooting myself in the foot - as usual

Best

 

[Tech9]

I realize now that for the last couple weeks, I enabled the traffic analyzer on the router. I can see when disabling it that the RAM usage went down from 78% to 66%.

This is totally unrelated to your connectivity issue. The power supply is also unrelated. This device perhaps needs better signal if a repeater improves the situation.

 

[dwp]

This is totally unrelated to your connectivity issue. The power supply is also unrelated. This device perhaps needs better signal if a repeater improves the situation.

Likely just wishful thinking. I have had some recent experience with ESP devices. Their onboard antennas are lame. And since they are fixed in the orientation of the board, I can see they might be very picky about orientation. I will try taking it off the wall and re-positioning it at a 90 degree angle to see if that helps any. Still, it was working quite well. I also realize that I recently swapped an ESP-based smart plug out for a TP-Link one in that area. Perhaps that made a difference? Thanks!

 

[Tech9]

Perhaps that made a difference?

Not greatest Wi-Fi is common for IoT devices. If the device is operating on the edge of usable for it signal any environmental change may cause disconnections. This change may be caused by turning on some machine with electric motors generating RF noise, microwave oven, cordless phone, etc. Hard to tell what exactly caused the issue in your case.