STT config error log entries

[PulsarFX]

The problem

I'm affected by this in 2023.7:

Logger: homeassistant.helpers.config_validation
Source: helpers/config_validation.py:1065

The stt integration does not support any configuration parameters, got [{'platform': 'google_cloud_stt', 'key_file': 'ha-google-tts.json', 'model': 'command_and_search'}]. Please remove the configuration parameters from your configuration.

Docs for https://www.home-assistant.io/integrations/google_cloud/ has config settings for tts
but also stt, as it states: "Basic instruction for all APIs" (that is, stt, tts, geocoding)

https://www.home-assistant.io/integrations/stt/ doesn't show any config options, though.

Found how to do the setup here: https://community.home-assistant.io/t/use-google-cloud-speech-to-text-in-home-assistant/570113
which links to https://github.com/chatziko/ha-google-cloud-stt

What version of Home Assistant Core has the issue?

2023.7.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

stt

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

stt:
  - platform: google_cloud_stt
    key_file: ha-google-tts.json
    model: command_and_search

Anything in the logs that might be useful for us?

Logger: homeassistant.helpers.config_validation
Source: helpers/config_validation.py:1065
First occurred: 18:28:24 (1 occurrences)
Last logged: 18:28:24

The stt integration does not support any configuration parameters, got [{'platform': 'google_cloud_stt', 'key_file': 'ha-google-tts.json', 'model': 'command_and_search'}]. Please remove the configuration parameters from your configuration.

Additional information

No response

[home-assistant]

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

Code owner commands

Code owners of google_cloud 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 google_cloud Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[home-assistant]

Hey there @home-assistant/core, @pvizeli, mind taking a look at this issue as it has been labeled with an integration (stt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of stt 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 stt Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

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

[chatziko]

This is the culprit: #93954

stt allows to setup platforms, so it should use PLATFORM_SCHEMA and accept parameters like this:

stt:
  - platform: google_cloud_stt
    key_file: googlecloud.json
    model: command_and_search

Likely this issue was not reported since none of the native HA integrations tries to setup an stt platform. However this breaks custom integrations like google_cloud_stt.

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

[felipecrs]

This issue is still valid.

[reflectivecode]

I can confirm that this is still an issue with version 2023.10.5.

[rknotter]

And confirming that in version 2023.11.3 this is still an issue.

[MartinHjelmare]

Integrations, including custom integrations, should follow our architecture decisions recorded in ADR7 and ADR10.

ADR7 says that integrations that are setup via YAML should put their config under the integration domain key and not under a platform domain key.

https://github.com/home-assistant/architecture/blob/master/adr/0007-integration-config-yaml-structure.md

ADR10 says that integrations that integrate devices and/or services should be setup via the UI.

https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md

In summary, it's not supported to set up stt platforms via platform YAML configuration and we don't intend to change this.