Skip to content

chore: mention Home Assistant in Setup instructions#1125

Open
Blaimi wants to merge 1 commit intoqdm12:masterfrom
ha-ddns-updater:chore/ha-in-readme
Open

chore: mention Home Assistant in Setup instructions#1125
Blaimi wants to merge 1 commit intoqdm12:masterfrom
ha-ddns-updater:chore/ha-in-readme

Conversation

@Blaimi
Copy link
Copy Markdown

@Blaimi Blaimi commented Apr 19, 2026

Hi guys,

I created a Home Assistant addon for ddns-updater. Would be nice if it could be mentioned in the setup-instructions.

Copy link
Copy Markdown
Owner

@qdm12 qdm12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Just add a newline between the text and heading 😉

Comment thread README.md
@Blaimi Blaimi force-pushed the chore/ha-in-readme branch from 74f5060 to 4fbaf37 Compare April 21, 2026 18:35
@Blaimi
Copy link
Copy Markdown
Author

Blaimi commented Apr 22, 2026

May I ask you about your current release workflow? Currently the addon is based on your latest tagged version and has pipelines to check for new versions to poke me via an MR. Relying on latest would likely break the addon very often or give me headache with updates. This is because the addon needs a settings schema and translation file which needs to match the settings of this project.

If you want, I can help you integrating https://github.com/semantic-release/semantic-release to this project. It would be the same workflow as at the moment (push to master, build from master, use from latest), but with version numbers (push to master, create tag/release, build from tag, use from tag—or latest) so the users can decide whether they want to pin to a major, minor, or specific version—or always follow the latest ;-) .

To be honest, I only created the addon because of #1046. I couldn't find any active and trustworthy HA addon which provides the new hetzner DNS API so I had to create my own. Instead of building it from scratch I thought it is more useful to build it around an existing and even more useful project which lead me here. And I love it! Not only because it has a webinterface, but especially because of its ability to update even offline devices via IPv6-suffixes (privacy disabled with eui64 of course).

@WolfRevo
Copy link
Copy Markdown

May I ask you about your current release workflow? Currently the addon is based on your latest tagged version and has pipelines to check for new versions to poke me via an MR. Relying on latest would likely break the addon very often or give me headache with updates. This is because the addon needs a settings schema and translation file which needs to match the settings of this project.

If you want, I can help you integrating https://github.com/semantic-release/semantic-release to this project. It would be the same workflow as at the moment (push to master, build from master, use from latest), but with version numbers (push to master, create tag/release, build from tag, use from tag—or latest) so the users can decide whether they want to pin to a major, minor, or specific version—or always follow the latest ;-) .

To be honest, I only created the addon because of #1046. I couldn't find any active and trustworthy HA addon which provides the new hetzner DNS API so I had to create my own. Instead of building it from scratch I thought it is more useful to build it around an existing and even more useful project which lead me here. And I love it! Not only because it has a webinterface, but especially because of its ability to update even offline devices via IPv6-suffixes (privacy disabled with eui64 of course).

@qdm12 @Blaimi I would love to see ddns-updater being released with semver releases on hub.docker.com instead of latest. That would much better fit into todays patch management requirements we have. So I like the idea of Blaimi supporting you here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants