Adding new on values for Tuya Presence Detection Sensor

[KunalAggarwal]

Breaking change

Proposed change

The new presence sensors by Tuya, have multiple values to indicate presence, including large_move, small_move and presence. So, updating the on value for the "hps" human presence sensor. See attached module API response with valid values.

See this sensor: https://solution.tuya.com/projects/CMavulo8wvpzqz

Documentation on the Chinese version shows these values in the API: https://developer.tuya.com/cn/docs/iot/s?id=K9j2w4p710ge9

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.

To help with the load of incoming pull requests:

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

[home-assistant]

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

Code owner commands

Code owners of tuya 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 tuya 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.

[frenck]

Thanks, @KunalAggarwal 👍

../Frenck

[frenck]

@KunalAggarwal I'm confused why you create an merge commit there? Was there an issue? What has changed?

[KunalAggarwal]

I happened to tap the Update Branch button on the action tab. Nothing has changed. Sorry about that.

[pabloromeo]

I believe "peaceful" should also be considered an "on" value shouldn't it?

If I understood the values correctly it appears that peaceful is for when you are present but standing still and that sort of thing.