MQTT breaking changes RC 2022.6

[parautenbach (Pieter Rautenbach)]

@michaelblight

HA is moving away from YAML to UI configuration to, I assume, become more accessible to new users.

It’s besides the point. I know this, and I’m fine with that and yes that’s the reason it’s being done. I need to add the config flow to my stuff – but that’s another topic.

@michaelblight

It would be madness to set up lights under “Lights”

I don’t understand why this seems illogical – or mad.

[oldfart101]

Having a nightmare with this
My configuration.yaml file:

mqtt: !include_dir_merge_named mqtt/
sensor: !include_dir_merge_list sensors

because I have sensors that are not MQTT
I have 2 files in mqtt:
acurite-humidity.yaml

sensor:
- name: "Indoor Humidity"
#'acurite/humidity'
  state_topic: "home/rtl_433"
  unit_of_measurement: '%'
  value_template: >
    {% if value_json is defined and value_json.id == 11794 %}
      {{ value_json.humidity }}
    {% else %}
      {{ states('sensor.indoor_humidity') }}
    {% endif %}

and acurite-temperature.yaml

sensor:
- name: "Indoor Temp"
#'acurite/temp'
  state_topic: "home/rtl_433"
  unit_of_measurement: '°C'
  value_template: >
    {% if value_json is defined and value_json.id == 11794 %}
      {{ value_json.temperature_C }}
    {% else %}
      {{ states('sensor.indoor_temp') }}
    {% endif %}

HA only shows the first sensor.
You can’t put more than 1 sensor in the same file - get an error.
(this was all working before the mqtt change!)

[dfrap (Darrell)]

Unfortunately, YAML - Home Assistant documents the old syntax to explain nesting a collection of mappings in a mapping.

sensor:
  - platform: mqtt
    state_topic: "sensor/topic"
  - platform: mqtt
    state_topic: "sensor2/topic"

It will be very confusing for some time to those of us struggling to understand YAML syntax.

[petro]

Because you’re using merge dir named. If you want to use it that way, you have to make separate folders for each domain…

mqtt:
  sensor: !include_dir_merge_list mqtt/sensor/

And then remove sensor: from your files.

Or if you want to use merge_named, then you can only have 1 file per domain.

[oldfart101]

can’t use the keyword ‘sensor’ more than once in configuration.yaml
and I have other non mqtt sensors

[oldfart101]

got it!
configuration.yaml:

mqtt:
  sensor: !include_dir_merge_list mqtt/
sensor: !include_dir_merge_list sensors

mqtt/humidity.yaml

- name: "Indoor Humidity"
#'acurite/humidity'
  state_topic: "home/rtl_433"
  unit_of_measurement: '%'
  ....

[stevemann (Stephen Mann (YAML-challenged))]

I have a number of MQTT devices and would like to get ahead of 2022.9 and not repeat my debacle of waiting too long to change my Z-Wave stuff.
So, what’s wrong here?

OLD:

switch:
  - platform: mqtt
    name: "steve_Heat"
    command_topic: "cmnd/steve_heat/power"
    state_topic: "stat/steve_heat/POWER"
    qos: 1
    payload_on: "ON"
    payload_off: "OFF"
    retain: false

NEW:

mqtt:
  switch:
    -name: "steve_Heat"
     command_topic: "cmnd/steve_heat/power"
     state_topic: "stat/steve_heat/POWER"
     qos: 1
     payload_on: "ON"
     payload_off: "OFF"
     retain: false

Is there a dictionary or Rosetta stone that helps interpret the error messages?
What is a <block end> and a '<block mapping start>' ?
[Edit to fix forum software munging my question].

[atomicpapa (Glenn Morrison)]

@stevemann

mqtt:
  switch:
    -name: "steve_Heat"
     command_topic: "cmnd/steve_heat/power"
     state_topic: "stat/steve_heat/POWER"
     qos: 1
     payload_on: "ON"
     payload_off: "OFF"
     retain: false

mqtt:
  - switch:
      - name: "steve_Heat"
        command_topic: "cmnd/steve_heat/power"
        state_topic: "stat/steve_heat/POWER"
        qos: 1
        payload_on: "ON"
        payload_off: "OFF"
        retain: false

