An open API service indexing awesome lists of open source software.

https://github.com/maxlyth/home-assistant-addons

Home Assistant add-on collection — household manifest pointing at per-addon source repos
https://github.com/maxlyth/home-assistant-addons

Last synced: 16 days ago
JSON representation

Home Assistant add-on collection — household manifest pointing at per-addon source repos

Awesome Lists containing this project

README

          

# maxlyth Home Assistant add-ons

A small household collection of [Home Assistant](https://www.home-assistant.io/)
add-ons. Each add-on's source lives in its own repository; this repo is the
single subscription URL the supervisor reads to discover and install them.

> **A note on the word "add-ons":** in the Home Assistant world, an "add-on" is
> a Docker container the supervisor manages on the host (panels, integrations,
> background services). It is **not** an Android app or a HACS pyscript /
> custom integration. If you arrived here looking for either of those, see the
> "Not in this repo" section below.

## Installing

In Home Assistant, go to **Settings → Add-ons → Add-on Store**, click the **⋮**
menu in the top-right, choose **Repositories**, and paste:

```
https://github.com/maxlyth/home-assistant-addons
```

The add-ons listed below will appear in the store. Click into one to read its
description and install. The first install of each add-on pulls a multi-arch
pre-built image from GHCR — no per-host Dockerfile rebuild.

## Add-ons in this repo

| Add-on | Source repo | Description |
|---|---|---|
| **Bayesian Studio** | [`maxlyth/ha-addon-bayesian-studio`](https://github.com/maxlyth/ha-addon-bayesian-studio) | Visual interactive tuning UI for Home Assistant Bayesian binary sensors. |
| **MkDocs** | [`maxlyth/ha-addon-mkdocs`](https://github.com/maxlyth/ha-addon-mkdocs) (friendly fork of [`XavierBerger/home-assistant-addons`](https://github.com/XavierBerger/home-assistant-addons)) | Project documentation with Markdown — read-only Material-styled vault rendered in an HA ingress panel. |

## How this repo is structured

This repo is a thin **manifest** — each `/` directory contains
only the supervisor-facing metadata (`config.yaml`, `README.md`, icons). The
actual source — Dockerfile, application code, tests, CHANGELOG — lives in
each add-on's own source repository.

```
home-assistant-addons/
├── repository.yaml # this repo's identity
├── bayesian-studio/
│ ├── config.yaml # name, slug, version, image: ghcr.io/maxlyth/...
│ └── README.md # pointer to source repo
├── mkdocs/
│ ├── config.yaml
│ ├── README.md
│ ├── icon.png
│ └── logo.png
└── README.md # this file
```

Each `config.yaml` declares an `image:` field pointing at the corresponding
multi-arch image on GHCR. The supervisor pulls the image instead of building
locally. To bump an add-on's version: bump the source repo, let its CI publish
the new tag to GHCR, then bump `version:` in this repo's matching
`config.yaml`. Two-step release flow; one canonical install URL.

## Not in this repo

- **Custom HACS integrations / pyscripts** — those live elsewhere
(e.g. [`maxlyth/homeassistant-bayesian-backfill`](https://github.com/maxlyth/homeassistant-bayesian-backfill),
[`maxlyth/homeassistant-lovelace-to-yaml`](https://github.com/maxlyth/homeassistant-lovelace-to-yaml)).
HACS, not the add-on store.
- **Android apps** — the title clash is unfortunate; nothing here is an
Android app.