Release ASUS ZenWiFi Pro ET12 Firmware version 3.0.0.6.102_36602 (2025/05/05)

[junior120872]

I went ahead and applied the May 5, 2025 firmware update, 3.0.0.6.102_36602. I downloaded the file from the ASUS website, and used the WebUI to manually update each of my two devices, the primary device first, as recommended by a Google search. So far, everything is running smoothly. Only one device, a camera in my back yard, that doesn't want to connect to it's closest node. Other than that, speeds are great, as expected. Now I'm debating whether to head off problems by doing a factory reset on each node. My system isn't that complicated, I use wireless 6Ghz for backhaul, and split the 2.4 and 5G WiFi into two separate SSIDs. For setup purposes, I can toss an ethernet cable across the hallway to the 2nd node, if necessary.

I'm curious if most of you go ahead and do the factory reset after updating firmware, or only reset if issues present themselves?

Thanks!

If it were me in that case for major releases, (3.0.0.4) to (3.0.0.6) I would do a reset and start from scratch, just to remove cruft from the previous. I'm sure there are a lot of folks that have no issues, but it's nice to start on a clean state at times. With all the new SDN stuff in this build it may be better to start at a clean state. If your network isn't too complex it shouldn't be too difficult. Just take notes of what your changes were from default, and it should be smooth sailing.

 

[rush_ad]

I am having an issue with my Lifx lights. They are not able to connect to my network after upgrading to 3.0.0.6.102_36602. I had the same issue with 3.0.0.6.102_36597. I had to revert back to 3.0.0.4.388_24610 for everything to work.

Similar experience for me... especially on VLAN Guest Network or IoT network... on my Kasa IoT devices.

On 6.102 firmwares...my Kasa devices are not able to connect to VLANs 2.4GHz on AiMesh nodes. They seem to work fine on my main router.

Also everything works fine on my home network. Just the VLANs on mesh nodes having problems.

I tried several factory reset, switching nodes, etc. Nothing worked. Went back to 4.388 and everything seems to be working now.

 

[junior120872]

Similar experience for me... especially on VLAN Guest Network or IoT network... on my Kasa IoT devices.

On 6.102 firmwares...my Kasa devices are not able to connect to VLANs 2.4GHz on AiMesh nodes. They seem to work fine on my main router.

Also everything works fine on my home network. Just the VLANs on mesh nodes having problems.

I tried several factory reset, switching nodes, etc. Nothing worked. Went back to 4.388 and everything seems to be working now.

Did you upgrade your nodes to 3006.102 as well? With the SDN features there will be issues, since 3006.102 uses Guest Network Pro/Network.

 

[rush_ad]

Did you upgrade your nodes to 3006.102 as well? With the SDN features there will be issues, since 3006.102 uses Guest Network Pro/Network.

Yes...all routers and nodes are updated to the latest version.

 

[rush_ad]

Seems to be something to do with WPA2/WPA3 Personal security setting.

When I set the security to WPA2/WPA3 Personal:
My Kasa devices can only connect to the main router and NOT to the AiMesh node.

When I set the security to WPA/WPA2 Personal:
My Kasa devices can connect to the main router and the AiMesh node.

I know for sure that Kasa devices support WPA2 and should be able to connect with either of the above settings.

 

[junior120872]

Seems to be something to do with WPA2/WPA3 Personal security setting.

When I set the security to WPA2/WPA3 Personal:
My Kasa devices can only connect to the main router and NOT to the AiMesh node.

When I set the security to WPA/WPA2 Personal:
My Kasa devices can connect to the main router and the AiMesh node.

I know for sure that Kasa devices support WPA2 and should be able to connect with either of the above settings.

Ah yes. I only have wpa2-personal set since I only run IoT devices on 2.4Ghz. I don't even have a 2.4Ghz SSID assigned for my main network. The second item is interesting. Are your nodes also ET12's?

 

[rush_ad]

Ah yes. I only have wpa2-personal set since I only run IoT devices on 2.4Ghz. I don't even have a 2.4Ghz SSID assigned for my main network. The second item is interesting. Are your nodes also ET12's?

