Fix message corruption in picotts component

[lukakama]

Breaking change

Proposed change

This fixes #93456, by sending the message to pico2wave subprocess using the stdin instead of command line arguments, as command line arguments seem to cause issues without a clear root cause.

Usage of stdin should be security equivalent, if not more secure, to usage of command line argument in shell-less subprocesses.

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 Cryptic spoken output for some PicoTTS calls #93456
• This PR is related to issue: Cryptic spoken output for some PicoTTS calls #93456
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend 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][dev-checklist]
• I have followed the [perfect PR recommendations][perfect-pr]
• 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][docs-repository]

If the code communicates with devices, web services, or third-party tools:

• The [manifest file][manifest-docs] 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][prs] in this repository.

[home-assistant]

Hi @lukakama

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

[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.

[lukakama]

I was unable to run the full test suite due a lot of "No module named" errors during tests collection, using the DevContainer environment, regardless installation of all dev and test requirements.
Anyway, there are no test for the picotts platform, so I'm unsure about their usefulness in the context of this PR.

Stale

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

homeassistant/components/picotts/tts.py:63

• [nitpick] Consider capturing stderr (e.g., by setting capture_output=True in subprocess.run) and logging it along with the return code to provide clearer diagnostics when pico2wave fails.

if result.returncode != 0:

[Copilot]

In the error branch, the temporary file is not removed, which could lead to resource leaks. Consider adding cleanup logic (e.g., os.remove(fname)) after logging the error.