Table of Contents

  1. Introduction
  2. Preparations
  3. Installing
  4. Setting up and using Home Assistant
  5. Automations
  6. Development
  7. Conclusion
  8. Resources


After the first general post about home automation it’s time to kick things into higher gear. In this post we’ll go into detail about Home Assistant. Home Assistant is a fully open source home automation platform. It has a web interface as well as apps for Android and iOS. It features over 1.700 integrations at the time of writing and allows for full local control of your smart home without using any of the big cloud vendors. As with many things, Home Assistant is relatively easy to pick up but hard to master. Read on down below for more the details.


Before we get to installing Home Assistant it is handy to have some items at hand:

  • A machine/VM to run the assistant on, can be a Raspberry Pi (3b or 4b recommended)
    • If you are using a SBC, a decent micro SD card, or even better, an external ssd to install everything on at least 32 GiB in size
  • The correct image of the Home Assistant OS, download the file best suited for your device. The download page also features detailed information for each specific option
    • Raspberry Pi (and other board) images
    • Intel NUC image (or any other intel based board)
    • Virtual machine
      • Virtual Box => VDI disk image
      • Hyper-V => VHDX disk image
      • KVM => QCOW2 disk image
      • VMware Workstation => VMDK disk image
      • Proxmox => QCOW2 disk image
      • VMware ESXi => OVA disk image
  • An ethernet connection, WiFi can work too but ethernet might be more reliable depending on your personal WiFi setup
  • Patience, don’t be afraid to start over if things don’t work after the first try!


Once you have everything downloaded and prepared we can get to installing and doing the basic setup for Home Assistant. If you have downloaded the virtual machine hard disk image, load the downloaded image in the software by creating a new VM and assigning it the downloaded disk image. 2GiB of RAM and 1 or 2 cores are usually more than sufficient, these values can always be increased later on if needed. Follow the instructions on the download page for you specific VM technology.

If you have downloaded a device image, flash it onto the micro sd card, or even better an external SSD (Booting the Raspberry Pi from USB). An external SSD or decent USB 3.1 stick will last much longer than most SD cards, especially when writing a lot of log files. You can use a tool like Balena Etcher (multi OS) or Rufus (Windows) to flash the image. Once done, insert the SD card or USB device into your Raspberry Pi. Once you have set up your device or VM and powered it on, you should be able to visit it by entering http://homeassistant.local:8123 in the browser, this is where we will continue. Follow the setup guide, this will let you create an account (local, no cloud shenanigans) and set up the details about your home. You can set up integrations during this wizard but we will be doing this later. Click complete to exit the wizard. You will then be greeted with your home’s dashboard amd Home Assistant is ready to be used.

Setting up and using Home Assistant

Your home has some types of objects in it, these are:

  • Integrations: These are the building blocks that integrate with physical devices or services.
  • Devices: Any physical device that is added through an integration has a representation here.
  • Entities: A device can expose one or multiple entities.
  • Automations: An automation is an action that is activated by a trigger and when an optional condition is met.
  • Blueprints: An automation instance that is re-usable.
  • Scenes: A collection of predefined states for one or more devices/entities.
  • Scripts: Is what it says it is, a sequence of commands and/or actions to execute.
  • Areas: A home can have multiple areas, think rooms. Each area can have zero or more devices/automations/scenes and or scripts assigned to it.

One of the advantages of Home Assistant is that is has a vast library of available integrations. These integrations allow greater flexibility than most integrations that are made for Apple HomeKit, Amazon Alexa or Google Home. Most integrations are maintained by the open source community and development is quite active.

In the previous section we installed the Home Assistant, now we are going to add some stuff to it. Open the dashboard again and in the lower right side menu click on the Configuration link. This will open the configuration view where we can manage the home.

First select the Areas option. By default some rooms have been added, you can delete the existing ones if desired or add extra ones. It’s easiest to add all the rooms you want to have available in the Home Assistant web UI and app before we continue.

After we have set up the rooms, we want to pick the Integrations option. If you have your Home Assistant installation correctly configured, it probably will suggest some integrations based on the results of a network scan. Click on the Configure option to add the integration, a wizard will guide you through the process. For the devices in your home that have not been automatically detected, click the Add Integration button in the lower left corner and search for a device you have at home that might be supported. Some often used integrations are:

  • Sonos (speakers)
  • Tuya (lights, outlets, sensors)
  • Nest (thermostat, fire alarms)
  • Ikea Tradfri (lights)

