-
-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Conversation
Hey there @flacjacket, mind taking a look at this pull request as it has been labeled with an integration ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
AmcrestSensorEntityDescription( | ||
key=_DOORBELL_KEY, | ||
name=_DOORBELL_NAME, | ||
device_class=BinarySensorDeviceClass.OCCUPANCY, | ||
event_code=_DOORBELL_EVENT_CODE, | ||
), |
There was a problem hiding this comment.
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
- https://github.com/home-assistant/architecture/blob/master/adr/0007-integration-config-yaml-structure.md
- https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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! :)
There was a problem hiding this comment.
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! 鉂わ笍
There was a problem hiding this comment.
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. :)
There was a problem hiding this comment.
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
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
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: