[BUG] - Incorrect Firmware Update Version Detection in MerlinAU

[fire-nxe]

Describe the bug
In the MerlinAU dashboard, the “Firmware Update Available” field displays version 3004.388.10.2-gnuton1, which is older than the currently installed firmware version 3004.388.11.1-gnuton0_beta1_tuf.

To Reproduce
Steps to reproduce the behavior:

1. Update to 3004.388.11.1-gnuton0_beta1_tuf in TUF-AX5400
2. Open router WebUI
3. Go to MerlinAU Dashboard v1.6.0
4. Observe “F/W Version Installed” and “F/W Update Available”

Expected behavior

• MerlinAU should only display firmware updates that are newer than the installed version.
• No update should be shown if the available version is older.

Screenshots

Router Information (please complete the following information):

• Router Model TUF-AX5400
• Firmware Version: 3004.388.11.1-gnuton0_beta1_tuf
• Firmware Variant: Gnuton
• MerlinAU Version: v1.6.0

[ExtremeFiretop]

But what does the CLI say.

The WebUI mostly displays what is stored in the settings file.

As long as no update is actually detected in CLI, it's not actually considered an update available.

[ExtremeFiretop]

@fire-nxe

Also please share the contents of your settings file, make sure to remove any sensitive content like your password.

[ExtremeFiretop]

@fire-nxe

Nvm I was able to recreate this issue.
I believe I addressed the areas that can influence this bug.

1. The WebUI was consistently setting a static weight value of -100 for Beta/Alpha releases, regardless of the setting for Beta-to-Release F/W Updates

• The WebUI should only set the weight penalty of beta/alpha releases if the setting is enabled for: Beta-to-Release F/W Updates
  Additionally, when enabled, it should compare the numeric segments first and only use beta/alpha status as a tie-breaker within the SAME numeric version.

@Martinski4GitHub please look at PR for fixing this report: #559

[ExtremeFiretop]

@fire-nxe

Did you want to test the change and advise?
My PR was merged into development branch last night.

If so, please run:
sh /jffs/scripts/MerlinAU.sh develop

to update to the latest development version.

When your ready to return to production, use:
sh /jffs/scripts/MerlinAU.sh stable

[fire-nxe]

Thank you @ExtremeFiretop . Ran the development branch and it looks good to me now.

Really appreciate how quickly you identified and fixed this issue!

[ExtremeFiretop]

Really appreciate how quickly you identified and fixed this issue!

It's how we do it around here ;) It helps that I have a great partner with @Martinski4GitHub
You can expect this bug to be fully fixed by the next release (which should be fairly soon)

Thanks for reporting!

[ExtremeFiretop]

Hi @fire-nxe

Would you be able to test something for us if you still have this router and the TUF WebUI installed?

Let me know!
Joel S.

[fire-nxe]

Hi @ExtremeFiretop

I've moved onto an RT-BE92U which has MerlinAU installed on the WebUI. Let me know if my help is needed.

Cheers!

[ExtremeFiretop]

Hi @ExtremeFiretop

I've moved onto an RT-BE92U which has MerlinAU installed on the WebUI. Let me know if my help is needed.

Cheers!

Hi @fire-nxe

I really do appreciate your offer to help and the quick response.

Unfortunately the testing we were hoping to run was to verify the visuals of the latest WebUI for MerlinAU, while on ROG or TUF routers.

We generally know the visuals work well with the "regular" WebUI, but we're not sure how it would work on ROG or TUF. It sounds like you may not have a TUF router available to you anymore. If that's not the case let me know and we can do some testing.

Otherwise no hard feelings at all and again really appreciate you stepping up!
Cheers!