Under controller firmware management page, we can currently only update firmware on a device with a lower version number.

Although this makes some sense, there have been a few beta and RC releasees recently (specifically on routers) where there have been several re-releases of updated firmware with the same version number.  The controller does not allow us to directly update these, as it seems to only check the current version, and if it matches, it cannot be applied, making us either have to use workarounds (eg ssh roll-back command, or the emergency re-flash function of the device directly) or wait a long time for it to appear on the support pages for direct download

This has hapenned recently on ER8411 1.3.0 (two builds, same version, a month apart), ER605 (two builds, same version, 2 weeks apart), ER7206 v2 (two builds, same version, 3 weeks apart)

What we seem to get for beta testing on the forums is generally modified and updated based on our feedback, then released to the controller.  If we updated through the forum release, we cannot directly upgrade to the controller release.

I propose this is adjusted in one of two ways:

- Controller should check the Date-String of a release and allow us to apply it if the build date is newer, regardless if the version is the same or not

- Just let us update anything all the time with no checks, other than "is this firmware actually for this device"