Adds new integration [magicbear/huawei_ups]

[magicbear]

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/magicbear/huawei_ups/releases/tag/v1.1.1
• Link to successful HACS action (without the ignore key): https://github.com/magicbear/huawei_ups/actions/runs/28178318171
• Link to successful hassfest action: https://github.com/magicbear/huawei_ups/actions/runs/28178317874

Integration summary

Repository: magicbear/huawei_ups
Domain: huawei_ups
Category: Integration

Home Assistant custom integration for Huawei UPS5000 devices via Modbus/TCP.

Note: Repository was renamed from huawei_ups_hacs to huawei_ups per HACS naming policy (repository names must not contain "HACS").

Features

• Config flow with connection validation and reconfigure support
• 85 optional sensors with register-block optimized polling
• Input/output/bypass/battery electrical metrics
• Power/UPS/battery state sensors with EN/ZH translations
• Auto-disable sensors on invalid register values (0x7FFF / 0xFFFF)
• Device info from UPS status registers

Requirements

• Home Assistant 2023.9.0+
• pymodbus >= 3.10.0

Maintainer

I am the repository owner and primary maintainer (@magicbear).

[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