Skip to content

Adds new integration [Shaffer-Softworks/Tripp-light]#7959

Open
sickkick wants to merge 3 commits into
hacs:masterfrom
sickkick:add-tripp-lite-srcool
Open

Adds new integration [Shaffer-Softworks/Tripp-light]#7959
sickkick wants to merge 3 commits into
hacs:masterfrom
sickkick:add-tripp-lite-srcool

Conversation

@sickkick
Copy link
Copy Markdown
Contributor

@sickkick sickkick commented May 24, 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.

Note for reviewers: Brand images (Home Assistant 2026.3+)

Home Assistant no longer accepts PRs for new custom integrations in home-assistant/brands. As of Home Assistant 2026.3, custom integrations are expected to ship their own brand assets in-repo.

This integration does that: custom_components/tripp_lite_srcool/brand/ contains icon.png, icon@2x.png, logo.png, and logo@2x.png. HA 2026.3+ uses these at runtime (Settings → Integrations, device UI, etc.). The integration is not listed in home-assistant/brands; brand assets are local to the repo per current HA guidance.

Integration summary

Home Assistant custom integration for the Tripp Lite SRCOOLNET SNMP Webcard Interface Module (Remote Cooling Management for SRCOOL12K / SRXCOOL12K) over Telnet. Provides climate control (setpoint, fan, power) and status sensors.

Links


Repository: Shaffer-Softworks/Tripp-light

Co-authored-by: Cursor <cursoragent@cursor.com>
@hacs-bot hacs-bot Bot marked this pull request as draft May 24, 2026 16:46
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.

Repository name case mismatch. The submitted name sickkick/Tripp-light does not match GitHub's actual repository name Shaffer-Softworks/Tripp-light. Please update your submission to use the exact case-sensitive repository name.

@sickkick sickkick marked this pull request as ready for review May 24, 2026 16:46
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.

Repository name case mismatch. The submitted name sickkick/Tripp-light does not match GitHub's actual repository name Shaffer-Softworks/Tripp-light. Please update your submission to use the exact case-sensitive repository name.

@hacs-bot hacs-bot Bot marked this pull request as draft May 24, 2026 16:46
Co-authored-by: Cursor <cursoragent@cursor.com>
@sickkick sickkick changed the title Adds new integration [sickkick/Tripp-light] Adds new integration [Shaffer-Softworks/Tripp-light] May 24, 2026
@sickkick sickkick marked this pull request as ready for review May 24, 2026 16:48
@hacs-bot
Copy link
Copy Markdown

hacs-bot Bot commented May 24, 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

Co-authored-by: Cursor <cursoragent@cursor.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.

1 participant