Release Asuswrt-Merlin 3004.388.10 is now available

[Unetwork]

Update to the new version 388.10 (AX88U)

Manual WPS reset and manual reconfiguration of all settings.

Everything seems to be working fine so far. Thank you Merlin

 

[shivaprasadh]

Upgraded my AX-88U from firmware version 3004.388.9_2 to 3004.388.10, and for the first time in my long experience with Asus Merlin, the new release 3004.388.10 has broken the functionality of the "Asus Router" App on iOS devices. After applying the update, the app stopped working. So decided to revert to version 3004.388.9_2, where the app's functionality was restored. I've decided to stick with 3004.388.9_2 until this issue is resolved in the latest release.

@RMerlin, I understand the Asus Router App might not be a top priority for you, but it would be greatly appreciated if you could look into this issue, as many users like myself enjoy the convenience of managing the router via the iOS app. Thank you once again for your time and effort.

 

[bennor]

Upgraded my AX-88U from firmware version 3004.388.9_2 to 3004.388.10, and for the first time in my long experience with Asus Merlin, the new release 3004.388.10 has broken the functionality of the "Asus Router" App on iOS devices.

The Asus router app is not officially supported by Asus-Merlin firmware. See RMerlin's response:

Configure it through the webui. The mobile app is not supported.

Edit to add: And this response by RMerlin.

I have no control over the mobile app, it's developed by Asus, not by me.

 

[ColinTaylor]

Upgraded my AX-88U from firmware version 3004.388.9_2 to 3004.388.10, and for the first time in my long experience with Asus Merlin, the new release 3004.388.10 has broken the functionality of the "Asus Router" App on iOS devices. After applying the update, the app stopped working. So decided to revert to version 3004.388.9_2, where the app's functionality was restored. I've decided to stick with 3004.388.9_2 until this issue is resolved in the latest release.

@RMerlin, I understand the Asus Router App might not be a top priority for you, but it would be greatly appreciated if you could look into this issue, as many users like myself enjoy the convenience of managing the router via the iOS app. Thank you once again for your time and effort.

This has been reported numerous times already in this thread. Asus' app is not supported by RMerlin and never has been.

 

[shivaprasadh]

This has been reported numerous times already in this thread. Asus' app is not supported by RMerlin and never has been.

I understand that this is not supported by RMerlin. But why suddenly in this release 3004.388.10 this functionality is broken?
So, I am requesting @RMerlin , to see if there is any chance for him to get this addressed. This is again a REQUEST to him to get this addressed.

 

[dave14305]

Perhaps the issues with the Asus app stem from the fact that Asus has not yet publicly released any 388 firmware based on version 388_25523 (used in Merlin 388.10) or later. Perhaps once (or if) they do, they will also update the Asus app to be compatible.

 

[RMerlin]

@RMerlin, I understand the Asus Router App might not be a top priority for you, but it would be greatly appreciated if you could look into this issue,

As @bennor said - that mobile application is written by Asus. I have zero way of even knowing what it does or how it does it, and I cannot control what it does either.

 

[STRUZZIN]

All units running great for me and family / friends:
RT-AX58U
RT-AX86U
RT-AX88U
RT-AX68U
Thank You

 

[ColinTaylor]

All units running great for me and family / friends:
RT-AX58U
RT-AX86U
RT-AX88U
RT-AX68U
Thank You

It would be helpful if you removed the colour attributes from your signature. White text is nearly invisible in "light" themes.

 

[DelBierzo]

Upgraded my AX-88U from firmware version 3004.388.9_2 to 3004.388.10, and for the first time in my long experience with Asus Merlin, the new release 3004.388.10 has broken the functionality of the "Asus Router" App on iOS devices. After applying the update, the app stopped working. So decided to revert to version 3004.388.9_2, where the app's functionality was restored. I've decided to stick with 3004.388.9_2 until this issue is resolved in the latest release.

@RMerlin, I understand the Asus Router App might not be a top priority for you, but it would be greatly appreciated if you could look into this issue, as many users like myself enjoy the convenience of managing the router via the iOS app. Thank you once again for your time and effort.

"Asus Router" app on android works fine. I know you're referring to iOS, just saying this as a note.

 

[STRUZZIN]

It would be helpful if you removed the colour attributes from your signature. White text is nearly invisible in "light" themes.

Don't even remember doing it is it okay in red or black?
I use pitch black theme so I never see what it looks like

 

[dave14305]

Don't even remember doing it is it okay in red or black?
I use pitch black theme so I never see what it looks like

Don’t use colors at all. That way it will adjust based on the theme in use (light or dark).

 

[gk802]

Dirty upgrade on RT-AX86U from 3004.388.9_2 to 3004.388.10. No issues whatsoever.

 

[shivaprasadh]

As @bennor said - that mobile application is written by Asus. I have zero way of even knowing what it does or how it does it, and I cannot control what it does either.

Above is the snapshot I took from the Asus Website for Firmware 3.0.0.4.388_24333. Looks like most of the updates are in alignment with the release notes from Merlin FW 3004.388.10.
As I highlighted in the above image, should I have to do the "Factory Reset" in order to activate all the new Security Enhacments? Will try this out today evening and see if this might help the "Asus Router" App issue.

 

[aex.perez]

