Fix translation string in motioneye

[j4n-e4t]

Breaking change

Proposed change

Add missing translation string to motioneye integration.
Links to #127811

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: Help wanted: fix missing translation strings #127811
• Link to documentation 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:

• Documentation added/updated for www.home-assistant.io

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:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

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

Code owner commands

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

[epenet]

I think this might be a false-positive
I think SOURCE_HASSIO should be a discovery source, and there is no need for this... so I opened #128454

[home-assistant]

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.

[j4n-e4t]

I think this might be a false-positive I think SOURCE_HASSIO should be a discovery source, and there is no need for this... so I opened #128454

Should we close this then?

[epenet]

I think this might be a false-positive I think SOURCE_HASSIO should be a discovery source, and there is no need for this... so I opened #128454

Should we close this then?

Let's wait and see if #128454 is approved.
If it is, then this one can be closed - if not then we can get it reviewed again.

[j4n-e4t]

btw didn't mean to reopen... 😔

[epenet]

Closing as #128454 has been accepted