New core integration for VegeHub

[GhoweVege]

Proposed change

I work for a company called Vegetronix. We would like to officially add support for connecting our VegeHub product to Home Assistant. I have attempted to do everything as instructed, but I am brand new to contributing to open source projects, so if I need to change the way I did anything, please let me know. Thank you.

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: VegeHub Integration Documentation home-assistant.io#35639

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]

Hi @GhoweVege

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[home-assistant]

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

[joostlek]

Integrations should have their logic to connect with the device or service in a library published on PyPi

[GhoweVege]

Sorry, this is my first time doing this. I usually write code for embedded platforms, so I'm trying to learn.

When you say that I should put the "logic to connect with the device" into its own library, what does that mean exactly? The integration only uses API calls to send and receive data from the device. Should I write a library with those specific API calls in it?

[joostlek]

Yep!

[GhoweVege]

OK, thank you. I will get to work on it.

[GhoweVege]

Ok, it took a few days of learning, but I think it's fixed. I have a library on PyPI now, and the integration uses that to connect with the device.