[stevemann (Stephen Mann (YAML-challenged))]

@atomicpapa

mqtt:

I didn’t notice that my earlier question was munged by the forum software, so I’ll ask again in code tags.

Also your suggested fix produced this error:

The system cannot restart because the configuration is not valid: Error loading /config/configuration.yaml: while parsing a block mapping in "/config/configuration.yaml", line 262, column 7 expected <block end>, but found '<block mapping start>' in "/config/configuration.yaml", line 263, column 8

Is there a codex or universal translator to help understand, just what is a <block end> and a '<block mapping start>' ?

[atomicpapa (Glenn Morrison)]

Try this way. I have a similar switch setup in a package.

mqtt:
  switch:
    - name: "steve_Heat"
      command_topic: "cmnd/steve_heat/power"
      state_topic: "stat/steve_heat/POWER"
      qos: 1
      payload_on: "ON"
      payload_off: "OFF"
      retain: false

[petro]

@stevemann

mqtt:
  switch:
    -name: "steve_Heat"

mqtt:
  switch:
  - name: "steve_Heat"

[stevemann (Stephen Mann (YAML-challenged))]

Thanks guys. I knew it had to be in the indenting. FWIW, the formatting in the “breaking-changes” is also indented wrong.

Works now.

But, for future errors, and I will absolutely have more.

@stevemann

Is there a codex or universal translator to help understand, just what is a <block end> and a '<block mapping start>' ?

Should I be looking for a YAML 101 guide on the web?

[petro]

The indentation and formatting in breaking-changes is correct. The indentation in your original question was fine, your issue was the dash not having a space between your field.

Yaml only cares about relative indentation. These yaml examples are functionally the same:

mqtt:
 sensor:
 - name: ...

mqtt:
  sensor:
                            - name: ...

mqtt:
                         sensor:
                         - name: ...

This is what you did wrong:

[stevemann (Stephen Mann (YAML-challenged))]

@petro

Yaml only cares about relative indentation.

Thanks. That explains a lot.

[Buster]

Thanks for this @petro Got all 98 of mine switched over with this process.

[angusc (Chris)]

Hi there,

Please could someone assist me with my mqtt re-configuration. I have my mqtt files saved in one folder like this:

/config/packages/systems/ustou/ustou_lights.yaml

My old configuration was like this:

# Devices
light:
  - platform: mqtt
    name: "Entrance Hall Light"   
    command_topic: "cmnd/halllight/POWER"
    state_topic: "stat/halllight/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
    unique_id: entrance hall light
    
  - platform: mqtt
    name: "Dining Floor Light"
    command_topic: "cmnd/floorlamp/POWER"
    state_topic: "stat/floorlamp/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
    unique_id: dining floor light
    
  - platform: mqtt
    name: "Telephone Table Lamp"
    command_topic: "cmnd/table3/POWER"
    state_topic: "stat/table3/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
    unique_id: telephone table lamp

I have 3 .yaml files; one for sensors, one for lights and one for switches

Now after changing to RC 2022.6 I changed the above to this:

# Devices
mqtt:
  light:
    - name: "Entrance Hall Light"    
      command_topic: "cmnd/halllight/POWER"
      state_topic: "stat/halllight/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
      unique_id: entrance hall light
    
    - name: "Dining Floor Light"
      command_topic: "cmnd/floorlamp/POWER"
      state_topic: "stat/floorlamp/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
      unique_id: dining floor light
    
    - name: "Telephone Table Lamp"
      command_topic: "cmnd/table3/POWER"
      state_topic: "stat/table3/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
      unique_id: telephone table lamp
    

Now after restart all lights are “unavailable” but switches and climate sensors are working…?

I changed my switches from this:

# Power Outlets
switch:
  - platform: mqtt
    name: "Mums Blanket"
    command_topic: "cmnd/mumblanket/POWER"
    state_topic: "stat/mumblanket/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
    
  - platform: mqtt
    name: "Dads Blanket"
    command_topic: "cmnd/dadblanket/POWER"
    state_topic: "stat/dadblanket/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    retain: true
       
  - platform: mqtt
    name: "Lili Blanket"
    command_topic: "cmnd/liliblanket/POWER"
    state_topic: "stat/liliblanket/POWER"
    payload_on: "ON"
    payload_off: "OFF"
    retain: true

