add redgtech integration

[Jonhsady]

Breaking change

Proposed change

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request: add documentation redgtech home-assistant.io#37217

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

When adding new integrations, limit included platforms to a single platform. Please reduce this PR to a single platform

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

Stale

[zweckj]

Hi, thanks for contributing. However, there's a couple of things wrong with this PR

• it's missing a meaningful description
• it's adding more than one platform, which the bot already told you
• it doesn't use a library on PyPi for abstracting the actual API communication

please check the Development Checklist

Thanks 👍

[zweckj]

I don't want to be rude, but please, read the development guidelines.

• you still have more than one platform (light & switch)
• your library code is not publicly avaiable on a repository (not PyPi), OSI license, automated & tagged releases
• you're quality scale is way off (e.g. you DO have stateful entities)
• only by glancing at your code I can tell you didn't really read the quality scale criteria (e.g. runtime-data)