Firmware Selector "Handling `defaults` not enabled on server"

Hi, when i try to build a custom firmware for my tp link 840n v4 in firmware selector, i got this error. Why do this happen?

  • Are you referring to the Firmware Selector?
  • If so, are you trying adding custom default configs?

Details please?

Same for me:

  • Is that a yes?
  • If so, what happens with no defaults?

(Tagging @aparcar)

the builder builds only when no oci script is specified

2 Likes

the firmware selector only builds when no uci default code is added. i generally add a code so that when i reset openwrt the ssid will turn on automatically

2 Likes

Problem is still there. As soon as you use any uci-defaults script, the build fails.

4 Likes

Any news? :pray:

yeah.. what they said!

Is there a plan to fix the problem?

In my opinion this is a feature, not a bug.
First of all, we can see the savings in storage space on the server.
Because if the packages for the same device will share the same storage link on the server.
If anyone wants to further customize the settings, they must do it offline on the computer/vps

I'm not agree with you, when you've an app who crash with an error message, I can call it a bug nor an incident.

I know we are here on a community and everyone does her best :blush:

@Darias if you've can explain us how to customize locally you'll be our super hero ! :star_struck:

2 Likes

I've made a formal request here, please spread the link and support it .

How is ASU related to the Firmware Selector issue?

Is this another issue?

The Imagebuilder docs were recently updated, and gives a well-detailed walkthrough of the process of customizing images locally :slight_smile:
I haven't tried it myself (I'd like a container image based on Alpine, maybe I'll make one?), but I'll give it a go in the coming days.

edit: There's also the Firmware-Selector, providing a graphical UX for the process after image-builder has finished (AFAICT)

edit 2: Hurray, there's already a fully featured docker image for ImageBuilder :tada:

Again the same problem, as soon as I add my starting script to the assembly
Handling 'defaults' not enabled on server

It is set to "False"