Asus RT-AX88U Pro, 3006_102.4_0 firmware and ESP32 devices; no connection at all?

[hjheins]

Hello All,

I have an RT-AX88U Pro, and was running firmware 3004_388.7_0 When 3006_102.4_0 came out, I updated.
However, after the update, none of my esp32 devices could connect anymore.
I already did all the tweaks before (ssid without spaces, Airtime Fairness, Roaming Assistant. Setting the esp to g-mode only, etc).
And with firmware version 3004_388.7_0 this all worked just fine.
With firmware 3006_102.4_0 I can not get any of the esp devices connected, even with all these tweaks.
Is this a firmware bug, or am I doing something wrong?

thanks.
Hendrik-Jan

 

[bennor]

If you haven't done so already, use the forum search feature to search for other discussions on IoT devices having trouble connecting with the 3006.x firmware. Some are finding their IoT devices are having issues with certain 3006 firmware WiFi settings. There are a number of past discussions with various suggestions. Among those suggestions are:

• Don't use WPA2/WPA3 as the Authentication Method, use WPA2-Personal.
• Turn off Smart Connect.
• Set the 2.4GHz band to 20 Mhz rather than 20GHz/40 Mhz.
• Set a specific Control Channel.
• Use AES Encryption Method if previously using TKIP+AES.

 

[hjheins]

Hi @bennor,
thank you for your reply.
The suggestions you mention are indeed also already in place for the 3884 firmware.
I have all of those implemented, and indeed in the 3884 it seems to work like that.
I searched for these connection issues in relation to the 3006 firmware specific, and so far I found nothing new (read: nothing that wasn' t already suggested for the 3884 firmware; and I already had implemented). hence my question here specific for this firmware version.

 

[bennor]

I searched for these connection issues in relation to the 3006 firmware specific, and so far I found nothing new (read: nothing that wasn' t already suggested for the 3884 firmware; and I already had implemented). hence my question here specific for this firmware version.

As a last resort troubleshooting step have you tried a hard factory reset on the router followed by a manual configuration (don't import a saved router.cfg file) ? Some are finding odd ball issues when they flashed the 3006 firmware over the top of the 388.x firmware and didn't do a hard factory reset post firmware flash.

PS: If you were previously using YazFi on the 388.x firmware and didn't uninstall it prior to installing the 3006 firmware that might potentially cause a conflict. YazFi is not currently supported under the 3006.x firmware.

 

[KuroSynthesis]

What I've done to solve the connection problems with my home automation devices is to create a guest Wi-Fi network on the 2.4 GHz WPA2 band.

I did the same thing with my previous router and now with the new one with Wifi 7 and since then I have not had any problems with disconnections or the device not connecting directly.

 

[CaptainSTX]

Hello All,

I have an RT-AX88U Pro, and was running firmware 3004_388.7_0 When 3006_102.4_0 came out, I updated.
However, after the update, none of my esp32 devices could connect anymore.
I already did all the tweaks before (ssid without spaces, Airtime Fairness, Roaming Assistant. Setting the esp to g-mode only, etc).
And with firmware version 3004_388.7_0 this all worked just fine.
With firmware 3006_102.4_0 I can not get any of the esp devices connected, even with all these tweaks.
Is this a firmware bug, or am I doing something wrong?

thanks.
Hendrik-Jan

Set the DNS for the problematic devices to 8.8.8.8 or 8.8.4.4 because if you have enabled DOT it can block certain devices from connecting as they want to know where they are and be able to connect to the mother ship.

 

[hjheins]

Hi All,
Thanks a lot for the suggestions!
from bottom to top
@CaptainSTX : Thanks, I actually refer to a DNS Server in my own network. So I guess this one is covered?
@KuroSynthesis : I have the esp devices on a separate guest network with only WPA2 Peronal + aes enabled.
@bennor : good point; I did not try that yet. I only uses the stock firmware and after that the Merlin firmware. I will test and get back

Hendrik-Jan

 

[bennor]

Thanks, I actually refer to a DNS Server in my own network. So I guess this one is covered?

Are you by chance blocking access to Google's DNS servers via LAN > Route, or some other method? Sometimes IoT devices will have their DNS servers hard coded which can cause issues if they cannot reach those DNS servers.
Also double check that the IoT devices are configured for Internet access. Blocking Internet access may also present issues for certain IoT devices.

 

[dacotmeister]

following this post... have ioT issues as well, very irratic behaviour sometimes and I cant pin point it yet why....

 

[hjheins]

Hello All,

@bennor , I followed your advice and did a full factory reset; I even did not load the config file, but configured by hand.
Unfortunaletly it made no differende; I switched back to the 3884 firmware. Now things are more or less stabel again, and my IOT devices are available. As info: it is all Tasmota, so external DNS should not make a difference.
@dacotmeister : When using the 3884 firmware, and using the ointers mentioned in this tread (separate wifi guest network etc...), you will get it more or less stable solution (I still need to reboot the router every so many weeks as at least 1 IOT device drops off the network.

cheers,

Hendrik-Jan

 

[dacotmeister]

Hello All,

@bennor , I followed your advice and did a full factory reset; I even did not load the config file, but configured by hand.
Unfortunaletly it made no differende; I switched back to the 3884 firmware. Now things are more or less stabel again, and my IOT devices are available. As info: it is all Tasmota, so external DNS should not make a difference.
@dacotmeister : When using the 3884 firmware, and using the ointers mentioned in this tread (separate wifi guest network etc...), you will get it more or less stable solution (I still need to reboot the router every so many weeks as at least 1 IOT device drops off the network.

cheers,

Hendrik-Jan

@hjheins it might be a good idea to revert to the previous version indeed as I have 50+ iOT devices in my LAN and it's a hell of a job to move them all to a seperate VLAN.