Zigbee2MQTT configuration.yaml

Configuration Zigbee
1

According the breaking changes I should add this to configuration.yaml


advanced:
  homeassistant_legacy_entity_attributes: false
  homeassistant_legacy_triggers: false
  legacy_api: false
  legacy_availability_payload: false
device_options:
  legacy: false

However this is my configuratuion.yml


homeassistant:
  enabled: true
  legacy_action_sensor: false
  experimental_event_entities: false
mqtt:
  server: mqtt://core-mosquitto:1883
  user: ********
  password: *******
  version: 5
serial:
  port: >-
    /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20220810134749-if00
  adapter: ezsp
frontend:
  enabled: true
  port: 8099
advanced:
  log_syslog:
    app_name: Zigbee2MQTT
    eol: /n
    host: localhost
    localhost: localhost
    path: /dev/log
    pid: process.pid
    port: 123
    protocol: tcp4
    type: '5424'
  transmit_power: 10
  channel: 15
  log_level: info
device_options: {}
devices:

I’ve snipped the devices and hidden user/password from above

I’ve updated to v2 (latest), and my zigbee is working fine, apart from illuminance sensor renamed, I’ve made no other changes.

Should I leave the config alone or make the changes regardless?

2

The reason it is working is that likely you do not have any legacy components. You can keep it as you have it, but adding would not do any harm either.

1 Like
3

Leave it as-is.

FWIW, I added all of those lines you listed prior to upgrading to version 2.0 (as per the instructions for upgrading to 2.0). After upgrading, the upgrade process automatically removed them.

1 Like
4

That’s interesting, so far have left it as is, everything works.

I’ll take your advice and keep it that way.

1 Like