How would one customize wifi-connect UI?

If I were to build the BalenaDashboard project, what would I need to to to customize the wifi-connect ssid name (currently balenaDash), password, and logos/colors? Has anyone done this?

Hi @kingstonsteele to customize the SSID and password, its just a matter of changing them on this line . For the logos in wifi connect, its a bit more involved. Essentially you would need to use the --ui-directory flag as specified here and then point it to a customized version of the wifi connect UI code from here:

Hey thanks for the reply! So obviously changing the SSID and password was easy enough but could you give me a little more explanation on using command line arguments?

Hi @kingstonsteele ,

Sure. If you look at the repository for Wifi Connect, it includes a ui directory:

This includes the default UI for Wifi Connect, as well as the images it uses to display the UI. For reference, the company logos are here:

You can therefore include a copy of the ui directory, for example my_new_ui, including any changed images, HTML, etc. into your built image and ensure that the scripts/ script is updated to include the UI directory option, ie. ./wifi-connect --ui-directory my_new_ui. This will start Wifi Connect up using the new UI directory, including any changes you’ve made.

Hope this clears things up a bit. Let us know if you need any further help!

Best regards,


So here’s what I did but it doesn’t seem to have worked:

# Start wifi-connect with SSID "balenaDash", Password "balenaDash" and make it exit if no interaction happens within 10 minutes.
./wifi-connect --ui-directory /ui -a 600 -s balenaDash -p balena

This is with my ui folder being inside my wifi-connect at /ui

After this change, wifi-connect doesn’t start so I must be doing something very wrong here.

Hi @kingstonsteele can you comment out the /.wifi-connect ... line from the start script and then once the change is deployed, ssh into the device service and run that command manually from the terminal. This should give you logs and hopefully an error message to work from :slight_smile:


This is the result I’m getting:

Cannot get the NetworkManager service state
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: D-Bus error: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory (org.freedesktop.DBus.Error.FileNotFound)', /checkout/src/libcore/
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Ahh! okay @kingstonsteele are you running wifi-connect on raspbian or balenaOS? On balenaOS you need to have your start script define the env var where the dbus interface will be. You can see this here: and you need to enable dbus access for that service as done in the balenaDash project here:

How are you running your project, could you share code and we should be able to point out why dbus is not found.

Here is my docker compose:

version: '2'
    restart: always
    build: ./wpe
    privileged: true
      - 8080:8080
    restart: always
    build: ./scheduler
    privileged: true
    build: ./wifi-connect
    restart: always
    network_mode: host
    privileged: true
      io.balena.features.dbus: '1'
      io.balena.features.firmware: '1'
    privileged: true
    restart: always
    build: ./photos
      - "8888:8888"

My dbus line in start script looks like this:

export DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket

I just forked the balenaDash repository and then altered the start script for my UI

The project is here:

hmm, that all looks correct. What version of balenaOS are you running this on? Also before running the ./wifi-connect command manually again, can you check that the dbus ENV is accessible in the shell environment using printenv | grep DBUS_SYSTEM_BUS_ADDRESS. I suspect it should be, but best to check we are getting the correct errors, before we go chasing red herrings :stuck_out_tongue:

Hey, thanks for the quick responses here. I’m runing balenaOS 2.43.0+rev1.

There was no output from printenv | grep DBUS_SYSTEM_BUS_ADDRESS

ah, that means for some reason its not set in the terminal shell environment. Can you open a webterminal to the container and run these two commands in sequence:

export DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket

./wifi-connect --ui-directory /ui -a 600 -s balenaDash -p balena

So if I run that all it seems to run fine and put out wifi but the captive portal doesn’t actually show up. Basically back to this:

Hi there!
Can you share some journal logs from the wifi-connect service?

Here’s how we modify the UI - we store a copy of the UI directory in our repo:


Then in our Dockerfile.template we include a simple COPY command to overwrite the default UI:

FROM balenalib/%%BALENA_MACHINE_NAME%%-debian:stretch

RUN install_packages dnsmasq wireless-tools wget

WORKDIR /usr/src/app

RUN curl -s \
    | grep -hoP 'browser_download_url": "\K.*%%BALENA_ARCH%%\.tar\.gz' \
    | xargs -n1 curl -Ls \
    | tar -xvz -C /usr/src/app/

COPY . .

CMD ["bash", ""]

The downside to this approach is that changes in the source could break the UI when we overwrite it with our version, but those types of changes are rare.

I’ve created a sample repo by gathering some of the snippets found in this thread.

The first thing that I observed in your above screenshot is that the & the Dockerfile.template were inside the ui folder, so I moved them next to it. After that I also changed the to use --ui-directory ui argument (w/o a / before the ui) and also make sure to provide a password to the -p argument that is at least 8 chars long.

For testing I just added an extra header in the index.html and I was able to see that in the captive portal.
Let us know if you face any issues.