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

Use entity name in Airzone Cloud sensors #95102

Merged
merged 3 commits into from Jun 23, 2023

Conversation

Noltari
Copy link
Contributor

@Noltari Noltari commented Jun 23, 2023

Proposed change

Use entity name in Airzone Cloud sensors.

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:

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
@Noltari Noltari changed the title airzone_cloud: sensor: use entity name Use entity name in Airzone Cloud sensors Jun 23, 2023
homeassistant/components/airzone_cloud/sensor.py Outdated Show resolved Hide resolved
homeassistant/components/airzone_cloud/sensor.py Outdated Show resolved Hide resolved
homeassistant/components/airzone_cloud/sensor.py Outdated Show resolved Hide resolved
homeassistant/components/airzone_cloud/sensor.py Outdated Show resolved Hide resolved
@home-assistant home-assistant bot marked this pull request as draft June 23, 2023 10:16
@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.

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
@Noltari Noltari marked this pull request as ready for review June 23, 2023 10:41
@home-assistant home-assistant bot requested a review from frenck June 23, 2023 10:41
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
@Noltari Noltari marked this pull request as draft June 23, 2023 11:49
@Noltari Noltari marked this pull request as ready for review June 23, 2023 11:57
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

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

Thanks, @Noltari 👍

../Frenck

@frenck frenck merged commit e5c1ce6 into home-assistant:dev Jun 23, 2023
23 checks passed
@Noltari Noltari deleted the airzone-cloud-sensor-entity-name branch June 23, 2023 12:30
@github-actions github-actions bot locked and limited conversation to collaborators Jun 24, 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

2 participants