Like with the auto detected integrations, a wizard will guide you through the setup process. The Home Assistant website has a collection of all published integrations, you can browse through and search the list. Each plugin on the site also has all the info to configure it correctly. During the setup process you should be able to assign each device to a specific area. You can skip this if wanted and assign a device to an area later (By opening the device and clicking the settings icon and picking the area there).

There are integrations which do not provide a setup wizard. To configure these integrations, a more hands on approach is required:

  • First click on the Supervisor link in the left bottom sidebar. This will open a section. In there select the Add-on Store in the top menu.
  • In the search field, type File editor, select the one add-on (it’s an official one) and click install. This will install a file editor so we can edit the configuration.yaml file without needing the login on the Home Assistant server itself via SSH. Once the add-on has been installed, you can find it in the supervisor UI under the Dashboard section.
  • Click on the add-on and click on start, then select open web ui. This will open the file editor.
  • In the top control bar of the editor, click on the folder icon and select configuration.yaml. Home Assistant uses the YAML format for its configuration. This is a well known format for most developers and has a very basic indentation based syntax. A plugin which does not provide a wizard-based setup will probably describe the configuration that needs to be added manually in the documentation. For more detailed information about editing files and changing the configuration.yaml, see the online documentation of Home Assistant

If you go back to the dashboard, you should see all available devices that have been assigned to a room. You can manage the dashboard manually too but this requires quite a bit of config. Experiment with this as you see fit. You can now control any device that is exposed and visible on the dashboard.

It might also be handy to create a number of scenes. A scene is a predefined set of states for one or multiple devices. For example a Good night and Good morning scene could be created to turn on/off lights, lower/raise any blinds or shutters and set any other device to a desired state. The scenes can then be used in automations to simplify the setup. To create a new scene:

  • Click the Configuration link in the left sidebar
  • Select the Scenes entry
  • Click on Add Scene
  • Give the scene a name and one or multiple devices with it You set the state of each device when adding it as you want it to be when the scene is activated

Home Assistant has a very extensive documentation. Consult it or the community if you get stuck!


While having all the devices visible is nice, a smart home wouldn’t be a smart home if it didn’t involve some automation. We want to make life easier and having to spend less time controlling our smart devices is one good way to do so. As with most things that involve automation, it will take some initial time investment to get things right. Don’t give up if it doesn’t work from the first time!

Home Assistant has an extensive automation framework that has multiple entities to its disposal for automating things.

To create a basic automation:

  • Click the Configuration link in the left sidebar
  • Select the Automations entry
  • Click Add Automation and select Start with an empty automation
  • Give the automation a name and description that tells you what it will do
  • Set the execution mode, single is a good default. This is mostly used for longer running automations
  • Select a trigger type, for example when another device is controlled, an event is sent
  • If desired add a condition This will be evaluated after the trigger is fired and before any actions are executed
  • Select one or multiple actions or scenes to control or activate
  • Click the Save button

It is also possible to edit the automation using the yaml format. In the top right click on the three dots and select Edit as YAML. This will give you an editor to edit the automation in its raw yaml formatting. You can always test the automation by clicking the execute button. This will ignore the trigger but test any of the given conditions and execute the specified actions.


Whilst there are plenty of integrations available for Home Assistant, some might be missing, or you have a very specific use case that is not available yet. By supporting web hooks, scripts, MQTT,… you can sometimes work around devices and platforms that have no ready to use integration, but sometimes you cannot.

It is possible by developing your own integrations for Home Assistant. A special website dedicated to developers is available to get started.

To start building a custom integration:

  • Have experience with Python, YAML and JSON
  • Set up the Home Assistant dev environment
  • Read through the documentation first, to prevent any RTFM situations later on. Everything you need is laid out in separate topics to read through.
  • From the dev environment, execute: python3 -m script.scaffold integration. This will create a new basic integration
  • Look at the example integrations
  • Test your integration locally by adding an entry to your integrations file to the configuration.yaml file: <config_dir>/custom_components/custom_integration/


Home Assistant is a very extensive home automation platform that is relatively easy to set up. Basic automations are fast to set up and use, while also providing very extensive options for advanced users. The extensive documentation and lively community make sure that most questions can be answered. If you are willing to get your hands dirty, creating your own integrations is also an option. A valid alternative to the home automation systems from Google and Amazon whilst not giving them access to all your home data!


Kevin is a senior consultant at Ordina, passionate about all modern web applications and smart tech. In his role as Competence Leader Smart Technologies he uses his knowledge of building custom software to build innovative solutions using new technologies. Loves to tinker with gadgets and electronics.