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

Use DEVICE_CLASS_DOOR and DEVICE_CLASS_SMOKE in various integrations #39950

Merged
merged 3 commits into from
Sep 12, 2020

Conversation

springstan
Copy link
Member

Breaking change

Proposed change

Use DEVICE_CLASS_DOOR and DEVICE_CLASS_SMOKE in various integrations

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:

# Example configuration.yaml

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:

@probot-home-assistant
Copy link

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

@@ -89,7 +92,7 @@ def name(self):
@property
def icon(self):
"""Icon for device by its type."""
if self._zone_type == "smoke":
if self._zone_type == DEVICE_CLASS_SMOKE:
Copy link
Member

Choose a reason for hiding this comment

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

Odd that this takes arbitrary strings for the zone type.

Copy link
Member

Choose a reason for hiding this comment

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

The zone type is not validated as a device class string. Then we shouldn't compare with our device class constants either.

@bdraco bdraco merged commit 1bb5d47 into home-assistant:dev Sep 12, 2020
@springstan springstan deleted the use-device-class-smoke-door branch September 12, 2020 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants