mirrors
/
rtl_433-hass-addons
mirror of https://github.com/pbkhrv/rtl_433-hass-addons.git
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Collection of Home Assistant add-ons that use rtl_433
299 Commits 14 Branches 17 Tags 537 KiB
Shell 82.8%
Dockerfile 17.2%
Go to file
Andrew Berry 20ca8f21d7
Downgrade paho-mqtt to 1.x #180 #178 #179 		2024-02-17 14:20:00 -05:00
.github Fix line endings on pull request template 2023-10-28 09:02:11 -04:00
rtl_433 Update CHANGELOG and versions 2024-02-17 14:11:23 -05:00
rtl_433-next Document how to read the version #161 2023-10-28 15:15:37 -04:00
rtl_433_mqtt_autodiscovery Update CHANGELOG and versions 2024-02-17 14:11:23 -05:00
rtl_433_mqtt_autodiscovery-next Default mqtt_retain to true #88 2024-02-16 19:46:19 -05:00
README.md Document what URL to use when adding #127 2023-08-26 21:16:53 -04:00
repository.json Changed URL, tweaks 2020-12-26 18:21:56 -05:00

README.md

rtl_433 Home Assistant add-ons

This is a collection of Home Assistant add-ons that work with rtl_433.

Running the Development Version

  • First, follow the tutorial at Tutorial: Making your first add-on 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 and reinstall the addon to rebuild the Docker containers to see any changes.

Release Process

  • The next branch represents the upcoming version of these addons.
  • rtl_433/config.json and 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.
    1. 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.