A sample Docker Compose configuration for the smart home services I use: Home Assistant, Mosquitto MQTT, Frigate NVR, Music Assistant, and RouterRebooter.
-
Clone the repository:
git clone https://github.com/mwdle/HomeAssistantConfig.git
-
Create a folder on your system for Docker bind mounts / storing container files. The folder should have the following structure:
docker_volumes/ ├── Frigate/ │ ├── config/ │ └── storage/ ├── HomeAssistant/ │ ├── config/ │ └── .ssh/ ├── MQTT/ │ ├── config/ │ ├── data/ │ └── log/ ├── MusicAssistant/ │ └── data/ ├── RouterRebooter/ │ ├── data/ │ └── secrets/
-
Create a file called
.env
in the same directory asdocker-compose.yml
containing the following properties:DOCKER_VOLUMES=<PATH_TO_DOCKER_VOLUMES_FOLDER> # The folder created in the previous step. RTSP_USER=<YOUR_RTSP_USER> # For Frigate RTSP_PASSWORD=<YOUR_RTSP_PASSWORD> # For Frigate MQTT_USER=<YOUR_MQTT_USER> # For Frigate MQTT_PASSWORD=<YOUR_MQTT_PASSWORD> # For Frigate MUSIC_VOLUME=<YOUR_MUSIC_LIBRARY_FOLDER> # A folder containing your local music library for Music Assistant.
-
Open a terminal in the directory containing the docker-compose file.
-
Create docker networks for the containers
docker network create -d macvlan --subnet=192.168.0.0/24 --gateway=192.168.0.1 -o parent=eno1 AAA_LAN # Ensure the gateway and subnet match your LAN network. YOUR LAN SHOULD BE TRUSTED. AAA in the name ensures Docker uses this network as the primary interface for all connected containers. docker network create Frigate docker network create HomeAssistant docker network create MusicAssistant docker network create RouterRebooter
The networks are configured in docker-compose.yml such that:
- Containers in the same network are accessible from each other by their container names.
- Music Assistant is in a macvlan, making it appear to be a physical interface on the host LAN (for mDNS / device discovery). Make sure to reserve the IP address listed in docker-compose.yml for Music Assistant on your router's web interface.
- Home Assistant is in a macvlan, making it appear to be a physical interface on the host LAN (for mDNS / device discovery). Make sure to reserve the IP address listed in docker-compose.yml for Home Assistant on your router's web interface.
- Frigate's Port 8555 (for WebRTC) is bound to port 8555 on the host.
- Frigate and MQTT can directly communicate.
- Home Assistant and MQTT can directly communicate.
- Home Assistant and RouterRebooter can directly communicate.
- Home Assistant and Music Assistant can communicate so long as you add your Reverse Proxy for MA to the Home Assistant Docker network using a Docker Network Alias to connect with.
- Home Assistant and Frigate can communicate so long as you add your Reverse Proxy for Frigate to the Home Assistant Docker network using a Docker Network Alias to connect with.
-
Start the containers:
docker compose up -d
-
To update images and containers (RouterRebooter must be built using the RouterRebooter repository):
docker compose pull --ignore-pull-failures # RouterRebooter must be built using Dockerfile from the RouterRebooter repository, so trying to pull it will fail. docker compose up -d
Your containers should now be up and running! Attach your reverse proxy container to the previously created Docker Networks and configure it accordingly.
This project is licensed under the GNU General Public License v3.0 (GPL-3.0). See the LICENSE file for details.
This repository is provided as-is and is intended for informational and reference purposes only. The author assumes no responsibility for any errors or omissions in the content or for any consequences that may arise from the use of the information provided. Always exercise caution and seek professional advice if necessary.