MerlinAU MerlinAU v1.3.12 - The Ultimate Firmware Auto-Updater (GNUTON SUPPORT!)

[ExtremeFiretop]

Hi,

I've got merlin au on main router and on the ai mesh, I've got a usb stick on the mesh, can you set the f/w update directory path to the usb stick, couldn't seen option for it when I set it up.

Thanks

Check under the advanced options (ad).
Option (1) .

Thanks

 

[visortgw]

Hi,

I've got merlin au on main router and on the ai mesh, I've got a usb stick on the mesh, can you set the f/w update directory path to the usb stick, couldn't seen option for it when I set it up.

Thanks

ad. (Advanced Options) ==> 1. (Set Directory for F/W Update File). Directory includes device name.

 

[jb68]

USB drive doesn't appear when I do that on the mesh router?

But on the main router it works fine:

 

[ExtremeFiretop]

View attachment 64098

USB drive doesn't appear when I do that?

Check to validate the path to your USB is actually mounted. If it is, then enter that path as the destination when it asks you in that screenshot.

Or just install MerlinAU with a USB already mounted; and it should detect it automatically as the default.

 

[jb68]

View attachment 64098

USB drive doesn't appear when I do that?

Check to validate the path to your USB is actually mounted. If it is, then enter that path as the destination when it asks you in that screenshot.

Or just install MerlinAU with a USB already mounted; and it should detect it automatically as the default.

Hi,

Reinstalled merlinau and it has defaulted to the usb stick now, thanks for the help.

Brilliant script!

 

[ExtremeFiretop]

Hi,

Reinstalled merlinau and it has defaulted to the usb stick now, thanks for the help.

Brilliant script!

No worries. The reason it falls back to the home directory is to make sure we get the required space for the firmware and logs if a USB dies or becomes unavailable.

But if a USB is mounted at the time of install though, as long as it remains available, it should default to it.

We give the option under advanced options to manually update the path if say, you change USB after MerlinAU was installed, have multiple USBs, or you wanted a custom location.

 

[ExtremeFiretop]

Hi everyone!
Happy to officially announce that the new MerlinAU 1.4.0 version with WebUI support has now been merged into the development branch and is available for Beta testing.

-What this means:

1. As previously mentioned, if you wish to update to the latest 1.4.0 Beta version, you MUST have version 1.3.10 already installed. Please update first to the latest 1.3.10 production release before attempting to upgrade to the 1.4.0 Beta version.
2. You may now test the WebUI and report any bugs or issues you identify. We ask that anyone testing the 1.4.0 Beta version open issues on our GitHub repository as 1.4.0 has not been officially released into production yet.
3. At any point, you can roll back to the production version of MerlinAU by switching to the main branch and then rebooting the router.
4. The WebUI is still in the "Beta" stage so currently under active development. Changes can happen quickly without any notice after any reported issues. Any recent changes can be obtained with a forced update via the following command:

sh /jffs/scripts/MerlinAU.sh forceupdate

The development branch is controlled by the "develop" parameter.

To switch to the development branch use the following command:

sh /jffs/scripts/MerlinAU.sh develop

To switch back to the production stable branch, use the following command:

sh /jffs/scripts/MerlinAU.sh stable

Thanks and happy testing!

 

[maghuro]

Testing! Thank you so much for your work

A little thing I noticed right away - when I switched to beta branch, in webui, the "enable automatic f/w update checks" was disabled. On terminal, it was enabled.

To solve this, on terminal, I disabled and enabled again this option, refreshed the webui and then the checkbox was shown correctly enabled.

Just a minor thing.

Edit: also, a suggestion. I don't have a secondary email address for notifications. I'm webui, instead of TBD, it should be blank.
I deleted this text a couple of times via webui, and it kept putting automatically the TBD. As a Portuguese user who isn't totally aware of acronyms, after a quick Google search, I understood it means "To Be Determined", but I was confused for a time blank should be a better understanding option. Blank or a placeholder in the text box with something like "not defined" or something like that

 

[maghuro]

Another one. As you can see, I have a postponement of 1 days. On pressing the F/W update check button, without checking the "bypass postponed days" checkbox, it gives me this alert.
However, I don't know if it will bypass postponed days if I continue, because no firmware update is available right now...

Edit: also, when trying to set postponed days via webui, the number doesn't stick after hit apply, and comes back to the old value. On terminal it changes correctly.
Changing the other options works.

 

[ExtremeFiretop]

Testing! Thank you so much for your work

A little thing I noticed right away - when I switched to beta branch, in webui, the "enable automatic f/w update checks" was disabled. On terminal, it was enabled.

To solve this, on terminal, I disabled and enabled again this option, refreshed the webui and then the checkbox was shown correctly enabled.

Just a minor thing.

This sounds odd to me.

Please include screenshots when reporting behavior if possible
I see you did that in the next post below; but would of helped in this situation as well.

Can you check the contents of your configuration file for: FW_UPDATE_CHECK it should say "ENABLED"

Which is what both the script and WebUI uses, I can review the logic in the morning and try to replicate.

Edit: also, a suggestion. I don't have a secondary email address for notifications. I'm webui, instead of TBD, it should be blank.
I deleted this text a couple of times via webui, and it kept putting automatically the TBD. As a Portuguese user who isn't totally aware of acronyms, after a quick Google search, I understood it means "To Be Determined", but I was confused for a time blank should be a better understanding option. Blank or a placeholder in the text box with something like "not defined" or something like that

Thanks for the suggestion; it's been noted!

 

[ExtremeFiretop]

View attachment 64146

Another one. As you can see, I have a postponement of 1 days. On pressing the F/W update check button, without checking the "bypass postponed days" checkbox, it gives me this alert.
However, I don't know if it will bypass postponed days if I continue, because no firmware update is available right now...

