Release Asuswrt-Merlin 3004.388.6 is now available

[Morris]

Just if anyone have this issue.
I have RT-AX86S running on 388.6_2.
I have a old Blink sync module unable to connect to 2.4GHz at all. There is no association logs at all.

When I turn on my RT-AC86U (386.7_2) as mesh node, the Blink sync module automatically connects without any issues.
The config I have tried for RT-AX86S still does not help.
- uncheck disable 11b
- disable wifi6 on 2.4GHz

Any ideas?

note: the Blink sync module only supports 2.4GHz

This is the Asus IOT recomendations:

Official Support | ASUS Global

ASUS Support Center helps you to downloads Drivers, Manuals, Firmware, Software; find FAQ and Troubleshooting

www.asus.com

Good luck,
Morris

 

[lala_cai]

This is the Asus IOT recomendations:

Official Support | ASUS Global

ASUS Support Center helps you to downloads Drivers, Manuals, Firmware, Software; find FAQ and Troubleshooting

www.asus.com

Good luck,
Morris

Forgot to mention that I was coming from 388.2
The blink sync module was connected via 2.4GHz without any issues.

The strange part is the sync module can connect to my mesh node RT-AC86U without any issues as well.
I assume the mesh node have the same wifi settings inherit from the RT-AX86S

Saw 1 post by allwise also having the same issue.
Will try to downgrade later and see.

 

[sandone]

In my case only tasmota sockets can't connect with 2.4GHz wlan. No guestnet is activated. Strange thing is that there is no problem with ac86u node which must have same settings as main router. After rebooting main all tasmotas can connect to main without changing any setting.

2.4GHz, wpa2, n only/legacy/auto (makes no difference)
No Aiprotection, no USB

EDIT: Tested also with factory fimware (3.0.0.6.102_33308) with same result.

With the ac86u (386.13_alpha1) there is no problem at all.

Did 388.7 fix the issue? I am staying on 388.6 until I hear a success story on going from 6->7.

Thanks!

 

[L&LD]

Is it a good idea to keep up with Firmware updates?

I have had issues in the past when updating firmware and Internet speed, But it may have just been a fluke, Should I keep up with the updates? If so On all routers or the nodes as well? What about ones acting as access points? Thanks

www.snbforums.com

The only success story that matters is your own. And you won't know the outcome until you test with your router and in your environment.

Use the link above to create a quick way to get back to where you are now. And, freeing yourself to test the current firmware properly too (with a full reset and minimal and manual configuration, if needed).

 

[Dedel66]

Did 388.7 fix the issue? I am staying on 388.6 until I hear a success story on going from 6->7.

In my case the issue does not exist anymore. but the reason was NOT asus, the reason were the ESP8622 devices (tasmota plugs). Switching them to "g"-mode fixed the problem.

In my opinion the 388.7 is an absolute stable firmware. You may save all your settings (yazdhcp is your friend ) and test your setup with 388.7. Even if you see everybody is satisfied with 388.7 it must not be perfect for you.