spdMerlin spdMerlin - v4.x - speedtest and bandwidth monitoring

[aletaziar]

Added to my post while you were typing - where did you get 4.4.7? Have I missed something?

GitHub - AMTM-OSR/spdMerlin: spdMerlin is an internet speedtest and monitoring tool for AsusWRT Merlin with charts for daily, weekly and monthly summaries. It tracks download/upload bandwidth as well as latency, jitter and packet loss.

spdMerlin is an internet speedtest and monitoring tool for AsusWRT Merlin with charts for daily, weekly and monthly summaries. It tracks download/upload bandwidth as well as latency, jitter and pac...

github.com

Note that the install command has a mistake, and should not have `/install` in the path.

 

[Ripshod]

Back to your original question then.
What we're all seeing is just the fact that we have 'develop' versions installed that haven't yet been released. Effectively we're running stable betas.

 

[Martinski]

After updating several scripts to the new versions hosted by the AMTM-OSR/spdMerlin organization, I'm getting this in AMTM after an update check. Not really sure if this is an amtm issue or a problem with the scripts not changing their update url and MD5.
View attachment 65982

No official announcement has been made by the AMTM-OSR team that the "orphaned" add-on repositories are now "open for business" and integrated with AMTM.

Work is still in progress (it's not like flipping a simple switch), so until an official announcement is made of the next production releases, any add-on scripts that you download from the current AMTM-OSR repositories may not yet be fully modified, tested, validated, and integrated with AMTM support.

I'd suggest uninstalling whatever scripts you have now installed from the AMTM-OSR repos and reinstalling the previous versions from their original repositories.

 

[ExtremeFiretop]

After updating several scripts to the new versions hosted by the AMTM-OSR/spdMerlin organization, I'm getting this in AMTM after an update check. Not really sure if this is an amtm issue or a problem with the scripts not changing their update url and MD5.
View attachment 65982

Spdmerlin isn't even hosted by us yet in AMTM. It still points to JackYaz for now.

Added to my post while you were typing - where did you get 4.4.7? Have I missed something?

Nope.

What does this person mean by they updated "several scripts"

The only ones ready is FlexQoS and scMerlin. Anything else they are just giving themselves problems and should wait until we pump out the updates through AMTM.

 

[aletaziar]

What does this person mean by they updated "several scripts"

"This person" is right here, and used the install script from the repos. Perhaps they should be changed to private or the readmes edited to say that they're not production ready if that's the case, since the new org's readme encourages browsing the repo list to "Explore our Repositories to see which scripts are currently hosted under our stewardship." The various repos themselves only give installation commands and instructions to go to SNB for issues.

But I have done what you recommended and rolled back.

 

[ExtremeFiretop]

"This person" is right here, and used the install script from the repos.

So this confirms you installed custom scripts outside of AMTM support. This would naturally explain any issues you experienced.

Perhaps they should be changed to private or the readmes edited to say that they're not production ready if that's the case, since the new org's readme encourages browsing the repo list to "Explore our Repositories to see which scripts are currently hosted under our stewardship."

Yes; you can absolutely browse to see what repos have been accepted into the stewardship. That doesn't mean they are ready, we have nothing to hide with the work we are doing, or the repos accepted by the team. Putting them private would serve no additional purpose and we are accepting code contributions from people from outside the team so that would actually be a disadvantage.

The various repos themselves only give installation commands and instructions to go to SNB for issues.

We could add a note to mention that are not production ready, but they soon will be anyways.

But I have done what you recommended and rolled back.

I understand the desire to run the latest and greatest, but all I can say is trust the process and they will soon be available to update through the regular update process.

 

[aletaziar]

So this confirms you installed custom scripts outside of AMTM support. This would naturally explain any issues you experienced.

It isn't as though I was just browsing Github and decided to copy-paste every install command I saw. My thought process went like this:
- AMTM notifies me of new updates
- I check the repos and realize it's a new org
- I look through the org's readme and see it has reputable people behind it, and that it has repos for several scripts I already use
- The repos have versions above what I currently have
- None of the repos mention that they are pre-production

We could add a note to mention that are not production ready, but they soon will be anyways.

Even if they'll be production ready soon, I think you might as well put a note in the readme. It's such a superficial change and easy to remove when production happens.

I understand the desire to run the latest and greatest, but all I can say is trust the process and they will soon be available to update through the regular update process.

I guess I thought I was following the process, because the org and and the readmes just give the bash install commands. They don't mention "just wait for AMTM".

Anyway, thank you for continuing support for these scripts. Every router update I was concerned scripts would stop working.

 

[ExtremeFiretop]

It isn't as though I was just browsing Github and decided to copy-paste every install command I saw. My thought process went like this:
- AMTM notifies me of new updates
- I check the repos and realize it's a new org
- I look through the org's readme and see it has reputable people behind it, and that it has repos for several scripts I already use
- The repos have versions above what I currently have
- None of the repos mention that they are pre-production

I can see the confusion thinking this is the process when you list it out like that.
But you would need to be a somewhat "advanced" user to go through those motions you listed; and would depend too much on people following what's developing on SNBForums and reading posts.
We wouldn't expect regular users to transition that way it would be a pretty "rough" transition due to this.

Even if they'll be production ready soon, I think you might as well put a note in the readme. It's such a superficial change and easy to remove when production happens.

Feedback received. It's really up to @thelonelycoder as he makes the calls; and he decides when AMTM is "ready" to push out the new scripts.

I guess I thought I was following the process, because the org and and the readmes just give the bash install commands. They don't mention "just wait for AMTM".

No worries; as I mentioned above I can see how you might of thought this was the process.
But we have a much more elegant solution in mind involving the scripts regular update functions to make it as seamless as possible for the regular user.

Anyway, thank you for continuing support for these scripts. Every router update I was concerned scripts would stop working.

We thank you for the feedback and for being eager to test the latest releases.