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

Bump python-myq to 3.1.11 #101266

Merged
merged 1 commit into from
Oct 2, 2023
Merged

Bump python-myq to 3.1.11 #101266

merged 1 commit into from
Oct 2, 2023

Conversation

Lash-L
Copy link
Contributor

@Lash-L Lash-L commented Oct 2, 2023

Breaking change

Proposed change

Changes: Python-MyQ/Python-MyQ@v3.1.9...v3.1.11

Summary:

Automatically change domains when one fails in certain situations
Reset user agent when we re-authenticate
Scrape and add __RequestVerificationToken to login
Switch to api v6
When we get a 429 error - back off instead of continuing to hammer the servers when we are rate limited.

Big thanks to all the users who helped me iteratively test to get to this point as I was unable.

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

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:

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

home-assistant bot commented Oct 2, 2023

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

Code owner commands

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

Copy link
Contributor

@edenhaus edenhaus left a comment

Choose a reason for hiding this comment

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

Thanks @Lash-L 👍

@edenhaus edenhaus merged commit 0544077 into home-assistant:dev Oct 2, 2023
@frenck frenck added this to the 2023.10.0 milestone Oct 2, 2023
frenck pushed a commit that referenced this pull request Oct 2, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2023
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.

MyQ Integration Receiving 403 Forbidden After Upgrading to 2023.9.X MyQ login error: 401 Unauthorized
3 participants