Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MQTT: The xxx option is deprecated, please remove it from your configuration #67138

Closed
pimw1 opened this issue Feb 23, 2022 · 10 comments · Fixed by #67174
Closed

MQTT: The xxx option is deprecated, please remove it from your configuration #67138

pimw1 opened this issue Feb 23, 2022 · 10 comments · Fixed by #67174
Assignees
Milestone

Comments

@pimw1
Copy link

pimw1 commented Feb 23, 2022

The problem

Since Home Assistant core-2022.3.0b0, i get the following MQTT errors:

Logger: homeassistant.components.mqtt
Source: helpers/config_validation.py:817
Integration: MQTT ([documentation](https://rc.home-assistant.io/integrations/mqtt), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+mqtt%22))
First occurred: 23:08:51 (7 occurrences)
Last logged: 23:08:51

The 'discovery' option is deprecated, please remove it from your configuration
The 'password' option is deprecated, please remove it from your configuration
The 'port' option is deprecated, please remove it from your configuration
The 'username' option is deprecated, please remove it from your configuration
The 'will_message' option is deprecated, please remove it from your configuration
Logger: homeassistant.components.mqtt.climate
Source: helpers/config_validation.py:817
Integration: MQTT ([documentation](https://rc.home-assistant.io/integrations/mqtt), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+mqtt%22))
First occurred: 23:08:57 (2 occurrences)
Last logged: 23:08:57

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

The only stuff that is configured via yaml, is the stuff below in configuration.yaml. The rest is all done via the GUI.
I'm not aware yet of functional impact, everything seems to be working fine so far.

switch:
  - platform: mqtt
    name: "Watermeter Install firmware update?"
    command_topic: "watermeter/smart_gateways/install_update"
    payload_on: "yes"
    payload_off: "no"

sensor:
  - platform: mqtt
    name: "connectix_watermeter_totaal"
    state_topic: "watermeter/reading/current_value"
    unit_of_measurement: "L"
    force_update: true
  - platform: mqtt
    name: "Watermeter MAC Adres"
    state_topic: "watermeter/smart_gateways/mac_address"
  - platform: mqtt
    name: "Watermeter Firmware versie van gateway"
    state_topic: "watermeter/smart_gateways/running_firmware_version"
  - platform: mqtt
    name: "Watermeter Beschikbare firmware versie"
    state_topic: "watermeter/smart_gateways/available_firmware_version"
  - platform: mqtt
    name: "Watermeter Firmware update beschikbaar"
    state_topic: "watermeter/smart_gateways/update_available"
  - platform: mqtt
    name: "Watermeter WiFi Signaalsterkte (rssi)"
    state_topic: "watermeter/smart_gateways/wifi_rssi"
    unit_of_measurement: 'dB'
  - platform: mqtt
    name: "Watermeter startup time"
    state_topic: "watermeter/smart_gateways/startup_time"
  - platform: derivative
    source: sensor.connectix_watermeter_totaal
    name: Waterverbruik
    round: 1
    unit_time: min
    time_window: "00:00:30"  # we look at the change over the last 30 seconds

It was working fine without errors with home assistant 2022.2.x

What version of Home Assistant Core has the issue?

core-2022.3.0b0

What was the last working version of Home Assistant Core?

core-2022.2.6

What type of installation are you running?

Home Assistant Supervised

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?

No response

Additional information

No response

@probot-home-assistant
Copy link

mqtt documentation
mqtt source
(message by IssueLinks)

@probot-home-assistant
Copy link

Hey there @emontnemery, 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!
(message by CodeOwnersMention)

@ludeeus ludeeus added this to the 2022.3.0 milestone Feb 23, 2022
@ludeeus
Copy link
Member

ludeeus commented Feb 23, 2022

conf = CONFIG_SCHEMA({DOMAIN: dict(entry.data)})[DOMAIN]

Hits the deprecated configs with values from the config entry
cv.deprecated(CONF_BIRTH_MESSAGE), # Deprecated in HA Core 2022.3
cv.deprecated(CONF_BROKER), # Deprecated in HA Core 2022.3
cv.deprecated(CONF_DISCOVERY), # Deprecated in HA Core 2022.3
cv.deprecated(CONF_PASSWORD), # Deprecated in HA Core 2022.3
cv.deprecated(CONF_PORT), # Deprecated in HA Core 2022.3
cv.deprecated(CONF_TLS_VERSION), # Deprecated June 2020
cv.deprecated(CONF_USERNAME), # Deprecated in HA Core 2022.3
cv.deprecated(CONF_WILL_MESSAGE), # Deprecated in HA Core 2022.3

@hmmbob
Copy link
Contributor

hmmbob commented Feb 24, 2022

Seeing this too on beta1, no MQTT setup in YAML

@oziee
Copy link

oziee commented Mar 4, 2022

I don't even have any code set with reference to send_if_off or hold_modes and I am seeing this message in the logs to remove the code too.

my config file has nothing in it with these

the docs don't help to what it could be.. doing a file search the only place these settings are found is in HA's own core files, nothing I have created.

where else should I look to see why this message is displaying?

here is the Mqtt for the climate item

name: LoungeroomAC
unique_id: aa6660
modes:
  - 'off'
  - cool
  - dry
  - heat
  - fan_only
  - auto
mode_command_topic: MHI-AC-Ctrl/LoungeroomAC/set/Mode
mode_state_topic: MHI-AC-Ctrl/LoungeroomAC/Mode
temperature_command_topic: MHI-AC-Ctrl/LoungeroomAC/set/Tsetpoint
temperature_state_topic: MHI-AC-Ctrl/LoungeroomAC/Tsetpoint
current_temperature_topic: MHI-AC-Ctrl/LoungeroomAC/Troom
min_temp: 18
max_temp: 30
precision: 1
fan_modes:
  - '1'
  - '2'
  - '3'
  - '4'
fan_mode_command_topic: MHI-AC-Ctrl/LoungeroomAC/set/Fan
fan_mode_state_topic: MHI-AC-Ctrl/LoungeroomAC/Fan
swing_modes:
  - '1'
  - '2'
  - '3'
  - '4'
  - '5'
  - swing
swing_mode_command_topic: MHI-AC-Ctrl/LoungeroomAC/set/Vanes
swing_mode_state_topic: MHI-AC-Ctrl/LoungeroomAC/Vanes
availability_topic: MHI-AC-Ctrl/LoungeroomAC/Availability
payload_available: online
payload_not_available: offline
device:
  identifiers: LoungeroomAC
  name: LoungeroomAC
  sw_version: 'Mitsubishi MHI-AC-Ctrl 0.4 '
  model: Mitsubishi MHI-AC-Ctrl
  manufacturer: MITSUBISHI ELECTRIC
platform: mqtt

debug file
mqtt-7fcf8c2c08df3dc7776668046d0ceb11-PlayroomAC-eb97fee6956d987e1bd9405a33482f26.json.txt

ta

@rotem925
Copy link

rotem925 commented Mar 6, 2022

I have the same issue as @oziee, nothing uses these two options and I still see this in the log.

@danye72
Copy link

danye72 commented Mar 8, 2022

Same problem. I don't have those parameters in configuration

@hmmbob
Copy link
Contributor

hmmbob commented Mar 8, 2022

Did you try upgrading to 2022.3.3? There's a commit that supposedly fixes this (#67661)

Other than that: this is a closed issue, so if the issue remains after upgrading to 2022.3.3, please open a new issue.

@danye72
Copy link

danye72 commented Mar 8, 2022

ok thanks, updated to 2022.3.3, I confirm that the problem has been solved

@rotem925
Copy link

rotem925 commented Mar 8, 2022

Works great on the latest version here as well. Thank you!

@github-actions github-actions bot locked and limited conversation to collaborators Apr 7, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants