8000 Add motion sensor setting to tplink by rytilahti · Pull Request #129393 · home-assistant/core · GitHub
[go: up one dir, main page]

Skip to content

Add motion sensor setting to tplink #129393

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

Merged
merged 5 commits into from
Nov 6, 2024
Merged

Add motion sensor setting to tplink #129393

merged 5 commits into from
Nov 6, 2024

Conversation

rytilahti
Copy link
Member

Proposed change

This PR adds a new switch to control the motion detection sensor found on some dimmers.

Related upstream PR: python-kasa/python-kasa#1174

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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @bdraco, @sdb9696, mind taking a look at this pull request as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tplink can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign tplink Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@rytilahti rytilahti marked this pull request as draft October 29, 2024 08:54
@rytilahti rytilahti added the waiting-for-upstream We're waiting for a change upstream label Oct 29, 2024
@rytilahti
Copy link
Member Author

Required version bump shipped in #129817, so marking this as ready for review.

8000

@rytilahti rytilahti marked this pull request as ready for review November 4, 2024 23:18
@rytilahti rytilahti removed the waiting-for-upstream We're waiting for a change upstream label Nov 4, 2024
Comment on lines 191 to 192
"pir_enabled": {
"name": "PIR enabled"
Copy link
Member

Choose a reason for hiding this comment

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

It feels strange to call this PIR enabled, since it's not enabled, the switch decides if its enabled

Choose a reason for hiding this comment

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

IMO, this is correct. The goal of this PR is to control the state of the motion sensor in the switch (enabled/disabled). This is a user setting, and the user decides if PIR should be enabled or disabled for the switch. You can control it from the Kasa app, and with this PR you can also control it via HA.

Here is how it looks in the Kasa app:

Photos_2024-11-05_06-24-46

Instead of PIR enabled we can name it Motion Sensor for consistency. But I'm fine with any name.

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed conflicts and renamed this to "Motion sensor". It is not consistent with some other X enabled switches, but it's more understandable than rather technical PIR so I think it's an improvement.

Copy link
Member
@joostlek joostlek left a comment

Choose a reason for hiding this comment

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

There's a merge conflict

@home-assistant home-assistant bot marked this pull request as draft November 5, 2024 14:42
@home-assistant
Copy link
home-assistant bot commented Nov 5, 2024

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.

@rytilahti rytilahti marked this pull request as ready for review November 6, 2024 11:23
@home-assistant home-assistant bot requested a review from joostlek November 6, 2024 11:23
@joostlek joostlek merged commit c6cb288 into dev Nov 6, 2024
31 of 32 checks passed
@joostlek joostlek deleted the tplink/feat/pir_feature branch November 6, 2024 12:40
@github-actions github-actions bot locked and limited conversation to collaborators Nov 7, 2024
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.

4 participants
0