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

[aex.perez]

You definitely need to comment in the FW release thread(s), if only to see if there’s a lightbulb moment amongst other users.

Sure must, just redid the setup on the Samsung soundbar. Didn't change a thing, exact same setup and now connected. Odd thing it wasn't even showing up on the offline list of devices on the router. Washer shoud have failed, I half expected it to fail, but it connected right up.

I'm sure there's a reason, I can't figure it out, there's no pattern to it, even downgrading to 388.8-4 doesn't fix it without a WPS reset, and then mostly (but not exclusively) on the nodes to use as a clue.

But now all done, everything connected and distributed to the Router and Nodes as they should be and were under 388.8-4
So went ahead and updated my Signature

 

[ExtremeFiretop]

A few of the devices that didn't connect (releatively new and can do WPA2/WPA3), I've had to go in and set them up, exactly the same as before and then they connected after I made the WPA2 change. The older one that should have a problem with that connected to the router but not to a node until I made the change to WPA2-Personal at the router for all the SSID's.

Just have one or two devices left, that even after a power cycle didn't conect that I anticipate will as soon as I reset them up, using the exact same settings as before

Just to put a bowtie on this and wrap it up before going back to official business with MerlinAU addon.
Heres what I did to get myself a successful upgrade (FINALLY!)

1. Downgraded back to the stable versions of 3006.102.3 for the primary, and 3004.388.8_4 for the node.
2. Factory reset on both, then restored them to their working config from the morning of April 9th.
3. Confirmed all my devices reconnected as expected; gave the network a few minutes to breath after a reboot.

4. Prepared my network (knowing that WPA2/WPA3-personal was no longer going to work) I disabled it from any network that had it on.
In my case, that was my guest network, and my standard -5GHz network. For the guest; I set to WPA3-personal, and for the 5GHz standard, I set to WPA2 personal. Rebooted.
5. Reauthenticated any devices that went offline due to the above WPA changes. In my case that was only my work device by chance lol. Reauthenticated it to use WPA2 again instead of WP3 and all was good.
6. Did the firmware upgrades again on the node to release 3004.388.9 and 3006.102.4_beta1 on the primary.
7. Held my breath and whoohoooo! Time to have a beer:

 

[aex.perez]

Just to put a bowtie on this and wrap it up before going back to official business with MerlinAU addon.
Heres what I did to get myself a successful upgrade (FINALLY!)

1. Downgraded back to the stable versions of 3006.102.3 for the primary, and 3004.388.8_4 for the node.
2. Factory reset on both, then restored them to their working config from the morning of April 9th.
3. Confirmed all my devices reconnected as expected; gave the network a few minutes to breath after a reboot.
View attachment 64933
4. Prepared my network (knowing that WPA2/WPA3-personal was no longer going to work) I disabled it from any network that had it on.
In my case, that was my guest network, and my standard -5GHz network. For the guest; I set to WPA3-personal, and for the 5GHz standard, I set to WPA2 personal. Rebooted.
5. Reauthenticated any devices that went offline due to the above WPA changes. In my case that was only my work device by chance lol. Reauthenticated it to use WPA2 again instead of WP3 and all was good.
6. Did the firmware upgrades again on the node to release 3004.388.9 and 3006.102.4_beta1 on the primary.
7. Held my breath and whoohoooo! Time to have a beer:
View attachment 64935

Unlike you I did't have to change a setting on any device, just refresh the setup. But like you, I've a few beers ready to go. Just in time as the wife walks in.

Now, I'm tempted to play with fate tomorrow and change the SSID's at the router, to update the nodes, back to WPA2/WPA3-Personal to see what happens.
Maybe even shorten some of the device names to fix this (cleared and refreshed browser) ;

Update: jumped the proverbial gun, shorterning the longer names, which also fixed the already shorter names

 

[mxxcon]

I just installed this not realizing that my router is not supported. How do I uninstall this script now? Even "MerlinAU.sh uninstall" refuses to run saying my router is not supported.

 

[ExtremeFiretop]

Here is the email:

Nvm; I got enough from the last post to find the problem in the code;
Will submit a PR to version 1.4.2 in dev shortly.

Hi @nlurker

I've created PR: 453 for this issue to be merged in 1.4.2
Thanks!

 

[ExtremeFiretop]

I just installed this not realizing that my router is not supported. How do I uninstall this script now? Even "MerlinAU.sh uninstall" refuses to run saying my router is not supported.

Did you try the interactive menu? Screenshots of what your talking about would go a long way.

Edit: nvm: i got it; will provide an update shortly.

 

[ExtremeFiretop]

I just installed this not realizing that my router is not supported. How do I uninstall this script now? Even "MerlinAU.sh uninstall" refuses to run saying my router is not supported.

Hi @mxxcon

I just added the fix for the uninstall in the same PR.
Run the following to be able to uninstall:

