Skip to content

Conversation

@chemelli74
Copy link
Contributor

@chemelli74 chemelli74 commented Dec 17, 2025

Proposed change

Add missing strings for Shelly voltmeter sensor:

image

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

  • I understand the code I am submitting and can explain how it works.
  • 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.
  • Any generated code has been carefully reviewed for correctness and compliance with project standards.

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

Code owner commands

Code owners of shelly 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 shelly 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
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR adds missing translation strings for Shelly voltmeter sensors that have channel names. These strings are automatically used by the configure_translation_attributes() method in the Shelly entity base class, which appends _with_channel_name to translation keys when a device has multiple channels.

Key changes:

  • Adds two new translation keys for voltmeter sensors with channel name placeholders

Comment on lines +541 to +544
"name": "Voltmeter value {channel_name}"
},
"voltmeter_with_channel_name": {
"name": "Voltmeter {channel_name}"
Copy link

Copilot AI Dec 17, 2025

Choose a reason for hiding this comment

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

The naming pattern for these translation strings is inconsistent with the established pattern in this file. All other _with_channel_name entries place the channel name placeholder at the beginning (e.g., "{channel_name} pulse counter value", "{channel_name} power factor"), but these new entries place it at the end ("Voltmeter value {channel_name}", "Voltmeter {channel_name}").

For consistency, these should be:

  • "voltmeter_value_with_channel_name": "name": "{channel_name} voltmeter value"
  • "voltmeter_with_channel_name": "name": "{channel_name} voltmeter"
Suggested change
"name": "Voltmeter value {channel_name}"
},
"voltmeter_with_channel_name": {
"name": "Voltmeter {channel_name}"
"name": "{channel_name} voltmeter value"
},
"voltmeter_with_channel_name": {
"name": "{channel_name} voltmeter"

Copilot uses AI. Check for mistakes.
@zweckj zweckj merged commit c8636ee into home-assistant:dev Dec 18, 2025
42 checks passed
@chemelli74 chemelli74 deleted the chemelli74-shelly-voltmeter branch December 18, 2025 22:23
@bramkragten bramkragten mentioned this pull request Dec 19, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Dec 20, 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.

6 participants