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

[ExtremeFiretop]

Upgraded from 1.3.10 to 1.4.0 using the force update before grabbing the develop version. Could it be that it’s because I’m running in AP mode?

Actually having a closer look at your screenshot, your missing the "AiMesh Node(s) Info" menu option, on the shell script's main menu, which means it's being detecting as running on an AiMesh node.
Basically that confirms that theory.

 

[Martinski]

... Could it be that it’s because I’m running in AP mode?

Yes, that's definitely what's preventing the WebUI page from being mounted, but I just made a change in the shell script to allow the web page to be mounted on APs as well.

If you're willing to test/validate this latest change, you can update the script with the following command:

/jffs/scripts/MerlinAU.sh forceupdate

Please let us know if it works well for you.

 

[ExtremeFiretop]

@vlord

I don't have an AP to validate this change, but @Martinski found the value from one of the routers he has access too.

Let us know if it works to mount the WebUI. Also if you could please report back if the "AiMesh Node(s) Info" menu option works as designed from the AP.

Thanks!

 

[vlord]

Probably. I don't think there's much distinction between AiMesh and AP mode in the nvram values we are using.
We can confirm by having you do a: nvram get sw_mode

If it returns as: 0 then that means it's basically thinking it's the same as an AiMesh node.
Which doesn't have a WebUI and shouldn't try to mount the page.

If it returns as 1; then it thinks it's in router mode.

I am getting 3 as the response

 

[vlord]

Yes, that's definitely what's preventing the WebUI page from being mounted, but I just made a change in the shell script to allow the web page to be mounted on APs as well.

If you're willing to test/validate this latest change, you can update the script with the following command:

/jffs/scripts/MerlinAU.sh forceupdate

Please let us know if it works well for you.

Just tried this and still getting the same. Tried restarting httpd which didn’t make any difference either

 

[ExtremeFiretop]

I am getting 3 as the response

Yeah, that's the value that @Martinski used / found on the router he has access too*.

Just tried this and still getting the same. Tried restarting httpd which didn’t make any difference either

Restarting httpd shouldn't be required, at worst a refresh / logout and login again for it to show.
I'm surprised your still having the issues. Did you manage to grab a screenshot this time of the update process?

Today was a day off for me and I expected to have time to work on this but got busy.
I'll do so more investigations with @Martinski when possible.

 

[Martinski]

Just tried this and still getting the same. Tried restarting httpd which didn’t make any difference either

Here's a partial screenshot showing the WebGUI page mounted & working fine on a router operating as an AP.

 

[ExtremeFiretop]

@vlord

Without logs and screenshots we are just guessing what flow you and the script are taking unfortunately. Running while blindfolded.
As @Martinski mentioned above it seems to work with the latest changes.

It would be extremely helpful if you could provide both logs from the Syslogs around the update process time, or Screenshots of the update process when you ran forceupdate.

Also, if you could report back on the AiMesh menu functionality I requested as well that would be extremely valuable.
Does the menu option show on an AP?
If so and you load the menu, do you see the AP itself, other APs/nodes or nothing? If it loads other devices, does it include the primary router?

Thanks

 

[vlord]

@vlord

Without logs and screenshots we are just guessing what flow you and the script are taking unfortunately. Running while blindfolded.
As @Marinski mentiones above it seems to work with the latest changes.

It would be extremely helpful if you could provide both logs from the Syslogs around the update process time, or Screenshots of the update process when you ran forceupdate.

Also, if you could report back on the AiMesh menu functionality I requested as well that would be extremely valuable.
Does the menu option show on an AP?
If so and you load the menu, do you see the AP itself, other APs/nodes or nothing? If it loads other devices, does it include the primary router?

Thanks

Whatever changed since I last posted made it working now. I just did another forceupdate and it immediately showed the webUI menu.

 

[ExtremeFiretop]

Whatever changed since I last posted made it working now. I just did another forceupdate and it immediately showed the webUI menu.

Nothing changed on our side fortunately since the last post.

Did you have the Ai Mesh Nodes menu on the AP?

 

[vlord]

Loving this! Here are my thoughts on the UI UX and other items.

