Sam Welek

hassio-config

My Home Assistant configuration running on a RPi4

Cover Photo
Photo by Home Assistant on GitHub

Background

This project covers my own configuration used by the Home Assistant instance running (currently) on my Raspberry Pi 4.

The below is taken from the README.md from the repository itself, view this file and rest of the repository on GitHub here

TiberiusHunter’s Hassio Configuration

Build Status Build Status MIT License

Contributors Forks Stargazers Issues

About

A repository storing and backing up my Home Assistant configuration

File Structure

The entry point for Hassio is the configuration.yaml file. From there I’ve split up the configuration into various folders and files found under the /configuration/ directory.

This has simply been to reduce the size of the configuration.yaml especially as my previous installation of Hassio ended up being a nightmare to maintain.. :roll_eyes:

From the configuration.yaml file, all the files under the configuration/integrations/ directory get imported - this lists what you’d likely see in a regular configuration file.

Once an integration contains any entities, sensors, scenes, scripts, etc. I then break that down into it’s own file under whichever type of integration it is - For example, for the camera: integration I’ve created a separate file under configuration/entities/camera/ directory for each camera.

Usage

This repository has been designed to be used with the default git pull addon once the build passes on the main branch.

When there are changes to any of the configuration files Hassio will pull the latest changes and automatically restart :tada:

Contributing

You’ve found a bug in my config, a mistake in the docs or maybe you want to add a new feature? :thinking:

I’m very open to any and all contributions to my config, please let me know by creating an issue on the repository and feel free to create a pull request with your changes :heart:

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Acknowledgements

Project Link: GitHub

Share on: