Add additional sensors for Tuya DIN

[cronjefourie]

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

[cronjefourie]

Trying to add the fix a 2nd time. The 1st time I mucked up with the re-base :D

[cronjefourie]

tried the "update branch" button

[jbouwh]

Can you add tests as well

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

[cronjefourie]

Oh yea I added that so that it ignores my VSCode workspace file

…

On Tue, 29 Aug 2023 at 13:19, Jan Bouwhuis ***@***.***> wrote: ***@***.**** requested changes on this pull request. Can you add tests as well ------------------------------ In .gitignore <#98752 (comment)> : > @@ -135,3 +135,4 @@ tmp_cache # python-language-server / Rope .ropeproject +*.code-workspace Seems this line is unrelated to the PR. Please remove it. ⬇️ Suggested change -*.code-workspace ------------------------------ In homeassistant/components/tuya/sensor.py <#98752 (comment)> : > @@ -818,6 +818,27 @@ class TuyaSensorEntityDescription(SensorEntityDescription): native_unit_of_measurement=UnitOfElectricPotential.VOLT, subkey="voltage", ), + TuyaSensorEntityDescription( + key=DPCode.CUR_CURRENT, + translation_key="current", I do not see the strings file updated. — Reply to this email directly, view it on GitHub <#98752 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADEWPUOJKLEGBDADUR4QXADXXXF4RANCNFSM6AAAAAA3YMPI3Q> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[frenck]

Removed a small unrelated change, rebased the whole PR onto the latest dev branch (which also cleaned up some commits because of that).

[frenck]

Thanks, @cronjefourie 👍

../Frenck

Comments addressed