+ + 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! In Hass.io 0.24 we introduced the option to have local add-ons be build on your device. This is great for developing new add-ons locally.
+To get started with developing add-ons, we first need access to where Hass.io looks for local add-ons. You can choose to either enable the Samba add-on for this or use the SSH add-on. 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:
FROM %%BASE_IMAGE%%
+
+ENV VERSION %%VERSION%%
+ENV LANG C.UTF-8
+
+# Copy data for add-on
+COPY run.sh /
+RUN chmod a+x /run.sh
+
+CMD [ "/run.sh" ]
+config.json:
{
+ "name": "Hello world",
+ "version": "0.1",
+ "slug": "hello_world",
+ "description": "My first real add-on!",
+ "startup": "before",
+ "boot": "auto",
+ "options": {},
+ "schema": {}
+}
+run.sh:
echo Hello from my first add-on!
+Step 2: Installing and testing your add-on
+Now comes the fun part, time to open the Hass.io UI and install and run your add-on.
+-
+
- Open the Home Assistant frontend +
- Go to the Hass.io panel +
- On the top right click the shopping basket to go to the add-on store. +
+
+From the Hass.io main panel open the add-on store.
+
-
+
- On the top right click the refresh button +
- You should now see a new card called “Local” that lists your add-on! +
+
+The Hass.io add-on store will list all available local add-ons.
+
-
+
- Click on your add-on to go to the add-on details page. +
- Install your add-on +
- Start your add-on +
- Refresh the logs of your add-on, you should now see “Hello world!” in your logs. +
+
+The add-on will print Hello world to the logs and then quit.
+
I don’t see my add-on?!
+Oops! You clicked refresh 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, it means that your config.json is invalid. It’s either invalid JSON or one of the specified options is incorrect. To see what went wrong, go to the Hass.io panel and in the supervisor card click on “View logs”. 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 refresh 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.json: Make the port from the container available on the host
+ run.sh: Run the Python 3 command to start the HTTP server
+
Add to your Dockerfile before RUN:
# Install requirements for add-on
+RUN apk add --no-cache python3
+
+# Set directory for Python 3 HTTP server to serve
+WORKDIR /data
+Add “ports” to config.json. This will make TCP on port 8000 inside the container available on the host on port 8000.
{
+ "name": "Hello world",
+ "version": "0.2",
+ "slug": "hello_world",
+ "description": "My first real add-on!",
+ "startup": "before",
+ "boot": "auto",
+ "options": {},
+ "schema": {},
+ "ports": {
+ "8000/tcp": 8000
+ }
+}
+Update run.sh to start the Python 3 server:
python3 -m http.server
+Step 4: Installing the update
+Since we updated the version number in our config.json, Home Assistant will show an update button when looking at the add-on details. You might have to refresh your browser or click the refresh 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://hassio.local:8000] to see our server in action!
+
+
+The Python 3 server will allow you to browse the /data folder.
+
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 an empty “config” and “schema” in our config.json, the 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.json 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"
+ },
+
+ …
+}
+Refresh 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.