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

Add yolink siren battery entity #99310

Merged
merged 2 commits into from Sep 10, 2023

Conversation

matrixd2
Copy link
Contributor

@matrixd2 matrixd2 commented Aug 30, 2023

Proposed change

Add Siren device battery entity.

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)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

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
  • I have followed the perfect PR recommendations
  • 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.

To help with the load of incoming pull requests:

@MartinHjelmare MartinHjelmare changed the title Add siren battery entity Add yolink siren battery entity Aug 30, 2023
Copy link
Member

@MartinHjelmare MartinHjelmare left a comment

Choose a reason for hiding this comment

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

The PR title doesn't match the change. We're not adding a new battery sensor for the siren.

and state.get("powerSupply") == "usb"
):
# When the power supply mode is usb, the power information is wrong
state["battery"] = None
Copy link
Member

Choose a reason for hiding this comment

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

We shouldn't modify to correct the data coming from the api. If it needs adjustment it should be done in the device library.

Is this a device that can both be powered by USB and battery and power supply can change during the entity lifetime?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks, I will change on API library, When the device has a battery installed and is powered by USB, the battery power obtained is inaccurate.

Copy link
Contributor Author

@matrixd2 matrixd2 Aug 30, 2023

Choose a reason for hiding this comment

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

I think just remove message convert is fine, When a battery is installed in the device, if device changed to USB power supply, if device battery level displayed as unavailable, which is unreasonable.

Copy link
Member

Choose a reason for hiding this comment

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

Is this the current behavior, that the sensor becomes unavailable if the power supply changes to USB? Where is the logic for this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

At my first commit, I tried to change siren battery entity value to None (unavailable) when device power supply change to USB, I think that is incorrect, When a battery is installed in the device, should not change siren battery entity to None even if the battery information is not correct(circuit design leads to),So I think just remove message convert is fine. No API library changes required.

Copy link
Member

Choose a reason for hiding this comment

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

Setting the value None as the sensor native value will be translated to unknown state in the base entity class, not unavailable state.

Copy link
Member

Choose a reason for hiding this comment

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

Ok.

@home-assistant home-assistant bot marked this pull request as draft August 30, 2023 05:06
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@MartinHjelmare
Copy link
Member

The PR title doesn't match the change. We're not adding a new battery sensor for the siren.

Nevermind this comment. I misread the change. It is a new sensor.

@MartinHjelmare
Copy link
Member

Please mark the PR as ready for review when it's ready to merge.

@matrixd2 matrixd2 marked this pull request as ready for review August 30, 2023 09:03
Copy link
Member

@Quentame Quentame left a comment

Choose a reason for hiding this comment

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

LGTM 😊

@Quentame Quentame merged commit 45fc158 into home-assistant:dev Sep 10, 2023
21 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Sep 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants