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

Fix int value in unique_id for Tellduslive #127526

Merged
merged 2 commits into from
Oct 4, 2024
Merged

Fix int value in unique_id for Tellduslive #127526

merged 2 commits into from
Oct 4, 2024

Conversation

robinostlund
Copy link
Contributor

@robinostlund robinostlund commented Oct 4, 2024

Proposed change

This fixes #127478 which was caused by #125987.

Issue is that self._id is a list which contains int values and #125987 expects that the values should be strings.

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

home-assistant bot commented Oct 4, 2024

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

Code owner commands

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

@@ -194,4 +194,4 @@ def native_value(self):
@property
def unique_id(self) -> str:
"""Return a unique ID."""
return "-".join(self._id)
return "-".join(map(str, self._id))
Copy link
Member

Choose a reason for hiding this comment

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

We should do a migration for the unique_ids that are an integer, otherwise it will create duplicate entities

Copy link
Member

Choose a reason for hiding this comment

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

Example for an unique_id migration: #122330

Copy link
Contributor Author

@robinostlund robinostlund Oct 4, 2024

Choose a reason for hiding this comment

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

That is out of my skills, but i have confirmed that this change doesn't create duplicate entities. It returns the same value as before so the entities is the same. This was the return before 2024.10 when it was working return "{}-{}-{}".format(*self._id) so i don't know if a migration is necessary as it will return the same value as before?

Copy link
Member

Choose a reason for hiding this comment

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

But this way can't produce an int as unique_id, unless self._id is not a list

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ahaa so you wan't to keep the int value? and migrate the existing ones that where all strings to use int in the unique id instead?

Copy link
Member

Choose a reason for hiding this comment

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

No we want it to be a string, but what I am wondering about, this can only return an integer when self._id only returns a single value. So I think the change itself is doing something wrong. When you run this code, do you see what the unique_id of the entity ends up being?

Copy link
Member

Choose a reason for hiding this comment

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

Oh I think I see what you mean, this looks good

@home-assistant home-assistant bot marked this pull request as draft October 4, 2024 07:06
@home-assistant
Copy link

home-assistant bot commented Oct 4, 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.

@robinostlund robinostlund marked this pull request as ready for review October 4, 2024 07:12
@home-assistant home-assistant bot requested a review from joostlek October 4, 2024 07:12
@epenet epenet added this to the 2024.10.1 milestone Oct 4, 2024
@@ -194,4 +194,4 @@ def native_value(self):
@property
def unique_id(self) -> str:
"""Return a unique ID."""
return "-".join(self._id)
return "-".join(map(str, self._id))
Copy link
Member

Choose a reason for hiding this comment

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

Oh I think I see what you mean, this looks good

Copy link
Contributor

@epenet epenet left a comment

Choose a reason for hiding this comment

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

LGTM 👍
cc @albertomontesg as author of offending PR.

@joostlek joostlek merged commit 64ea029 into home-assistant:dev Oct 4, 2024
28 of 30 checks passed
frenck pushed a commit that referenced this pull request Oct 4, 2024
@frenck frenck mentioned this pull request Oct 4, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 5, 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.

Tellstick 433MHz temp sensor values no longer registered
4 participants