curl --retry 3 "https://raw.githubusercontent.com/ExtremeFiretop/MerlinAutoUpdate-Router/refs/heads/dev/MerlinAU.sh" -o "/jffs/scripts/MerlinAU.sh" && chmod 755 "/jffs/scripts/MerlinAU.sh"

 

[mxxcon]

Hi @mxxcon

I just added the fix for the uninstall in the same PR.
Run the following to be able to uninstall:

curl --retry 3 "https://raw.githubusercontent.com/ExtremeFiretop/MerlinAutoUpdate-Router/refs/heads/dev/MerlinAU.sh" -o "/jffs/scripts/MerlinAU.sh" && chmod 755 "/jffs/scripts/MerlinAU.sh"

That worked, thank you.

 

[ExtremeFiretop]

That worked, thank you.

Thank you for reporting!

 

[ExtremeFiretop]

MerlinAU 1.4.2 Released!

What's Changed/Fixed?:

PR: [ #451 ] - Minor Fixes and Additions
-After the Router PWD is set we now add a successfully tested or unvalidated result to main menu.

-Change the wording for the update process to fix nitpicks related to "anyways" vs "anyway" as reported by: @jksmurf here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-950762
-Update Minimum Versions to 3 behind production

• Version"3004.386.13.2" for the 386 branch;
• Version "3004.388.8.0" for the 388 branch
• Version "3004.388.8.2" for the 3006.102 branch

-Fix the WebUI status for the changelog approval being "Disabled" instead of "TBD"

-Fixes some visual nitpicks of the WebUI

PR: [ #452 ] - Code Improvements
-Make sure the "FW_New_Update_Changelog_Approval" option is initialized properly under all circumstances.
-Show the Password "Verified" status in GREEN = GOOD.

-Minor cleanup.
(Thanks @Martinski4GitHub / @Martinski )

PR: [ #453 ] - Fix Changelog and Email Notifications and Patch Uninstall
-Fix a report from @nlurker for blank changelog URLs in the email notifications: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-951011
The Changelog check (pre-approval) was not running before the email notification with the run_now parameter.
-Quick fix to allow uninstall of the script when installed on unsupported routers as reported by @mxxcon here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-951128

PR: [ #454 ] - Improvement
-Miscellaneous code improvements.
(Thanks @Martinski4GitHub / @Martinski )

PR: [ #455 ] - Fixes and Code Improvements
-Improved uninstallation workflow when users attempt to install MerlinAU on unsupported routers.
-Now the code will automatically prompt users to uninstall immediately after informing them that their current router model is unsupported. In such scenarios, this provides users a quick & easy way to uninstall.

(Thanks @Martinski4GitHub / @Martinski )

As always, we highly recommend you update ASAP as this includes functional improvements and little bug fixes.

Thanks!

 

[jksmurf]

Change the wording for the update process to fix nitpicks related to "anyways" vs "anyway"

Get outta here .... I didn't get a mention for a real issue I picked up in the previous release but get an honourable mention for this bit of fun. You so funny .

 

[ExtremeFiretop]

MerlinAU 1.4.1 Released!

What's Changed/Fixed?:

PR: [ #449 ] - Patch Update Process
-Resolved some issues causing reports of having to run the update process twice, or reports of incorrectly identified updates.
Issues reported by @vlord here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-950588
And here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-950593

And @jksmurf here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-950590
And here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-950749

As always, we highly recommend you update ASAP as this includes important functional improvements and bug fixes.

Thanks!

@jksmurf

You mean this above?

 

[jksmurf]

@jksmurf

You mean this above?

Ok you got me…
Awesome stuff btw; loving the password is verified, green is good

 

[maghuro]

MerlinAU 1.4.2 Released!

What's Changed/Fixed?:

PR: [ #451 ] - Minor Fixes and Additions
-After the Router PWD is set we now add a successfully tested or unvalidated result to main menu.
View attachment 65016
-Change the wording for the update process to fix nitpicks related to "anyways" vs "anyway" as reported by: @jksmurf here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-950762
-Update Minimum Versions to 3 behind production

• Version"3004.386.13.2" for the 386 branch;
• Version "3004.388.8.0" for the 388 branch
• Version "3004.388.8.2" for the 3006.102 branch

-Fix the WebUI status for the changelog approval being "Disabled" instead of "TBD"
View attachment 65015
-Fixes some visual nitpicks of the WebUI

PR: [ #452 ] - Code Improvements
-Make sure the "FW_New_Update_Changelog_Approval" option is initialized properly under all circumstances.
-Show the Password "Verified" status in GREEN = GOOD.
View attachment 65017
-Minor cleanup.
(Thanks @Martinski4GitHub / @Martinski )

PR: [ #453 ] - Fix Changelog and Email Notifications and Patch Uninstall
-Fix a report from @nlurker for blank changelog URLs in the email notifications: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-951011
The Changelog check (pre-approval) was not running before the email notification with the run_now parameter.
-Quick fix to allow uninstall of the script when installed on unsupported routers as reported by @mxxcon here: https://www.snbforums.com/threads/m...auto-updater-gnuton-support.91326/post-951128

PR: [ #454 ] - Improvement
-Miscellaneous code improvements.
(Thanks @Martinski4GitHub / @Martinski )

PR: [ #455 ] - Fixes and Code Improvements
-Improved uninstallation workflow when users attempt to install MerlinAU on unsupported routers.
-Now the code will automatically prompt users to uninstall immediately after informing them that their current router model is unsupported. In such scenarios, this provides users a quick & easy way to uninstall.
View attachment 65018View attachment 65020
(Thanks @Martinski4GitHub / @Martinski )

As always, we highly recommend you update ASAP as this includes functional improvements and little bug fixes. Also as previously mentioned you must update to this version if you wish to have a smooth transition to the upcoming 1.4.0 release.

Thanks!

Awesome as always! Thanks for your dedication and good job.

Would be possible to receive an email notification whenever the script auto updates?

"Congratulations! The script successfully auto updated at X hours!"
"Oh no! An error occurred when trying to auto update. How is that possible? OMG, what a shame!"

 

[ExtremeFiretop]

Awesome as always! Thanks for your dedication and good job.

Would be possible to receive an email notification whenever the script auto updates?

"Congratulations! The script successfully auto updated at X hours!"
"Oh no! An error occurred when trying to auto update. How is that possible? OMG, what a shame!"

Yep no problem; being handled by PR: 458 for the next release.

Thanks!

 

[maghuro]

Yep no problem; being handled by PR: 458 for the next release.

View attachment 65050View attachment 65051

Thanks!

Hello,
Better is impossible. You don't know how much it helped my OCD

Just to clarify - it sends the "update available" email only when auto update is off, right? I'm asking because it doesn't make sense receiving a "update available" and immediately after that a "script updated"
My regards

 

[ExtremeFiretop]

Hello,
Better is impossible. You don't know how much it helped my OCD

Just to clarify - it sends the "update available" email only when auto update is off, right? I'm asking because it doesn't make sense receiving a "update available" and immediately after that a "script updated"
My regards

I think you mean to say when auto updates is on Not off.

If it's off, then AMTM handles script update notifications when the script is out of date. When auto updates are ON. Then AMTM will no longer send email updates since MerlinAU is always "up to date" and therefore requires the notifications when Auto Update is ON

 

[maghuro]

I think you mean to say when auto updates is on Not off.

If it's off, then AMTM handles script update notifications when the script is out of date. When auto updates are ON. Then AMTM will no longer send email updates since MerlinAU is always "up to date" and therefore requires the notifications when Auto Update is ON

Misinterpreted regarding my notable lacking of English skills
- scenario 1 - script auto updates are on - script auto updates and then sends an email saying "the script was successfully updated" (or failed the update). Not an email saying that an update is available, because it doesn't makes sense, as it updated automagically
- scenario 2 - script auto updates are off - only sends an email saying "an update is available", correct?

 

[ExtremeFiretop]

Misinterpreted regarding my notable lacking of English skills
- scenario 1 - script auto updates are on - script auto updates and then sends an email saying "the script was successfully updated" (or failed the update). Not an email saying that an update is available, because it doesn't makes sense, as it updated automagically

Currently it sends one saying it is available and then if it managed to update successful or not. So 2 emails with auto updates on within the script. First to say a new update is found, and second to say "update successful" or "update failed" as per your original request that's what it sounded like you wanted:

"Congratulations! The script successfully auto updated at X hours!"
"Oh no! An error occurred when trying to auto update. How is that possible? OMG, what a shame!"

We can cut that down to a single email of if it managed to succeed or not.

- scenario 2 - script auto updates are off - only sends an email saying "an update is available", correct?

We don't handle scenario 2 at all, as I mentioned that's handled by AMTM email notifications. We won't clash with AMTM email notifications and send duplicate notifications for the same thing. If auto updates is off. Script will fall out of date as soon as we release a new version, and AMTM will send an email notification, there is no purpose in us handling scenario 2.

 

[maghuro]

Currently it sends one saying it is available and then if it managed to update successful or not. So 2 emails with auto updates on within the script. First to say a new update is found, and second to say "update successful" or "update failed" as per your original request that's what it sounded like you wanted:



We can cut that down to a single email of if it managed to succeed or not.



We don't handle scenario 2 at all, as I mentioned that's handled by AMTM email notifications. We won't clash with AMTM email notifications and send duplicate notifications for the same thing. If auto updates is off. Script will fall out of date as soon as we release a new version, and AMTM will send an email notification, there is no purpose in us handling scenario 2.

Understood!

I think that , for the sake of simplicity, one email is sufficient - saying that an update was available and successfully installed