The 'schema' option is deprecated, please remove it from your configuration

[rwjack]

The problem

I get this warning for the mqtt integration, I have no idea what it's talking about.

What version of Home Assistant Core has the issue?

core-2024.6.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

mqtt

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.mqtt
Source: helpers/config_validation.py:915
integration: MQTT (documentation, issues)
First occurred: 1:00:49 AM (1 occurrences)
Last logged: 1:00:49 AM
The 'schema' option is deprecated, please remove it from your configuration

### Additional information

Happens once on every startup, everything seems to be working, it's just the warning that's annoying.

[home-assistant[bot]]

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

Code owner commands

Code owners of `mqtt` 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 mqtt` 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)}}

---

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

[jbouwh]

Perhaps the logging should be improved here, I'll have a look what causes it.

[jbouwh]

I think the message is about a discovery message for a state vacuum. We used to have 2 schema's for vacuum, and the schema option is deprecated and not used anymore. For discovery messages, that is not a big issue as we allow extra options. But the logging should show some more information about the config causing the warning here.

[rwjack]

I've been getting this for a few months at the very least, but I'm not seeing any Schema parameter in the settings (Re-configure mqtt).

Although I get what you're saying, clearer logging should definitely tell us what's up.

[jbouwh]

The schema option might be in a discovery message. If have openened a PR to improve the logging. You should be able to see what MQTT vacuums are added during startup. Options for MQTT entities are in YAML or in discovery message that are received. Meant to set up MQTT items/entities.

[rwjack]

I'll update this issue once the PR is approved and released.

[jbouwh]

Noet that the issue will be closed automatically when it is merged. The improvement will be targeted for ha core 2024.7.

[rwjack]

Found the culprit!

https://github.com/Hypfer/Valetudo/issues/1992