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

Scan QR code to log in And Migrate Tuya integration to new sharing SDK #104767

Merged
merged 6 commits into from
Jan 30, 2024

Conversation

shihuimiao
Copy link
Contributor

@shihuimiao shihuimiao commented Nov 30, 2023

Breaking change

You need to re-authenticate the Home Assistant Tuya integration with your Smart Life app or Tuya Smart app after the upgrade.

image

image

Proposed change

This PR moves the Tuya integration onto the new sharing SDK, which removes the need for a developer account and can directly log users in by scanning a QR code using the Smart Life app or Tuya Smart app.

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:

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:

@home-assistant
Copy link

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.

Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate of #103007 ?

I'm confused this is coming from you guys like this, especially since there was feedback asked, provided and without any responses something totally different comes in.

We cannot go this route, it is fully breaking for users on upgrade, which is not acceptable. We've provided a possible path (and #103007 shows that path is possible), yet this is completely ignored.

../Frenck

@home-assistant
Copy link

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.

@home-assistant home-assistant bot marked this pull request as draft November 30, 2023 03:01
@shihuimiao
Copy link
Contributor Author

Duplicate of #103007 ?

I'm confused this is coming from you guys like this, especially since there was feedback asked, provided and without any responses something totally different comes in.

We cannot go this route, it is fully breaking for users on upgrade, which is not acceptable. We've provided a possible path (and #103007 shows that path is possible), yet this is completely ignored.

../Frenck

The changes here support the Tuya Smart app and have upgraded the SDK version. After email communication, we thought we would resubmit a new PR.
so we have raised a new one. We have also undergone local testing, so please take a look. Sincerely

@frenck
Copy link
Member

frenck commented Nov 30, 2023

As far as I am aware there has not been follow up from Tuya on the email communication.

As said, this PR is not acceptable, and will not be reviewed at this point in time.

Please recheck the email communication and the above linked PR (from which parts of this code was copied), for the suggested route to take.

Thanks!

../Frenck

@shihuimiao
Copy link
Contributor Author

As far as I am aware there has not been follow up from Tuya on the email communication.

As said, this PR is not acceptable, and will not be reviewed at this point in time.

Please recheck the email communication and the above linked PR (from which parts of this code was copied), for the suggested route to take.

Thanks!

../Frenck

There may have been some misunderstandings in our previous communications. Allow me to clarify the situation.

The code I submitted for this pull request supports both the Tuya Smart app and the Smart Life app(instead of only Smart Life app). This means that all the existing users can scan the QR code and log in through either app after upgrading. Based on my understanding, there should be no disruption for existing users, so we don't need to deal with the "deprecation period" concerns, and we have tested it locally.

Based on the reasons mentioned above, please help review if any further modifications are needed for this pull request or if the changes still need to be updated in #103007?

Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
If you are the author of this PR, please leave a comment if you want to keep it open. Also, please rebase your PR onto the latest dev branch to ensure that it's up to date with the latest changes.
Thank you for your contribution!

@github-actions github-actions bot added the stale label Jan 29, 2024
@frenck frenck changed the base branch from dev to tuya-sharing-sdk January 30, 2024 19:04
@frenck frenck marked this pull request as ready for review January 30, 2024 19:04
@home-assistant home-assistant bot requested a review from frenck January 30, 2024 19:04
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @shihuimiao 👍

I've created a tuya-sharing-sdk branch that will be used as an intermediate branch to put this code in. From there on, I'll update the code with a few changes to our frontend and standards. The result of that, I will put up as a new PR against our dev branches.

../Frenck

@frenck
Copy link
Member

frenck commented Jan 30, 2024

Removed the breaking-change flag, as this is going into an intermediate branch.

@frenck frenck merged commit 2df4c86 into home-assistant:tuya-sharing-sdk Jan 30, 2024
3 checks passed
balloob pushed a commit that referenced this pull request Jan 31, 2024
* Scan QR code to log in And Migrate Tuya integration to new sharing SDK (#104767)

* Remove non-opt-in/out reporting

* Improve setup, fix unload

* Cleanup token listner, remove logging of sensitive data

* Collection of fixes after extensive testing

* Tests happy user config flow path

* Test unhappy paths

* Add reauth

* Fix translation key

* Prettier manifest

* Ruff format

* Cleanup of const

* Process review comments

* Adjust update token handling

---------

Co-authored-by: melo <411787243@qq.com>
@github-actions github-actions bot locked and limited conversation to collaborators Jan 31, 2024
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.

None yet

2 participants