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

Drop fritzdect integration #31359

Merged
merged 1 commit into from Jan 31, 2020
Merged

Drop fritzdect integration #31359

merged 1 commit into from Jan 31, 2020

Conversation

@escoand
Copy link
Contributor

escoand commented Jan 31, 2020

Breaking change

The integration fritzdect isn't available anymore.

Proposed change

The fritzdect integration is doing the exact same as fritzbox but the latter can do additional things.

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

Example entry for configuration.yaml:

Change this:

# Example configuration.yaml
switch:
  - platform: fritzdect
    username: YOUR_USERNAME
    password: YOUR_PASSWORD

to this:

# Example configuration.yaml
fritzbox:
  devices:
    - host: fritz.box
      username: YOUR_USERNAME
      password: YOUR_PASSWORD

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
Dev automation moved this from Needs review to Reviewer approved Jan 31, 2020
@balloob balloob merged commit d225fc0 into home-assistant:dev Jan 31, 2020
11 checks passed
11 checks passed
CI Build #20200131.64 succeeded
Details
CI (FullCheck Mypy) FullCheck Mypy succeeded
Details
CI (FullCheck Pylint) FullCheck Pylint succeeded
Details
CI (Overview CheckFormat) Overview CheckFormat succeeded
Details
CI (Overview Lint) Overview Lint succeeded
Details
CI (Overview Validate) Overview Validate succeeded
Details
CI (Tests PyTest Python37) Tests PyTest Python37 succeeded
Details
cla-bot Everyone involved has signed the CLA
codecov/patch Coverage not affected when comparing 1d537ad...13bf766
Details
codecov/project 94.63% (target 90%)
Details
docs-missing Documentation ok.
Dev automation moved this from Reviewer approved to Done Jan 31, 2020
@lock lock bot locked and limited conversation to collaborators Feb 2, 2020
@escoand escoand deleted the escoand:fritzdect_drop branch Feb 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Dev
  
Done
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can鈥檛 perform that action at this time.