-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
Add DROP Alert product support #117867
Add DROP Alert product support #117867
Conversation
Hey there @ChandlerSystems, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
@@ -31,6 +31,7 @@ | |||
"pending_notification": { "name": "Notification unread" }, | |||
"reserve_in_use": { "name": "Reserve capacity in use" }, | |||
"salt": { "name": "Salt low" }, | |||
"alert_sensor": { "name": "Sensor" }, |
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.
We should use a better name for it and not "Sensor", similar to "Leak detected"
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.
The generic naming of the sensor input on this device is intentional based on the many ways that it can be used on a DROP system. For example, it can be used with a float switch to detect rising a water level in a sump pit, notify users that pump equipment has entered a fault state, detect water intrusion, or shut off the water due to a dry contact closure on an alarm panel. Because of this, the sensor input really doesn't have a better name that wouldn't be incorrect in some cases. We spent quite a bit of time considering alternatives when the marketing plan for the device was formed and decided it was better to be vague instead of misleading.
That being said, we're open to suggestions but haven't come up with anything that is an improvement.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
@@ -31,6 +31,7 @@ | |||
"pending_notification": { "name": "Notification unread" }, | |||
"reserve_in_use": { "name": "Reserve capacity in use" }, | |||
"salt": { "name": "Salt low" }, | |||
"alert_sensor": { "name": "Sensor" }, |
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.
Please keep the keys alphabetically sorted, it's annoying to have to go through the entire map to check if something is there or not.
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.
Addressed in 0abb8e1
), | ||
DROPBinarySensorEntityDescription( | ||
key=POWER, | ||
translation_key=POWER, |
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.
Did you forget to add this to strings.json
, or should it be alert_sensor
here instead?
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.
No, the power monitoring feature is separate from the alert_sensor
input. We intend for the power monitoring sensor to simply be labeled 'Power', so no entry in strings.json
is necessary.
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.
OK, that makes sense. However, if the entity name is not translated, you should not set the translation_key
.
Maybe something like this, so it's clear from the code it's intentional to not set the name.
DROPBinarySensorEntityDescription(
key=POWER,
translation_key=None, # Use name provided by binary sensor device class
device_class=BinarySensorDeviceClass.POWER,
value_fn=lambda device: device.drop_api.power(),
),
), | ||
DROPBinarySensorEntityDescription( | ||
key=POWER, | ||
translation_key=POWER, |
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.
translation_key=POWER, | |
translation_key=None, # Use name provided by binary sensor device class |
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.
Changed in 36db6c6
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.
Thanks, @pfrazer 👍
* dev: (642 commits) Improve config flow type hints (part 4) (home-assistant#124348) Improve config flow type hints (part 1) (home-assistant#124343) Add tests for Bring integration (home-assistant#123087) Add DROP Alert product support (home-assistant#117867) update ttn_client - fix crash with SenseCAP devices (home-assistant#124370) Add Aranet Radon Plus support (home-assistant#124197) Fix Spotify Media Browsing fails for new config entries (home-assistant#124368) Convert Bang & Olufsen testing logging patches to caplog (home-assistant#124366) Remove unneeded check for Bang & Olufsen events and device update (home-assistant#124363) Bump async-interrupt to 1.2.0 (home-assistant#124360) Rename OpenThermGatewayDevice to OpenThermGatewayHub (home-assistant#124361) Fix Weatherflow Cloud lightning (home-assistant#124082) Change POWER_VOLT_AMPERE_REACTIVE to UnitOfReactivePower (home-assistant#117153) Disable Habitica deprecated entities by default (home-assistant#123522) Add test cases for ViCare entities (home-assistant#122983) Add tests for IronOS integration (home-assistant#123078) Fix state name for binary_sensor Power from clear/detected to on/off (home-assistant#116994) Extend blebox shutterbox tilt support (home-assistant#110547) blebox: use blebox_uniapi.cover.BleboxCoverState enum members instead of plain integers (home-assistant#124302) Add custom panel for LCN configuration (home-assistant#108664) ...
Proposed change
Add support for a new DROP product: DROP Alert
Type of change
Additional information
Checklist
ruff format 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
.To help with the load of incoming pull requests: