Add BaseEntity for apsystems integration

[mawoka-myblock]

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:

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.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

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

[home-assistant]

Hey there @SonnenladenGmbH, mind taking a look at this pull request as it has been labeled with an integration (apsystems) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of apsystems can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign apsystems Removes the current integration label and assignees on the pull request, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

[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.

[joostlek]

I think epenet makes some valid comments, I personally don't like to just throw big data objects (like the config entry) in these tiny entities

[mawoka-myblock]

I think epenet makes some valid comments, I personally don't like to just throw big data objects (like the config entry) in these tiny entities

Oh, completely missed the comments from epenet 🤦🏼. Regarding those big objects, if you say so, I'll address it, but I thought I'd do it as the Adguard integration did it.

[joostlek]

Right, I only said Adguard because they were one of the first to have the ConfigEntry data implemented, but now I am looking at the rest and meh, I don't like it 😂

[mawoka-myblock]

Right, I only said Adguard because they were one of the first to have the ConfigEntry data implemented, but now I am looking at the rest and meh, I don't like it 😂

No, I haven't chosen Adguard because of you, only because it's at the top in the folder and is pretty full-featured and pretty high quality.

[mawoka-myblock]

I would love to get this merged before the release so that users don't open issues because of an incomplete featureset.

[epenet]

LGTM 👍

[mawoka-myblock]

Thanks for the review!