I see your point.
My IoT SSID is 2.4GHz only. But my main SSID is set to Triband Smart Connect.

And I only have a pair of ET12s...both running latest firmware.

My issue must be something to do with the firmware because:
1) I can get IoT to connect to the main router, but not with the node.
2) I swapped main router and the node ... as in trying both ET12 units as the main routers...and the issue persists.


So overall I feel that the firmware isn't setting up the AiNode properly to serve WPA2/WPA3 Personal security to the IoT devices.

 

[junior120872]

I see your point.
My IoT SSID is 2.4GHz only. But my main SSID is set to Triband Smart Connect.

And I only have a pair of ET12s...both running latest firmware.

My issue must be something to do with the firmware because:
1) I can get IoT to connect to the main router, but not with the node.
2) I swapped main router and the node ... as in trying both ET12 units as the main routers...and the issue persists.


So overall I feel that the firmware isn't setting up the AiNode properly to serve WPA2/WPA3 Personal security to the IoT devices.

Interesting. Have you tried removing 2.4Ghz from Smart connect? When it's outside of smart connect you may see different encryption options. I have them all separate but same SSID and password for 6ghz and 5ghz. When you swapped the router/node, did you start from scratch or restore the config? Is the 2.4Ghz radio enabled on the node? Also have you tried breaking the mesh and re-adding the node again?

 

[rush_ad]

Interesting. Have you tried removing 2.4Ghz from Smart connect? When it's outside of smart connect you may see different encryption options. I have them all separate but same SSID and password for 6ghz and 5ghz. When you swapped the router/node, did you start from scratch or restore the config? Is the 2.4Ghz radio enabled on the node? Also have you tried breaking the mesh and re-adding the node again?

My IoT network is 2.4Ghz only...which is where my problems area. And it's enabled on all mesh nodes.

My main network is Triband and it has no problems.

For all my swapping and different ideas... I setup from scratch. I don't restore settings at all.

I'm able to replicate the problem by changing IoT SSID security between WPA/WPA2 Personal (works) and WPA2/WPA3 Personal (doesn't work).

 

[bennor]

Seems to be something to do with WPA2/WPA3 Personal security setting.

Quite a few have reported compatibility issues to the various Asus subforums on this site when using WPA2/WPA3, or just WPA3, when it comes to WiFi clients on the 3006.x firmware. Seems quite a few have problems with the WPA2/WPA3 on the Guest Network Pro feature when using certain IoT devices. The workaround, for most seems to be drop the WiFi authentication down to WPA2-Personal or WPA/WPA2. Some also have to change a few of the WiFi 2.4Ghz settings as well. Like setting the frequency to 20hz and setting the channel to 1, 6 or 11.

 

[rush_ad]

So I have something new to share...totally by accident.

I was setting up VPN Fusion with my parents home, using another Asus router. Using Wireguard protocol.

All I did was to apply VPN Fusion to all my home devices. And instantly my Kasa IoT devices on the guest network disconnected with the AiNode and started connecting with the main router. I did not change anything with SSID security...just VPN.


Basically it sounds to me that the current firmware has issues transferring setting to the nodes...when changes are made to the main router. So far I am able to confirm that security settings and VPN setting cause problems.

 

[Gunslinger]

If it were me in that case for major releases, (3.0.0.4) to (3.0.0.6) I would do a reset and start from scratch, just to remove cruft from the previous. I'm sure there are a lot of folks that have no issues, but it's nice to start on a clean state at times. With all the new SDN stuff in this build it may be better to start at a clean state. If your network isn't too complex it shouldn't be too difficult. Just take notes of what your changes were from default, and it should be smooth sailing.

I went ahead and did the factory reset. The only issue I had is that my Honeywell T10 thermostat refused to connect to either the 2.4 or 5Ghz primary networks. It did connect to the guest network at 2.4Ghz, surprisingly. I factory reset the Thermostat, and now it connects to the primary 2.4Ghz network, but still not the 5Ghz side, which is where it had been for 2 years. I suspect that it's a result of my changing the 5Ghz channel from the manual ch.36 that it was on before I reset, to ch.149. The T-stat may not be able to handle the upper 5Ghz channels. Other than that, all works well.