Add some entity categories to Reolink

[balloob]

Breaking change

Proposed change

Recently got a Reolink PoE camera. Noticed a couple of entities missing the entity category.

Maybe person/motion could be considered diagnostic too but that can be for a future discussion.

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 Black (black --fast 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 @starkillerOG, mind taking a look at this pull request as it has been labeled with an integration (reolink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of reolink 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 reolink Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[starkillerOG]

Thank you for the PR!

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

[balloob]

Comments addressed.

Both commented places removed

[starkillerOG]

Thanks, LGTM

[starkillerOG]

A bit off topic, but would like some input:
What would still be needed to get the Reolink integration to platinum level?

[balloob]

I don't know. I haven't checked the code very thorough. Generally it's the code owner opening a PR and marking things as checked. And they will be verifiedi n the PR.

[bdraco]

@starkillerOG Example: #102069

[balloob]

Should is_recording switch have a config entity category?

[starkillerOG]

Thanks for the info, will look into the quality scaled.

@balloob yes I think is_recording can be considered config. I did not add it yet since I think it is one of the main features of the camera (to record), and I did not want to push it to the bottom of the device page together with other less relevant settings. But indeed it is a setting not a pysicall control. So we can add the category

[balloob]

PR for record category #102439