Skip to content

Adds new integration [Big-Xan/adaptive_plant]#6520

Draft
Big-Xan wants to merge 3 commits into
hacs:masterfrom
Big-Xan:add-adaptive-plant
Draft

Adds new integration [Big-Xan/adaptive_plant]#6520
Big-Xan wants to merge 3 commits into
hacs:masterfrom
Big-Xan:add-adaptive-plant

Conversation

@Big-Xan
Copy link
Copy Markdown

@Big-Xan Big-Xan commented Mar 25, 2026

Checklist

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

Links

Link to current release: https://github.com/Big-Xan/adaptive_plant/releases/tag/v1.0.7
Link to successful HACS action (without the ignore key): https://github.com/Big-Xan/adaptive_plant/actions/runs/23520327795
Link to successful hassfest action (if integration): https://github.com/Big-Xan/adaptive_plant/actions/runs/23520256820

@hacs-bot hacs-bot Bot changed the title Add Big-Xan/adaptive_plant Adds new integration [Big-Xan/adaptive_plant] Mar 25, 2026
@hacs-bot
Copy link
Copy Markdown

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

Copy link
Copy Markdown
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Hi @Big-Xan, thanks for the submission! 👋

One blocker before merge:

Sort position. The line "Big-Xan/adaptive_plant" is placed between "BigPiloto/ha-drugstore-stock" and "binarydev/ha-generac", but in the case-insensitive ASCII sort that HACS uses, the hyphen in big-xan (codepoint 0x2D) sorts before letters like n (0x6E) and p (0x70). After the big prefix matches, your repo's next character is -, which makes it sort before both bignocciolino and bigpiloto. Please move the line so it sits between "bieniu/ha-perplexity" and "BigNocciolino/CryptoTracker".

Push the fix to the existing branch and CI will re-run automatically.

A couple of non-blocking notes for a future release:

  • www/adaptive-plant-card.js at the repo root is not shipped via HACS for an integration submission (HACS only copies custom_components/<domain>/). If you want users to receive the card automatically, move it inside custom_components/adaptive_plant/frontend/ and serve it via hass.http.async_register_static_paths, registering the Lovelace resource in async_setup_entry. There's a clean reference for this pattern in #6517 (eladnahum5/ha-vouchervault).
  • Same for blueprints/automation/ at the repo root. If you want HACS users to get the example blueprints, embed them under custom_components/adaptive_plant/blueprints/ and copy them into hass.config.path("blueprints") on setup via the executor with an mtime guard. Reference: #6514 (dn5qMDW3/tzevaadom).

../Frenck

                       

Blogging my personal ramblings at frenck.dev

@hacs-bot hacs-bot Bot marked this pull request as draft May 17, 2026 16:48
Fix sort position for Big-Xan/adaptive_plant
@Big-Xan
Copy link
Copy Markdown
Author

Big-Xan commented May 17, 2026

Hi Frenck, thanks for the detailed review and all that you do for HA and HACS!

I've fixed the sort position — Big-Xan/adaptive_plant is now placed between bieniu/ha-perplexity and BigNocciolino/CryptoTracker. CI is passing.

I've noted the two non-blocking points about the frontend card and blueprints — I'll tackle both in a follow-up release once the integration is listed. Thank you so much for the tips :)

Marking as ready for review. Thanks again!

@Big-Xan Big-Xan marked this pull request as ready for review May 17, 2026 22:43
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.

@hacs-bot hacs-bot Bot marked this pull request as draft May 17, 2026 22:43
@Big-Xan Big-Xan requested a review from frenck May 18, 2026 22:22
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