Adds new integration [Nosdave/ha-lg-ac-infrared]

[Nosdave]

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

• Repository: https://github.com/Nosdave/ha-lg-ac-infrared
• Current release: https://github.com/Nosdave/ha-lg-ac-infrared/releases/tag/v0.2.4
• Successful HACS action: https://github.com/Nosdave/ha-lg-ac-infrared/actions/runs/26417052779
• Successful hassfest action: https://github.com/Nosdave/ha-lg-ac-infrared/actions/runs/26417052798

About

A HACS custom integration that exposes an LG split-AC as a native climate
entity (plus switches, buttons and service actions), driven through the
Home Assistant native infrared platform (HA 2026.4+) and any ESPHome
ir_rf_proxy device. Verified end-to-end on LG A12AHD (AS-H126PDL1,
remote 6711A20073Z) with a Seeed Studio XIAO Smart IR Mate.

The IR proxy stays generic; all LG protocol logic lives in this
integration. Brand assets ship in-repo under custom_components/lg_ac_infrared/brand/
per the HA 2026.3+ convention.

[hacs-bot]

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