Skip to content

Sensors name are outdated #36521

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

Closed
dapuzz opened this issue Dec 23, 2024 · 2 comments · Fixed by #36525
Closed

Sensors name are outdated #36521

dapuzz opened this issue Dec 23, 2024 · 2 comments · Fixed by #36525

Comments

@dapuzz
Copy link

dapuzz commented Dec 23, 2024

Feedback

I think that sensor.transmission_current_status is now named just as sensor.transmission_status

Please pay attantion entity names have been translated, so in italian I have sensor.transmission_stato, and this breaks the custom lovelace card. Not sure translating entity name is always a good idea.

Thank you very much for your work.
Bye

URL

https://www.home-assistant.io/integrations/transmission/

Version

2024.12.5

Additional information

No response

@home-assistant
Copy link

Hey there @engrbm87, @JPHutchins, mind taking a look at this feedback as it has been labeled with an integration (transmission) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of transmission can trigger bot actions by commenting:

  • @home-assistant close Closes the feedback.
  • @home-assistant rename Awesome new title Renames the feedback.
  • @home-assistant reopen Reopen the feedback.
  • @home-assistant unassign transmission Removes the current integration label and assignees on the feedback, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information) to the feedback.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information) on the feedback.

@frenck
Copy link
Member

frenck commented Dec 23, 2024

so in italian I have sensor.transmission_stato, and this breaks the custom lovelace card.

This is an issue with the custom card, not the integration or documentation. Users can change entity IDs or might have multiple instances of integrations running (using multiple transmissions on different locations). It is up to the custom card to handle this.

I'll open up a PR to adjust the documentation on our end.

../Frenck

@github-actions github-actions bot locked and limited conversation to collaborators Jan 24, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants