Skip to content

Set has entity name to True in Meater #146954

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
Jun 25, 2025
Merged

Conversation

joostlek
Copy link
Member

@joostlek joostlek commented Jun 16, 2025

Proposed change

Set has entity name to True in Meater, this was forgotten in PR #95732

Also truncate the device id when generating device name because it is very very long, making it not user friendly.

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:
  • Link to developer documentation pull request:
  • Link to frontend 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 @Sotolotl, @emontnemery, mind taking a look at this pull request as it has been labeled with an integration (meater) you are listed as a code owner for? Thanks!

Code owner commands

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

@@ -189,7 +190,7 @@ def __init__(
},
manufacturer="Apption Labs",
model="Meater Probe",
name=f"Meater Probe {device_id}",
name=f"Meater Probe {device_id[:8]}",
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we know it's safe to truncate the device ID like this? If we end up with several sensors with the same entity_id (but suffixed by a number) it's a huge mess for users to untangle.

Copy link
Contributor

Choose a reason for hiding this comment

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

We discussed this a bit and it's probably fine to do the truncation even if we risk device name collisions.

@abmantis abmantis marked this pull request as draft June 16, 2025 16:33
@abmantis
Copy link
Member

Marking this as draft since there are merge conflicts.

joostlek added 2 commits June 16, 2025 18:38
# Conflicts:
#	tests/components/meater/snapshots/test_sensor.ambr
Copy link
Contributor

Choose a reason for hiding this comment

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

Why are there so many changes to the snapshots?

Copy link
Member Author

Choose a reason for hiding this comment

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

Because has entity name was turned off and there were translations so stuff just went south

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't understand what that means.
Can you elaborate?

Copy link
Contributor

Choose a reason for hiding this comment

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

OK, so the issue was that the entity translations did not work because the PR adding them did not set has_entity_name to True

@joostlek joostlek marked this pull request as ready for review June 16, 2025 17:10
@zweckj
Copy link
Member

zweckj commented Jun 16, 2025

@joostlek conflicts

joostlek added 2 commits June 25, 2025 08:52
# Conflicts:
#	tests/components/meater/snapshots/test_sensor.ambr
@emontnemery emontnemery merged commit 7031167 into home-assistant:dev Jun 25, 2025
33 of 34 checks passed
@joostlek joostlek deleted the meat-ham branch June 25, 2025 06:59
@github-actions github-actions bot locked and limited conversation to collaborators Jun 26, 2025
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