Adds new integration [pjordanandrsn/ha-generac]

[pjordanandrsn]

Repository

https://github.com/pjordanandrsn/ha-generac

Latest release

https://github.com/pjordanandrsn/ha-generac/releases/tag/v0.5.3

CI runs

https://github.com/pjordanandrsn/ha-generac/actions/workflows/validate.yaml

Category

Integration

Description

Auth0 universal-login fork of binarydev/ha-generac that handles MobileLink's post-2024 auth migration.

Generac switched MobileLink from cookie-scrape login to Auth0 universal-login + DPoP-bound refresh tokens on 2026-04-21 (support article). The original integration broke; this fork ports @sslivins's in-flight rewrite (PR #267) and adds a _handle_custom_prompt handler for Auth0 Forms consent / T&C prompts that some accounts get on first OAuth login.

Why a fork instead of upstream PR

PR #267 has been open since 2026-04 without a merge. This fork lets users with broken MobileLink integrations install a working version through HACS today; the prompt-handler patch is a candidate to push back to PR #267 once that's accepted.

Checklist

• Latest release tagged on default branch (v0.5.3)
• hacs.json present
• manifest.json complete
• HACS validate + hassfest CI green on main (latest run)
• License preserved from upstream (MIT)
• README documents install + reauth flow

[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

[frenck]

Hi @pjordanandrsn, thanks for the submission! 👋

Approving and merging now.

../Frenck

                       

Blogging my personal ramblings at frenck.dev

[hacs-bot]

Congratulations! Your repository has been added to HACS 🎉

Your repository has been approved:
Your repository has been successfully merged into the HACS default repository list.
It might take up to 8 hours before your repository appears in HACS for users.

Resources:

• HACS Discord
• Home Assistant Developer Blog

Thank you for contributing to the Home Assistant community! 🎉