Skip to content

Adds new integration [cm-makes/aurum-ha]#6653

Open
cm-makes wants to merge 6 commits into
hacs:masterfrom
cm-makes:add-aurum
Open

Adds new integration [cm-makes/aurum-ha]#6653
cm-makes wants to merge 6 commits into
hacs:masterfrom
cm-makes:add-aurum

Conversation

@cm-makes
Copy link
Copy Markdown

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/cm-makes/aurum-ha/releases/tag/v1.0.0
Link to successful HACS action (without the ignore key): https://github.com/cm-makes/aurum-ha/actions/runs/23783703214
Link to successful hassfest action (if integration): https://github.com/cm-makes/aurum-ha/actions/runs/23783703239

@hacs-bot hacs-bot Bot changed the title Add cm-makes/aurum-ha Adds new integration [cm-makes/aurum-ha] Mar 31, 2026
@hacs-bot
Copy link
Copy Markdown

hacs-bot Bot commented Mar 31, 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

@cm-makes cm-makes marked this pull request as draft March 31, 2026 10:29
@cm-makes cm-makes marked this pull request as ready for review March 31, 2026 12:13
@hacs-bot hacs-bot Bot marked this pull request as draft May 19, 2026 04:05
Copy link
Copy Markdown

@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.

@cm-makes cm-makes marked this pull request as ready for review May 19, 2026 04:35
cm-makes added a commit to cm-makes/aurum-ha that referenced this pull request May 19, 2026
- Validate energy-source selections in setup and options flow: power
  sensors must report W/kW, energy sensors Wh/kWh, battery SOC a percent.
  Catches the silent-misbehavior cases (kWh sensor picked as grid, SOC
  reported as 0-1 fraction) with clear, actionable error messages in
  English and German.
- Replace manual version fields in bug-report template with required
  diagnostics-file attachment; the diagnostics JSON already carries
  versions, sensor states and device config.
- Add a Troubleshooting section to the README covering the runtime
  patterns validation can't catch: grid sign convention, battery mode
  stuck on charging, missing battery charge/discharge sensors, devices
  waiting despite surplus, flapping.
- Lead README install with HACS default flow (with custom-repo fallback
  noted until hacs/default#6653 merges); swap badge to HACS-Compatible.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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