KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#dsh #dsh-plugin #ai-agent #developer-tools #codex #typescript #cli #deepseek-harness #claude-code #ai-agents #mcp #rust

rtl_433-hass-addons

★ 348 Open GitHub ↗

Collection of Home Assistant add-ons that use rtl_433

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# rtl_433 Home Assistant add-ons

This is a collection of Home Assistant add-ons that work with [rtl_433](https://github.com/merbanan/rtl_433).

[![Open your Home Assistant instance and show the add app repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgithub.com%2Fpbkhrv%2Frtl_433-hass-addons)

* [How to add this add-on repository to your Home Assistant install](https://www.home-assistant.io/common-tasks/os#installing-a-third-party-app-repository)
* Use `https://github.com/pbkhrv/rtl_433-hass-addons` as the URL for the repository.

## Running the Development Version

- First, follow the tutorial at [Tutorial: Making your first add-on](https://developers.home-assistant.io/docs/add-ons/tutorial/) to learn how to build a basic addon.
- Use `git` to clone this repository same `addons` folder used in the tutorial.
- Make changes to the code, or use `git` to checkout branches to test.
- Remember to to [reload](https://developers.home-assistant.io/docs/add-ons/tutorial/#i-dont-see-my-add-on) and reinstall the addon to rebuild the Docker containers to see any changes.

## Release Process

* The [next](https://github.com/pbkhrv/rtl_433-hass-addons/tree/next) branch represents the upcoming version of these addons.
* [rtl_433/config.json](rtl_433/config.json) and [rtl_433_mqtt_autodiscovery/config.json](rtl_433_mqtt_autodiscovery/config.json) will contain the version numbers of the previously set addon versions, but will have different code.
* When `next` is ready to be tagged for a release:
  1. Create a pull request against `main`, bumping the versions of each `config.json` file if the individual addon has been changed. As well, update the `CHANGELOG.md` in the same pull request.
  2. When the pull request has been approved, create a date-based tag such as `2022.12.01.0` on the last commit of the pull request. This will build docker containers with the version numbers in `config.json`.
  3. Merge the PR into `main` to actually promote the release to end users. Note the new version(s) in the commit message.
    - Note we do not tag `main` in git, since each addon has it's own version number.
  4. Create a new branch off of `main` setting the addon versions back to `next`. Create a PR to merge `main` into `next` to reconcile the branches.

rtl_433-hass-addons

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README