1. Suggest collapsing all configuration items into their own section with a single save button. It all fits within a single screen so really no need to separate them out into different sections.
2. Move the action buttons to their own section and stack them in rows vs columns. scMerlin is a good example.
3. Clicking on latest changelog will open a new window but if you go back to the original window, you can see it’s applying some setting. That seems to be a bug. If possible, can you open the changelog in a modal/overlay panel similar to the “view list” in the network map page rather than a new window?
4. Why does selecting check for firmware update result in settings being applied? I’m not quite sure what was happening during those 60 seconds or so it was applying settings.
5. The three action buttons have two that are related (FW Update Check and Latest Changelog) and one that isn’t (Uninstall). It should be clear what buttons are related to what action FW controls vs MerlinAU actions. If you move these to their own dedicated actions section, you could also add a control for forcing MerlinAU update

 

[vlord]

Nothing changed on our side fortunately since the last post.

Did you have the Ai Mesh Nodes menu on the AP?

Yes. I believe all APs have the Ai mesh Nodes menu

 

[ExtremeFiretop]

Yes. I believe all APs have the Ai mesh Nodes menu

No; I mean in the shell script.
Please check my previous responses. Quoted below.

@vlord
Also if you could please report back if the "AiMesh Node(s) Info" menu option works as designed from the AP.

Thanks!

Also, if you could report back on the AiMesh menu functionality I requested as well that would be extremely valuable.
Does the menu option show on an AP?
If so and you load the menu, do you see the AP itself, other APs/nodes or nothing? If it loads other devices, does it include the primary router?

Thanks

 

[ExtremeFiretop]

1. Suggest collapsing all configuration items into their own section with a single save button. It all fits within a single screen so really no need to separate them out into different sections.

1. See previous responses below to dave related to the choice of having multiple sections with a save button for each:

I myself thought it was pretty intuitive when I designed the original interface to have a save for each section.
The thought is to have it similar to how MerlinAU has a main menu and an "Advanced Options" menu both with their own set of options to save.

It's just a design choice, the idea behind it is simply to maintain separation of the settings mostly.

2. Move the action buttons to their own section and stack them in rows vs columns. scMerlin is a good example.

2. Not sure I'm following; I think the previous responses above probably covered it. If not maybe a screenshot of what you mean.

3. Clicking on latest changelog will open a new window but if you go back to the original window, you can see it’s applying some setting. That seems to be a bug. If possible, can you open the changelog in a modal/overlay panel similar to the “view list” in the network map page rather than a new window?

3. Not a bug; working as designed.
It needs to fetch the log before it can be viewed, we open the window, fetch the log in the background, and when it's ready to display; we do so in the new window.
The "view list" in network map is using information the router already has available so it can be displayed instantly in comparsion.

4. Why does selecting check for firmware update result in settings being applied? I’m not quite sure what was happening during those 60 seconds or so it was applying settings.

4. It's either checking for updates; Using the same logic as option 1 in the Shell script, or flashing the firmware using that same logic as well.
It's up to the shell script to decide during those 60 seconds if it will report an update if one becomes available; or flash the firmware.... based on how it's configured.
(i.e was a postpone period set? was the bypass postpone enabled when it checked? is the changelog block enabled? is there high risk phrases that need approval? etc.)

You should have a popup confirmation of a similar effect when you click the button:

I also believe this previous response I provided to you may help clarify:

With my current implementation you could click the check update button, and if there is a postpone period it would just update the webpage to advise the version found and the expected update date.
If you don't have a postpone period set, it would run the entire update process right away when you click check for updates (after giving a warning that it will log you out of the WebUI of course!)

5. It should be clear what buttons are related to what action FW controls vs MerlinAU actions. If you move these to their own dedicated actions section, you could also add a control for forcing MerlinAU update

5. They are all MerlinAU actions. Adding a control for updating MerlinAU isn't a bad idea though. Might add that to the to-do list. Thanks for the suggestions!
Clicking the "F/W Update Check" button is triggering the same thing as MerlinAU option (1) from the Shell script.
Checking latest changelogs is the same as MerlinAU option main menu --> Log Options (lo) --> View Latest F/W Changelog (cl) in the shell script.

 

[vlord]

No; I mean in the shell script.
Please check my previous responses. Quoted below.

Yes. It shows the other two nodes including the router

 

