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

Switcher add current current temperature sensor #130653

Merged
merged 3 commits into from
Nov 15, 2024

Conversation

YogevBokobza
Copy link
Contributor

@YogevBokobza YogevBokobza commented Nov 14, 2024

Proposed change

Adding a sensor for the current temperature of Thermostat Switcher 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)
  • 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

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 @thecode, mind taking a look at this pull request as it has been labeled with an integration (switcher_kis) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of switcher_kis 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 switcher_kis 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.

Copy link
Member

@thecode thecode left a comment

Choose a reason for hiding this comment

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

Temperature is already provided by the climate entity -

self._attr_current_temperature = data.temperature

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

@home-assistant home-assistant bot marked this pull request as draft November 14, 2024 21:28
@YogevBokobza
Copy link
Contributor Author

YogevBokobza commented Nov 14, 2024

Temperature is already provided by the climate entity -

self._attr_current_temperature = data.temperature

I think it is easier to work with a sensor entity rather than searching the entity's attributes, especially for using in automations.
I can remove this from the climate attributes if you worry about duplication.

Plus, this temperature is by no means the "device's temperature" it is shows the outside temperature.. I think it makes more sense to make it its own sensor.

@YogevBokobza
Copy link
Contributor Author

The end results look like this:
image

@YogevBokobza YogevBokobza marked this pull request as ready for review November 15, 2024 16:46
@frenck frenck self-requested a review November 15, 2024 16:48
@frenck
Copy link
Member

frenck commented Nov 15, 2024

Removed my accidental approval, awaiting approval from @thecode

@thecode
Copy link
Member

thecode commented Nov 15, 2024

To be honest I don't like creating sensors from climate entity since this opens a path for creating sensors for rare cases instead of templates, however since Home Assistant allows creating temperature sensor for the climate entity, mainly to allow long term statistics for this sensor I am approving this PR.

Please note that future sensors for the climate entity will be rejected (I already saw a request for a binary sensor if the AC is on)

Thanks

@thecode
Copy link
Member

thecode commented Nov 15, 2024

@YogevBokobza once again I ask, please avoid constantly force pushing a branch for no reason, this has already pass tests, so no need to force push the branch

@YogevBokobza
Copy link
Contributor Author

@YogevBokobza once again I ask, please avoid constantly force pushing a branch for no reason, this has already pass tests, so no need to force push the branch

It seems like I had to.. it was failing on something weird not related to this PR

@YogevBokobza
Copy link
Contributor Author

@YogevBokobza once again I ask, please avoid constantly force pushing a branch for no reason, this has already pass tests, so no need to force push the branch

It seems like I had to.. it was failing on something weird not related to this PR

@thecode Failed again on this "CI / Upload test coverage to Codecov (partial suite) (pull_request)" do you know what this is and how to resolve it?

@frenck frenck merged commit 6279979 into home-assistant:dev Nov 15, 2024
29 of 30 checks passed
@YogevBokobza YogevBokobza deleted the switcher-add-temp-sensor branch November 15, 2024 21:18
silamon pushed a commit to silamon/core that referenced this pull request Nov 16, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Nov 16, 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.

3 participants