To this and they are still present and working in my dashboard:

# Power Outlets
mqtt:
  switch:
   -  name: "Mums Blanket"
      command_topic: "cmnd/mumblanket/POWER"
      state_topic: "stat/mumblanket/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
    
   -  name: "Dads Blanket"
      command_topic: "cmnd/dadblanket/POWER"
      state_topic: "stat/dadblanket/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
       
   -  name: "Lili Blanket"
      command_topic: "cmnd/liliblanket/POWER"
      state_topic: "stat/liliblanket/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
        

I made the same changes made to my sensors and switches, as I did to my lights. So I’m confused as to why the lights no longer work.

Any advice would be greatfully received.

[nukeman]

@angusc

mqtt:
  light:
    - name: "Entrance Hall Light"    
      command_topic: "cmnd/halllight/POWER"
      state_topic: "stat/halllight/POWER"
      payload_on: "ON"
      payload_off: "OFF"
      retain: true
      unique_id: entrance hall light

I’m also having issues with the new changes. I’m getting the error “missing property platform” in sensor.yaml when I use a separate mqtt sensor file. How did you solve this?

Configuration.yaml

mqtt:
  broker: #hidden
  port: 1883
  username: #hidden
  password: #hidden
  sensor: !include sensor.yaml

sensor.yaml

mqtt:
  sensor:
  - name: "mqtt_temp"
    state_topic: "l/t_1/sensor/t_1/state"
    unit_of_measurement: '°C'
    payload_available: "online"
    payload_not_available: "offline"
    availability_topic : 'l/tyl_1'
    state_class: measurement

[petro]

It looks like it should work for light as long as you are using packages. If you aren’t using packages and you have a single configuration, then both light and switch need to be in 1 mqtt section.

[petro]

It does not go in sensor.yaml or the sensor section. It goes in a new MQTT section. There are multiple ways to specify this, and it’s covered earlier in the thread.

MQTT breaking changes RC 2022.6

You don’t say but this Makes me assume you have something this in configuration.yaml right now right? sensor: !include_dir_merge_list sensors So just make subfolders I guess. Something like this could work: sensors mqtt template … legacy_format And then add this to configuration.yaml: mqtt: sensor: !include_dir_merge_list sensors/mqtt template: - sensor: !include_dir_merge_list sensors/template sensor: !include_dir_merge_list sensors/legacy_format I assume you also needed to …

MQTT breaking changes RC 2022.6

well, if you have multiple… before: sensor: - platform: mqtt name: xyz - platform: mqtt name: abc binary_sensor: - platform: mqtt name: ijk - platform: mqtt name: lmn after: mqtt: sensor: - name: xyz - name: abc binary_sensor: - name: ijk - name: lmn Basically, instead of being spread out across multiple domains (fields), they are now all inside the mqtt umbrella.

MQTT breaking changes RC 2022.6

The lazy way I did it was: mqtt: !include_dir_merge_named mqtt/ and then I made an mqtt folder and placed my files into that. The names of the files don’t matter, but I named them what they were adding… config/mqtt/binary_sensor.yaml binary_sensor: - name: xyz - name: abc EDIT: If you do it the way @CentralCommand is doing it, you can make it granular. I.e. you’d make separate folders in the mqtt folder for each type, then you can name the files humidiy.yaml and it wouldn’t care but you’…

MQTT breaking changes RC 2022.6

Except it was always mqtt integration and always said MQTT. I’m not really understanding, the config went from this: sensor: - platform: mqtt name: My MQTT sensor ... cover: - platform: mqtt name: My MQTT cover ... To this: mqtt: sensor: - name: My MQTT sensor ... cover: - name: My MQTT cover ... If anything it says MQTT less times now since you don’t have to put platform: mqtt in everything. But more importantly here is this was never the cove…

[nukeman]

Thanks. I’ve looked at those and structured my code accordingly. For some reason, the error actually went away. However, the sensor doesn’t show up as an entity when I search for it.