I understand that this is not supported by RMerlin. But why suddenly in this release 3004.388.10 this functionality is broken?
So, I am requesting @RMerlin , to see if there is any chance for him to get this addressed. This is again a REQUEST to him to get this addressed.

You can try what I did - https://www.snbforums.com/threads/asuswrt-merlin-3004-388-10-is-now-available.95831/post-971185
The app bombed on the Alpha and the Beta, and obviously with the release. I got it to work again under IOS 18.x and IOS 26.x on my iPhone. But I had to completely remove the app on the iPhone, and it's data and start from scratch with a fresh install of it from the App store and resetup the authentication. I didn't have to do a factory refresh either...

It works on my iPhone 14, just went it again now to make sure.
Your Mileage May Vary - But NOT Supported

 

[Analog-1]

Will try this out today evening and see if this might help the "Asus Router" App issue.

Possibly, but Asus recommending a factory reset is simply for one reason. It will kick in the new password limitations and force you to comply.

 

[Aarlin303]

Everything good on my simple setup, AXE-11000.
Thanks Merlin

 

[Vaskivskyi]

Hello there. Since quite a number of replies here are related to the issues with the Home Assistant integrations causing issues with WebUI, I think I can clarify what happened. My project is the Python communication backend behind both mentioned here HA integrations - AsusWRT (native HA, from the version 2025.9.0) and AsusRouter - a custom one used by some.

Short version: The library works by introducing itself as the mobile app in the HTTP headers - thus the issue in the current release. Since the App is not supported by Merlin, nothing to judge the developers' team for this.

Long version: Depending on the exact FW version before, our favourite routers were able to keep a limited number of simultaneous connections over HTTP(S). So, for my library to work, I found the only method of connection, which was:
- non-blocking for the WebUI
- was not dropped when someone logs into the WebUI
shortly - mimicking the Asus Router mobile app. In this way, I got compatibility with routers as old as RT-AC66U (my first one) on 380.70 and as new as whatever is there now (BE models).
Some, of course, had more issues, for which I found "solutions" in terms of recommending an SSL connection to be set up (because those were dropped less), and some more to patch what was mostly working fine. Anyways...

Solution?
I will try to find an auth/communication method which would work better with the new release as soon as I get free time for this. I have an RT-AX88U, which can be used for tests, but as you can imagine, just taking an active router (actually, node) from my home network during the working week for this is troublesome.
Meanwhile, some of my users found that having SSL for the mobile app and HA, while keeping non-SSL for using WebUI, works in some cases. So, this might be a super temporary solution (https://github.com/Vaskivskyi/ha-asusrouter/issues/1024#issuecomment-3372815673).

P.S. Disclaimer: `AsusRouter` Python library, HA integration and other resources like the webpage mentioned in comments before, are NOT affiliated with Asus, regardless of their name. I don't have any actual information on how exactly the communication protocols for our routers work. Any work done by me is based on tracking what the WebUI and mobile apps are sending and receiving, dumb testing on my personal devices and a bit of scientific guessing. I am not paid for the work on these projects, nor do I receive any direct monetary or other kind of reward from any party.

 

[zakazak]

Hello there. Since quite a number of replies here are related to the issues with the Home Assistant integrations causing issues with WebUI, I think I can clarify what happened. My project is the Python communication backend behind both mentioned here HA integrations - AsusWRT (native HA, from the version 2025.9.0) and AsusRouter - a custom one used by some.

Short version: The library works by introducing itself as the mobile app in the HTTP headers - thus the issue in the current release. Since the App is not supported by Merlin, nothing to judge the developers' team for this.

Long version: Depending on the exact FW version before, our favourite routers were able to keep a limited number of simultaneous connections over HTTP(S). So, for my library to work, I found the only method of connection, which was:
- non-blocking for the WebUI
- was not dropped when someone logs into the WebUI
shortly - mimicking the Asus Router mobile app. In this way, I got compatibility with routers as old as RT-AC66U (my first one) on 380.70 and as new as whatever is there now (BE models).
Some, of course, had more issues, for which I found "solutions" in terms of recommending an SSL connection to be set up (because those were dropped less), and some more to patch what was mostly working fine. Anyways...

Solution?
I will try to find an auth/communication method which would work better with the new release as soon as I get free time for this. I have an RT-AX88U, which can be used for tests, but as you can imagine, just taking an active router (actually, node) from my home network during the working week for this is troublesome.
Meanwhile, some of my users found that having SSL for the mobile app and HA, while keeping non-SSL for using WebUI, works in some cases. So, this might be a super temporary solution (https://github.com/Vaskivskyi/ha-asusrouter/issues/1024#issuecomment-3372815673).

P.S. Disclaimer: `AsusRouter` Python library, HA integration and other resources like the webpage mentioned in comments before, are NOT affiliated with Asus, regardless of their name. I don't have any actual information on how exactly the communication protocols for our routers work. Any work done by me is based on tracking what the WebUI and mobile apps are sending and receiving, dumb testing on my personal devices and a bit of scientific guessing. I am not paid for the work on these projects, nor do I receive any direct monetary or other kind of reward from any party.

Thank you. So this will most likely also be the cause for the issue with the asus mobile app (I don't use it but I guess this is it).

I am not using your integration but instead the officia HA AsusWRT integration. I hope they are fixing the issue too.

Or maybe easier, if @RMerlin could find a way to make it work like it did with the previous version? In that case everything will be back to normal for every 3rd party.