Malformed title key for "Energenie Power Sockets" integration

[NoRi2909]

The problem

The title key of the "Energenie Power Sockets" integration is currently

core/homeassistant/components/energenie_power_sockets/strings.json

Line 2 in 5172139

"title": "Energenie Power Sockets Integration.",

containing the wrong part "integration" and period at the end.

This makes it the only one showing up in the list like that:

As this looks like a kind of a sentence in Lokalise it also results in even worse translations:

Should be just

Energenie Power Sockets

instead.

(I'd fix it myself but changing the "title" key needs additional test so it's out of scope for the GitHub web editor)

What version of Home Assistant Core has the issue?

2025.1.0b2

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Energenie Power Sockets

Link to integration documentation on our website

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

[home-assistant]

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

Code owner commands

Code owners of energenie_power_sockets can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign energenie_power_sockets Removes the current integration label and assignees on the issue, 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 issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

energenie_power_sockets documentation
energenie_power_sockets source
_{^{(message by IssueLinks)}}

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[joostlek]

@NoRi2909 this is now fixed right

[NoRi2909]

Yes, I forgot to link our PR #141014 to this.