AiMesh - AX92U firmware upgrade 3.0.0.4.384_8681

[Simon W]

I'm currently using a AX88U on 384.16_B1, along with a couple of AX92U's on 3.0.0.4.384_7977.

AiMesh seems to be working better than previously, and I'm putting this possibly down to the fact both these Merlin and oem firmwares use the same GPL release (certainly can't hurt, right?).

I notice 3.0.0.4.384_8681 is now available for the AX92U.. wondering if taking me out of sync (again) might do more harm than good?

Any reports from anyone with a similar setup having already taken the plunge?

 

[JDB]

My experience has always been its best to stay on the same GPL

Given the nodes are not a major part of your network’s security or features you are not gaining anything by upgrading them ahead of the router anyway.


Sent from my iPhone using Tapatalk

 

[L&LD]

Why break a working setup? If the 'AX92U's are nodes, no real reason for you to upgrade (performance or security-wise).

 

[Simon W]

Agreed and this is exactly why I haven't upgraded!

In terms of AiMesh, I do still consider it a work-in-progress offering, especially in terms of interoperability across different models (despite this being one of its key sales pitches) - there's no way Asus have fully tested various combinations of models/firmware versions/configurations and features.. disappointingly seemingly not even the most likely ones to be found in the wild - though I'm pleased to say with each firmware release I'm seeing stability improvements. Ok, perhaps "each release" might include a placebo effect but I'm 100% certain things have improved from first release to this point. Like I say, my AiMesh is now working better than ever.. but this is against the backdrop of it being truly awful to begin with!!

Edit: "better than ever" = rarely needs to be manhandled back into life, still switches down from 5Ghz to 2.4Ghz backhaul more often than is surely desirable, occasionally 'sticks' at 2.4Ghz (which is bordering on useable due to bandwidth requirements and congestion) and requires a reboot to immediately put it back up to 5Ghz for a few more days. Now it's more a cause of sometimes just needing to flick clients wi-fi off and on to force a reevaluation of their life (wi-fi) choices which is obviously easier done on some devices (phones, laptops) than others (cameras etc).

Edit 2: I also recognise the bulk of client roaming issues are just that - issues with the client - but I'm hoping as standards and implementations evolve this too will improve.