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

New amcrest binary sensor to monitor doorbell button #66302

Merged
merged 2 commits into from
Feb 11, 2022

Conversation

PanicRide
Copy link
Contributor

Proposed change

This integration can now use a binary sensor to monitor the state of a built-in doorbell button found on some Amcrest camera devices.

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

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

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 Feb 11, 2022
@probot-home-assistant
Copy link

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

@MartinHjelmare MartinHjelmare changed the title New binary sensor to monitor doorbell button New amcrest binary sensor to monitor doorbell button Feb 11, 2022
Copy link
Member

@Kane610 Kane610 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 Feb 11, 2022
Copy link
Contributor

@flacjacket flacjacket left a comment

Choose a reason for hiding this comment

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

Nice!

@Kane610 Kane610 merged commit 0797533 into home-assistant:dev Feb 11, 2022
Dev automation moved this from Reviewer approved to Done Feb 11, 2022
Comment on lines +118 to +123
AmcrestSensorEntityDescription(
key=_DOORBELL_KEY,
name=_DOORBELL_NAME,
device_class=BinarySensorDeviceClass.OCCUPANCY,
event_code=_DOORBELL_EVENT_CODE,
),
Copy link
Member

@frenck frenck Feb 12, 2022

Choose a reason for hiding this comment

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

This PR violated ADR-0007 and ADR-0010

This integration still uses a platform configuration and adding a sensor here affects YAML options for this integration. Additionally, it probably violates ADR-0003 as well, as this could be considered a monitored condition (which is also no longer allowed).

I suggest reverting this PR @Kane610 @PanicRide @flacjacket, as we no longer allow integrations to add or change a platform YAML configuration.

Copy link
Member

Choose a reason for hiding this comment

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

Dang it! So much for helping with the review effort, sorry... I'll revert it tonight

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Aww... so much for finding something simple for my first contribution.

Don't worry, I still love you @frenck! :)

Copy link
Member

Choose a reason for hiding this comment

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

Well, it's not personal @PanicRide! I definitely am thankful for the willingness to contribute! 鉂わ笍

Copy link
Contributor Author

Choose a reason for hiding this comment

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

After reading those ADR documents, I agree with the concepts. I just wasn't aware of them. I don't take it personally. :)

Copy link
Member

Choose a reason for hiding this comment

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

New PR to revert published

Kane610 added a commit to Kane610/home-assistant that referenced this pull request Feb 12, 2022
@Kane610 Kane610 mentioned this pull request Feb 12, 2022
22 tasks
@github-actions github-actions bot locked and limited conversation to collaborators Feb 13, 2022
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

5 participants