Tutorial: Making your first add-on

So you've got Home Assistant going and you've been enjoying the built-in add-ons but you're missing this one application. Time to make your own add-on!

To get started with developing add-ons, we first need access to where Home Assistant looks for local add-ons. For this you can use the Samba or the SSH add-ons.

For Samba, once you have enabled and started it, your Home Assistant instance will show up in your local network tab and share a folder called "addons". This is the folder to store your custom add-ons.

tip

If you are on macOS and the folder is not showing up automatically, go to Finder and press CMD+K then enter smb://homeassistant.local

For SSH, you will have to install it. Before you can start it, you will have to have a private/public key pair and store your public key in the add-on config (see docs for more info). Once started, you can SSH to Home Assistant and store your custom add-ons in the /addons directory.

Once you have located your add-on directory, it's time to get started!

Step 1: The basics

• Create a new directory called hello_world
• Inside that directory create three files:
  • Dockerfile
  • config.yaml
  • run.sh

The Dockerfile file

This is the image that will be used to build your add-on.

ARG BUILD_FROM
FROM $BUILD_FROM

# Copy data for add-on
COPY run.sh /
RUN chmod a+x /run.sh

CMD [ "/run.sh" ]

The config.yaml file

This is your add-on configuration, which tells the Supervisor what to do and how to present your add-on.

For an overview of all valid add-on configuration options have a look here

name: "Hello world"
description: "My first real add-on!"
version: "1.0.0"
slug: "hello_world"
init: false
arch:
  - aarch64
  - amd64
  - armhf
  - armv7
  - i386

The run.sh file

This is the script that will run when your add-on starts.

#!/usr/bin/with-contenv bashio

echo "Hello world!"

note

Make sure your editor is using UNIX-like line breaks (LF), not DOS/Windows (CRLF).

Step 2: Installing and testing your add-on

Now comes the fun part, time to open the Home Assistant UI and install and run your add-on.

• Open the Home Assistant frontend
• Go to "Settings"
• Click on "Add-ons"
• Click "Add-on store" in the bottom right corner.

• On the top right overflow menu, click the "Check for updates" button
• Refresh your webpage when needed
• You should now see a new section at the top of the store called "Local add-ons" that lists your add-on!

• Click on your add-on to go to the add-on details page.
• Install your add-on
• Start your add-on
• Click on the "Logs" tab, and refresh the logs of your add-on, you should now see "Hello world!" in your logs.

I don't see my add-on?!

Oops! You clicked "Check for updates" in the store and your add-on didn't show up. Or maybe you just updated an option, clicked refresh and saw your add-on disappear.

When this happens, try refreshing your browser's cache first by pressing Ctrl + F5 (Windows/Linux) or Cmd + Shift + R (macOS). If that didn't help, it means that your config.yaml is invalid. It's either invalid YAML or one of the specified options is incorrect. To see what went wrong, go to "Settings" → "System" → "Logs" and select "Supervisor" in the top-right drop-down menu. This should bring you to a page with the logs of the supervisor. Scroll to the bottom and you should be able to find the validation error.

Once you fixed the error, go to the add-on store and click "Check for updates" again.

Step 3: Hosting a server

Until now we've been able to do some basic stuff, but it's not very useful yet. So let's take it one step further and host a server that we expose on a port. For this we're going to use the built-in HTTP server that comes with Python 3.

To do this, we will need to update our files as follows:

• Dockerfile: Install Python 3
• config.yaml: Make the port from the container available on the host
• run.sh: Run the Python 3 command to start the HTTP server

Update your Dockerfile:

ARG BUILD_FROM
FROM $BUILD_FROM

# Install requirements for add-on
RUN \
  apk add --no-cache \
    python3

# Python 3 HTTP Server serves the current working dir
# So let's set it to our add-on persistent data directory.
WORKDIR /data

# Copy data for add-on
COPY run.sh /
RUN chmod a+x /run.sh

CMD [ "/run.sh" ]

Add "ports" to config.yaml. This will make TCP on port 8000 inside the container available on the host on port 8000.

name: "Hello world"
description: "My first real add-on!"
version: "1.1.0"
slug: "hello_world"
init: false
arch:
  - aarch64
  - amd64
  - armhf
  - armv7
  - i386
startup: services
ports:
  8000/tcp: 8000

Update run.sh to start the Python 3 server:

#!/usr/bin/with-contenv bashio

echo "Hello world!"

python3 -m http.server 8000

Step 4: Installing the update

Since we updated the version number in our config.yaml, Home Assistant will show an update button when looking at the add-on details. You might have to refresh your browser or click the "Check for updates" button in the add-on store for it to show up. If you did not update the version number, you can also uninstall and install the add-on again. After installing the add-on again, make sure you start it.

Now navigate to http://homeassistant.local:8000 to see our server in action!

Bonus: Working with add-on options

In the screenshot, you've probably seen that our server only served up 1 file: options.json. This file contains the user configuration for this add-on. Because we specified two empty objects for the options and schema keys in our config.yaml, the resulting file is currently empty.

Let's see if we can get some data into that file!

To do this, we need to specify the default options and a schema for the user to change the options. Change the options and schema entries in your config.yaml with the following:

...
options:
  beer: true
  wine: true
  liquor: false
  name: "world"
  year: 2017
schema:
  beer: bool
  wine: bool
  liquor: bool
  name: str
  year: int
...

Reload the add-on store and re-install your add-on. You will now see the options available in the add-on config screen. When you now go back to our Python 3 server and download options.json, you'll see the options you set. Example of how options.json can be used inside run.sh

Bonus: Template add-on repository

We maintain a full template example repository for add-ons you can use to get started. You can find that in the home-assistant/addons-example repository.