It says "if you have no postpone days set or remaining, it may flash now"
In short, if you click check for updates, it won't bypass the postpone, it will only check for updates. (Unless you specifically set the bypass button)

After 1 day has past from the detection date, you have no more postpone days remaining, so it would flash right away. Same as the CLI shell script.
If you have no postpone set, it will always flash right away with or without the bypass checkmark set.

Edit: also, when trying to set postponed days via webui, the number doesn't stick after hit apply, and comes back to the old value. On terminal it changes correctly.
Changing the other options works.

Again ideally some screenshots comparing both would be ideal, but I'll try to replicate this in the morning.
Check the contents of your configuration file for that as well.

 

[ExtremeFiretop]

Testing! Thank you so much for your work

A little thing I noticed right away - when I switched to beta branch, in webui, the "enable automatic f/w update checks" was disabled. On terminal, it was enabled.

To solve this, on terminal, I disabled and enabled again this option, refreshed the webui and then the checkbox was shown correctly enabled.

Just a minor thing.

Okay; I was able to replicate this so no screenshots needed this time.

Edit: also, when trying to set postponed days via webui, the number doesn't stick after hit apply, and comes back to the old value. On terminal it changes correctly.
Changing the other options works.

This I seem unable to replicate, even with a fresh install and upgrade to the development branch, so screenshots and checking the configuration file would be helpful for this one!

 

[ExtremeFiretop]

Edit: also, a suggestion. I don't have a secondary email address for notifications. I'm webui, instead of TBD, it should be blank.
I deleted this text a couple of times via webui, and it kept putting automatically the TBD. As a Portuguese user who isn't totally aware of acronyms, after a quick Google search, I understood it means "To Be Determined", but I was confused for a time blank should be a better understanding option. Blank or a placeholder in the text box with something like "not defined" or something like that

This suggestion had been handled by @Martinski in PR:

Show blank field if Secondary Email not set. by Martinski4GitHub · Pull Request #417 · ExtremeFiretop/MerlinAutoUpdate-Router

If the "Secondary Email Address" is not yet set show a blank field in the WebGUI page.

github.com

Please run the following command and test again:

sh /jffs/scripts/MerlinAU.sh forceupdate

 

[maghuro]

This I seem unable to replicate, even with a fresh install and upgrade to the development branch, so screenshots and checking the configuration file would be helpful for this one!

The value is between quotation marks. Automatically defined by the script itself. Maybe that's the culprit?

Edit: https://limewire.com/d/2d900f9f-a92...3#9OxnWk7_PVQs2ULROG8yrjmO4JE-_9dLlsYqf5Ae9G0

 

[maghuro]

This suggestion had been handled by @Martinski in PR:

Show blank field if Secondary Email not set. by Martinski4GitHub · Pull Request #417 · ExtremeFiretop/MerlinAutoUpdate-Router

If the "Secondary Email Address" is not yet set show a blank field in the WebGUI page.

github.com

Please run the following command and test again:

sh /jffs/scripts/MerlinAU.sh forceupdate

Perfect! Done... Thanks for your work

 

[Martinski]

The value is between quotation marks. Automatically defined by the script itself. Maybe that's the culprit?

Edit: https://limewire.com/d/2d900f9f-a92...3#9OxnWk7_PVQs2ULROG8yrjmO4JE-_9dLlsYqf5Ae9G0

This falls under user error. Take a closer look at the WebGUI to familiarize yourself with the page layout before you continue testing. There are 3 distinct sections. Each of the 2 bottom sections contains its own "Save" button that applies ONLY to that specific section. If you modify a field value from one section and click on the "Save" button from a different section, the value won't change. You must use the corresponding "Save" button on each specific section of the WebUI for the new parameter to take effect.

 

[ExtremeFiretop]

This falls under user error. Take a closer look at the WebGUI to familiarize yourself with the page layout before you continue testing. There are 3 distinct sections. Each of the 2 bottom sections contains its own "Save" button that applies ONLY to that specific section. If you modify a field value from one section and click on the "Save" button from a different section, the value won't change. You must use the corresponding "Save" button on each specific section of the WebUI for the new parameter to take effect.

This is probably the right answer, I'm just waking up now from a long night, but even with fresh eyes I can't replicate this report.

I can for sure replicate his other reported issue of the script not starting as "Enabled" in the WebUI though!

I'll start poking at that in a moment.

 

[ExtremeFiretop]

Edit: https://limewire.com/d/2d900f9f-a92...3#9OxnWk7_PVQs2ULROG8yrjmO4JE-_9dLlsYqf5Ae9G0

Just checked the video out, and as Martinski mentioned I now see the issue where you used the save button for the "Advanced Options" section instead of the "Actions" Section.

Also on a side note, I haven't seen LimeWire in nearly 20 years.

 

[maghuro]

This falls under user error. Take a closer look at the WebGUI to familiarize yourself with the page layout before you continue testing. There are 3 distinct sections. Each of the 2 bottom sections contains its own "Save" button that applies ONLY to that specific section. If you modify a field value from one section and click on the "Save" button from a different section, the value won't change. You must use the corresponding "Save" button on each specific section of the WebUI for the new parameter to take effect.

Oh... I see...

So this "bug" became user not-friendly interface report...

 

[maghuro]

Just checked the video out, and as Martinski mentioned I now see the issue where you used the save button for the "Advanced Options" section instead of the "Actions" Section.

Also on a side note, I haven't seen LimeWire in nearly 20 years.

Take your time, fella .. have a good rest...

LimeWire was a quick "file upload" search on Google. I was surprised too