[ExtremeFiretop]

Yes. It shows the other two nodes including the router

Thanks for testing and confirming; we will likely block this from functioning on the AP.
Really the AP should be considered/treated the same as an AiMesh node to MerlinAU shell script. (With the exception of mounting the WebUI)

 

[ExtremeFiretop]

WELL FOLKS!

We have been busy behind the scenes. Below are recent updates to the DEVELOP branch.

MerlinAU Version 1.4.0 is still unreleased at this time; and only available for beta testing.
If you are currently on the production version 1.3.10 or develop 1.4.0; you may update to test these changes below using the following commands:

- v1.3.10 (update with)

sh /jffs/scripts/MerlinAU.sh develop

- v1.4.0 (update with)

sh /jffs/scripts/MerlinAU.sh forceupdate

We request any 1.4.0 testers to try the new changes below and report back.
Thanks!

PR: [ #421] - Improved Symmetry

• I changed the location of the "Changelog Approval" setting value under the firmware status section.
• Every other setting in the setting section, is a setting the user controls and won't change without user control... While other values in the firmware status section is dynamic and can change without user action, aka, going from TBD to Blocked. And then from Approved back to TBD.

PR: [ #422] - Minor Cleanup

• Some minor changes to get "clean" code via the Linter tool.
• (Thanks @Martinski4GitHub @Martinski)

PR: [ #423] - Minor Fixes

• Fixed a rare and uncommon "post email upgrade" bug we found back in January.
• Added a check to validate the downloaded firmware version by MerlinAU is in fact the version found by the router's webs_update.sh script.
• (Essentially blocking accidential downgrades if a firmware is issued and recalled)
  
  
  

PR: [ #424] - Typo Correction

• Fixed a long standing bug with the firmware decompression validation step, which allowed the script to continue even if the firmware unzip process failed for some reason.

PR: [ #425] - Test WebGUI Support in AP Mode.

• Martinski made a tweak to test/validate WebGUI support when router is in AP Mode. Reported by @vlord
• (Thanks @Martinski4GitHub @Martinski)

PR: [ #426] - Improvements to support APs

• (This was to address a concern of mine where an AP would show the AiMesh nodes menu and run in "Primary router" mode.)
• Martinski made changes so that we can handle specific functionality or features based on whether the router is operating in "Router Mode" (i.e. Primary router) or in "AP Mode."
• This allows us to determine whether the WebGUI should be mounted or whether the AiMesh nodes should be handled only by the Primary router.
• Added WebUI Tab URL info to the CLI "About" page.
• (Thanks @Martinski4GitHub @Martinski)
  
  
  

PR: [ #427] - Cleanup Changelog Flow in WebUI

• I changed the visuals of the "Latest Changelog" button in the WebUI at the request of @vlord
• The process is more or less the same, but it will now open in an overlay instead of a new window, and won't display as though it's applying any setting.
  
  
  
  
  
  

PR: [ #428] - Change Layout For Single Save Button

• Change layout for a single save button:
  1. It's caused confusion for @maghuro from his mobile
  2. @dave14305 commented it doesn't follow the usual standards
  3. @vlord requested it as well
• Frankly; I don't care enough about the original design to explain forever; So be it, It only ended up the original way because it developed that way as I was playing and learning with the project.
  
  
  

 

[ExtremeFiretop]

Quick patch to the WebUI to fix a bug when saving the settings in commit: https://github.com/ExtremeFiretop/M...mmit/069413f01e8cd22ca85e77890c35f3a974cd7695
Accidently introduced after changing the layout.

 

[visortgw]

Quick patch to the WebUI to fix a bug when saving the settings in commit: https://github.com/ExtremeFiretop/M...mmit/069413f01e8cd22ca85e77890c35f3a974cd7695
Accidently introduced after changing the layout.

Have you considered implementing automatic updates of the development branch when develop is installed, and Auto-Updates for MerlinAU Script is enabled?

 

[ExtremeFiretop]

Have you considered implementing automatic updates of the development branch when develop is installed, and Auto-Updates for MerlinAU Script is enabled?

All we would need to do is increment the version with each new PR, but that's generally not how we handle versioning

All of these PRs are in the dev branch and all these changes are still under the "version 1.4.0" until released.