I can´t find to model TP-LINK EC230-G1 version 1.0
exist any compatible ????
Thanks
This is a convenient tool! It would be nice to be able to check the new version of OpenWrt for my device.
This device does not seem to be supported by OpenWrt.
The link to the wiki is there. But the link scheme is not consistent enough, as such, the link utilizes the wiki search.
Would have been nice if you finally added gpg-signed checksum files. Currently you only provide a raw checksum which at best ensures that the file was downloaded correctly yet does nothing to protect from malicious code in case someone gains admin access to your website.
2 Likes
Hello, thanks for the project!
May I add some suggestion?
It would be useful also to have accompanying luci plugin to check for updates from within the device itself, as it already "knows" it's own name for sure and it would free up humans from error-prone "best guess" work 
1 Like
This has been cross posted multiple times. However I’m happy to answer it here again. Vanilla images aren’t aware that they are… vanilla. So the app can’t know if it should request the buildbot image (vanilla) or a custom image (because of a different package selection).
While it’s possible to offer two buttons saying “install custom” and “install vanilla”, people will end up installing vanilla images and losing modification without knowing.
The current implementation tries to be as user friendly as possible to make sure a sysupgrade doesn’t break things.
Now the argument is that the sysupgrade service can’t be trusted because it’s not the buildbots. For that we should work on the reproducibility of OpenWrt images so that whatever image the service (and buildbot really) creates, it’s verifiable.
3 Likes
How about a red !WARNING! along with “install vanilla” button?
That might be a long term task.
I tried to ask what's missing and how long would it take to fix it but didn't get even overage impression.
Maybe nobody even knows..
And until it didn't happen, the solution might be just a red warning along with additional button.
Just noticed that BT Home Hub 5 Type A is listed as British Telecom Home Hub 5 Type A. I think it's best to list it as BT, as this is the name that people will look for (and also previous models are listed as BT).
Loos good, thanks!
not seem and not support by OpenWrt
Is there an API to automate the download of the latest available image?
Got it with vanilla checksums using profiles.json suggested by @anon50098793.
The attended-sysupgrade server at https://github.com/aparcar/asu has an API documented at: https://sysupgrade.openwrt.org/ui/ This might help.
1 Like
Hi folks, the translations for the firmware selector is missing some translations.
Please have a look here and search for // missing in https://github.com/mwarning/openwrt-firmware-selector/blob/master/www/i18n.js, or just check if the existing translations match the English ones that we use as primary source.
Make a merge request on the github repository or create an issue or send it as a PM. I will make sure that it will be added to the official OpenWrt gitlab repository as well.
Thank you very much and have a nice vacation. o/
Regarding translations, has OpenWrt considered Transifex? They have a free opensource project plan.
Transifex does not support the translation format of the firmware selector. I tried to change the input file format to make it acceptable. But the trial and error got tiresome. And then I could not remove the uploaded resources. It is a mess.
If someone wants to use Transifex, please do and then make a merge request on github or gitlab.
1 Like
I'd prefer to use Weblate since we already use it for the LuCI web interface.
It does seem to support JSON files, would you mind to check it out? https://docs.weblate.org/en/latest/formats.html#json