MerlinAU MerlinAU v1.4.1 - 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!