Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tuya v2 integration Update #53498

Closed
wants to merge 3 commits into from
Closed

Tuya v2 integration Update #53498

wants to merge 3 commits into from

Conversation

zlinoliver
Copy link
Contributor

@zlinoliver zlinoliver commented Jul 26, 2021

Breaking change

Tuya Smart always strive to provide the best development experience possible and keep updating our Home Assistant integration capabilities. Since the old version of Tuya Home Assistant integration supports limited categories and control commands, now we bring you our new integration with extended support for more categories and commands.

Our new integration is built on Tuya’s standard Open APIs and tackles the limits of categories and accessible control commands. We deliver more development-friendly features including virtual device debugging, official authorization, and technical supports, which will help you efficiently work on development with the Tuya ecosystem.

The existing Tuya Integration is no longer maintained by Tuya officially, and will be deprecated. The estimated deprecation date is 2021.12.31. The new integration will be officially maintained by the Tuya Developer Team, for more information of the migration, please check this documentation How to Migrate the Tuya Home Assistant Integration from the Old Version

Proposed change

As we discussed with Paulus previously, it's the minimum viable integration that allows it to be configured via a config flow. Include a small integration to make sure it all works.

  • Supported Device Category

  • Support Scene feature

  • Support new device pairing status refresh

  • Support Tuya smart home cloud project type

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)
  • 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:
  1. Fixed the issue where contact sensors cannot be added. [nmap based device tracking plugin #14][Device tracker are case sensitive #37]
  2. Fixed the issues where some color lights cannot be turned on. [Refactor device components #42]
  3. Fixed the issues where some humidifiers cannot work correctly. [Add configurable intervals to device tracker. #36]
  4. Support current, power, voltage on some device, like socket, power strip and switch #17
  5. Support vacuum #9
  6. Support Thermostat #7
  7. Support Pet Water Feeder #23
  8. Fix AC shows incorrect temperature #15
  • 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
  • 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:

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

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

@probot-home-assistant
Copy link

Hey there @ollo69, 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!
(message by CodeOwnersMention)

@ollo69
Copy link
Contributor

ollo69 commented Jul 26, 2021

It is not more logic create a new integration instead try to merge the new V2 in the old version?

@frenck
Copy link
Member

frenck commented Jul 26, 2021

@ollo69 The core team is in touch with the development team @ Tuya and we have a plan for this all. It has been discussed, but thanks for thinking along 👍

@frenck
Copy link
Member

frenck commented Jul 26, 2021

@zlinoliver This should have been targeting the branch @balloob created for you and not dev, right?
Additionally, we should follow or general PR rules, even with an intermediate branch:

https://developers.home-assistant.io/docs/creating_component_code_review/#5-make-your-pull-request-as-small-as-possible

As this becomes too large to review otherwise.

@zlinoliver
Copy link
Contributor Author

@zlinoliver This should have been targeting the branch @balloob created for you and not dev, right?
Additionally, we should follow or general PR rules, even with an intermediate branch:

https://developers.home-assistant.io/docs/creating_component_code_review/#5-make-your-pull-request-as-small-as-possible

As this becomes too large to review otherwise.

Hi @frenck , sorry for the mistake, I have recreated a new PR for the update: #53510, please check this one. This PR includes all the necessary functionalities of the old Tuya integration, includes login, device list fetching, device status update, etc. Cannot break it into a smaller PR now. Let me know if you have other thoughts, thanks!

@zlinoliver zlinoliver closed this Jul 26, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants