Skip to content

Adds new integration [qlerup/budget-manager-sync]#5041

Draft
qlerup wants to merge 11 commits intohacs:masterfrom
qlerup:budget-manager-sync
Draft

Adds new integration [qlerup/budget-manager-sync]#5041
qlerup wants to merge 11 commits intohacs:masterfrom
qlerup:budget-manager-sync

Conversation

@qlerup
Copy link
Contributor

@qlerup qlerup commented Jan 7, 2026

Checklist

  • I've read the publishing documentation.
  • I've added the HACS action to my repository.
  • (For integrations only) I've added the hassfest action to my repository.
  • The actions are passing without any disabled checks in my repository.
  • I've added a link to the action run on my repository below in the links section.
  • I've created a new release of the repository after the validation actions were run successfully.

Links

Link to current release: https://github.com/qlerup/budget-manager-sync/releases/tag/v1.0.1
Link to successful HACS action (without the ignore key): https://github.com/qlerup/budget-manager-sync/actions/runs/20797256719
Link to successful hassfest action (if integration): https://github.com/qlerup/budget-manager-sync/actions/runs/20797256715

@hacs-bot
Copy link

hacs-bot bot commented Jan 7, 2026

Thank you for submitting your repository to HACS (Home Assistant Community Store).

Your submission is in the review queue:
Your repository is waiting to be reviewed and included in HACS.

You can view the current queue here. Pull requests are processed in the order they were created, oldest first.

What to avoid during review:
To help reviewers work efficiently, don't do the following:

  • Comment on the pull request - The reviewer will contact you when they have feedback or questions.
  • Open a new pull request - This won't speed up the process and creates duplicate work.
  • Ask followers to comment on the pull request - This won't speed up the process and may delay your review.
  • Merge in the default branch - Only do this if a maintainer asks you to resolve a merge conflict.

If you need to make changes:
You can continue updating your repository while waiting for review. Changes to your repository will be reflected when the reviewer examines it. Only comment on the pull request if you need to withdraw your submission or have critical information for reviewers.

About draft pull requests:
Draft pull requests aren't included in the review queue. Your pull request may be marked as draft by a reviewer if issues need to be addressed. Once you've resolved all issues, mark it as ready for review to re-enter the queue.

What happens next:
Once a reviewer examines your submission, they'll either:

  • Approve and merge your pull request if everything meets the requirements
  • Request changes or ask questions if adjustments are needed

@hacs-bot hacs-bot bot marked this pull request as draft January 12, 2026 09:34
@qlerup qlerup marked this pull request as ready for review January 12, 2026 16:28
Copy link

@hacs-bot hacs-bot bot left a comment

Choose a reason for hiding this comment

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

Your branch seems out of date. Please update your branch with the latest changes from the base branch.

@hacs-bot hacs-bot bot marked this pull request as draft January 12, 2026 16:28
@qlerup qlerup marked this pull request as ready for review January 12, 2026 16:29
"Pyhass/Hive-Custom-Component",
"pypolestar/polestar_api",
"pytoyoda/ha_toyota",
"qlerup/budget-manager-sync",
Copy link
Member

Choose a reason for hiding this comment

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

As this is not yet bundled with the card, ill draft this.
Mark it as ready once you want to proceed here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi again,

Does it have to be a bundle? The downside of running it through an integration is, as I understand it, that:

  1. The Resources has to be added manually.

  2. You have to restart Home Assistant for every update, regardless of whether it’s the card or the integration that has been updated.

Isn’t it possible to do them separately? Since the updates will mainly be to the card itself.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Can you please point me to some docs where i can read how to bundle a card and integration together?

Copy link
Member

Choose a reason for hiding this comment

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

AFAIK, there are not much docs for custom integrations.
Just look at other integrations that do the same (HACS itself is one of those that register custom frontend resources).

@ludeeus ludeeus marked this pull request as draft January 13, 2026 07:26
@qlerup qlerup marked this pull request as ready for review January 18, 2026 19:48
@ludeeus ludeeus marked this pull request as draft January 19, 2026 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants