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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Mutesync dynamic update interval and catch invalid response values #50764

Merged
merged 3 commits into from Jun 17, 2021

Conversation

bramkragten
Copy link
Member

Proposed change

This PR sets the update interval to 10 seconds by default, but to 1 second when in a meeting.

The client sometimes returns None, at least for muted, and this resulted in the binary_sensor going to off. We now throw when we get a None value during an update.

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: 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
  • 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:

@project-bot project-bot bot added this to Needs review in Dev May 17, 2021
@probot-home-assistant
Copy link

Hey there @currentoor, mind taking a look at this pull request as its been labeled with an integration (mutesync) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

Copy link
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

Looks good!

Dev automation moved this from Needs review to Reviewer approved Jun 17, 2021
@MartinHjelmare MartinHjelmare changed the title Mutesync: dynamic update interval and catch invalid response values Add Mutesync dynamic update interval and catch invalid response values Jun 17, 2021
@MartinHjelmare MartinHjelmare merged commit 0327d0b into dev Jun 17, 2021
Dev automation moved this from Reviewer approved to Done Jun 17, 2021
@MartinHjelmare MartinHjelmare deleted the mutesync branch June 17, 2021 09:40
@github-actions github-actions bot locked and limited conversation to collaborators Jun 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Dev
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants