[ADDONS]Support Page[ADDONS]

[miroco]

I've got an RT-AC86U on FW 384.15. I ran a factory default on it after the FW upgrade. It's configured as an AP from the ground up. I have tried the suggested steps to make "Addons" appear, but no dice. Any suggestions?

 

[AndreiV]

I've got an RT-AC86U on FW 384.15. I ran a factory default on it after the FW upgrade. It's configured as an AP from the ground up. I have tried the suggested steps to make "Addons" appear, but no dice. Any suggestions?

I would think that in AP mode you won't see "Addons" as that is used in router mode.

 

[miroco]

I would think that in AP mode you won't see "Addons" as that is used in router mode.

That's strange. I followed the discussions on the alfa and beta builds, but I can't recall that the feature was router only?

 

[L&LD]

@miroco what scripts do you have running on that AP?

A simple/wired AP or in AiMesh mode?

 

[Clark Griswald]

@miroco My Router shows all tabs, yet in AP Mode the "addons" tab (and others) do not. I am only running the scripts on my Main.

 

[miroco]

@miroco what scripts do you have running on that AP?

I haven't gotten that far in the thought process, partly because the FW is just days old. The second reason is that the scripts now are part of the FW lowering the threshold to actually take advantage of them, which I think is great. Not to forget future "Addons".

It's a simple wired setup.

 

[L&LD]

@miroco, no, the scripts themselves are not part of the firmware.

amtm is (and is the recommended/official way now to install Entware).

 

[miroco]

Thank you for clearing up my misunderstanding

Well, I took amtm for a spin.

 

[Stevens243]

In an attempt to clarify the AP question here; you won't see/run scripts nor see addon tab on the AP. Access Points are sub-element in a network and you should have a router running in router mode. The router and everything connected to it (including the AP) will benefit from the scripts running on the router UNLESS you specifically stop that from happening from within the router settings (like bypassing VPN for specific devices, etc).

This is true for a traditional AP and an AIMesh node.

 

[miroco]

Thanks. That explains why Xentrk's remedy for making "Addons" appear, wasn't applicable in my use case.

https://www.snbforums.com/threads/addons-support-page-addons.61723/#post-549432

 

[Jack Yaz]

As a heads up, I will be shortly pushing updates to all jy scripts - you must update all of them (ignore any error messages during updates after the first script). You can then either reboot, or run

rm -rf /www/user/shared-jy && rm -rf /jffs/addons/shared-jy

then open any jy script you have installed and run 1 further update.

This will hopefully be the last time any of this messing around is needed - I'm switching to a single archive for all shared-jy resources to ease the pain of any new files that are needed in the future.

 

[L&LD]

I had a feeling this was coming. Thank you @Jack Yaz!

 

[Jack Yaz]

As a heads up, I will be shortly pushing updates to all jy scripts - you must update all of them (ignore any error messages during updates after the first script). You can then either reboot, or run

rm -rf /www/user/shared-jy && rm -rf /jffs/addons/shared-jy

then open any jy script you have installed and run 1 further update.

This will hopefully be the last time any of this messing around is needed - I'm switching to a single archive for all shared-jy resources to ease the pain of any new files that are needed in the future.

The update is now live.

With this update, if you are running my other scripts (connmon, ntpmerlin, spdmerlin, uiDivStats, modmon), you MUST update these as well. Ignore any error messages during updates after the first script (it will mention too many levels of symbolic links), and let the update complete.

Once you have updated all of the scripts, run

rm -rf /www/user/shared-jy && rm -rf /jffs/addons/shared-jy

then open any of the scripts mentioned above and run 1 further update.

This will hopefully be the last time any of this messing around is needed - I'm switching to a single archive for all shared-jy resources to ease the pain of any new files that are needed in the future. Please accept my apologies for the inconvenience!

 

[Jack Yaz]

IMPORTANT

With my next batch of script updates, there is a new minimum version requirement: Merlin 384.15/384.13_4 or Fork 43D1

This is so that only user.asp pages are used, and not overriding unused ASP pages

 

[dave14305]

Fork 42E7

It will require Fork 43D1 (Dev build) or whatever the next public release is called. This is for the easy page integration to the addons tab.

 

[Jack Yaz]

It will require Fork 43D1 (Dev build) or whatever the next public release is called. This is for the easy page integration to the addons tab.

Thanks, updated

 

[chongnt]

Hi, I noticed that your Addons tab naming is different from what I am getting. Yours shows Diversion Stats, Uptime Monitoring, NTP Daemon. Whereas mine shows uiDivStats, connmon, ntpMerlin.

When I was running John fork on N66U, I am able to make the change by edit user*.title under /tmp/var/wwwext to match your naming convention. However, in AC86U, edit the same file has no effect on the addon tab naming. How do I do that?

 

[SomeWhereOverTheRainBow]

Hi, I noticed that your Addons tab naming is different from what I am getting. Yours shows Diversion Stats, Uptime Monitoring, NTP Daemon. Whereas mine shows uiDivStats, connmon, ntpMerlin.

When I was running John fork on N66U, I am able to make the change by edit user*.title under /tmp/var/wwwext to match your naming convention. However, in AC86U, edit the same file has no effect on the addon tab naming. How do I do that?View attachment 29622

The tabs have gone through name changes per individual script developers design and are in no way customizable.

 

[dave14305]

When I was running John fork on N66U, I am able to make the change by edit user*.title under /tmp/var/wwwext to match your naming convention. However, in AC86U, edit the same file has no effect on the addon tab naming. How do I do that?

John’s fork handles add-on tabs differently than Merlin, since the older ASUS WebUI in the fork wasn’t as easy to manipulate tabs.

 

[chongnt]

The tabs have gone through name changes per individual script developers design and are in no way customizable.

John’s fork handles add-on tabs differently than Merlin, since the older ASUS WebUI in the fork wasn’t as easy to manipulate tabs.

Thanks @SomeWhereOverTheRainBow and @dave14305 for your explanation.
I will leave the tabs naming as it is.