Collect Zigbee cluster definitions

[luar123]

The correct setup of clusters is not always trivial and requires careful reading of the Zigbee cluster library
So lets collect endpoint/cluster/attribute definitions that are know to work. With this we can help each other to get working setups and it would help me to finally implement an automated setup of the definitions.

Device types have two purposes:

1. Let other zigbee devices find an endpoint that implements a certain functionality. Example: A thermostat could search for endpoints that have device type = HA_TEMPERATURE_SENSOR_DEVICE in oder to bind and read the temperature cluster.
2. Automatically setup mandatory clusters, so you don't need to define them manually.

Available device types can be found here, clusters that are included here and the full definitions are in the ZigBee Home Automation Application Profile

In the end it is up to you how you want to implement multiple devices. You can add all to one endpoint or setup many endpoints. If no device type is fitting you can always use TEST or CUSTOM_ATTR. (SIMPLE_SENSOR should only be used for a binary switch.)

[luar123]

Sensors:

(value is always the default value and could be different from what is shown here)

• Temperature

 endpoints:
    - device_type: TEMPERATURE_SENSOR
      num: 1
      clusters:
        - id: TEMP_MEASUREMENT
          attributes:
            - attribute_id: 0x0
              type: S16
              value: 100
              device: temp_id
              scale: 100

• Pressure:
  No fitting device type, often added to temperature endpoint

      clusters:
        - id: PRESSURE_MEASUREMENT
          attributes:
            - attribute_id: 0x0
              type: S16
              report: true
              value: 0x8000
              device: press_id

• Particular matter
  No fitting device type, often added to temperature endpoint

      clusters:
        - id: PM2_5_MEASUREMENT
          attributes:
            - attribute_id: 0x0
              type: single
              report: true
              value: 0
              device: pm25
            - attribute_id: 0x2 # maximum value is needed!
              type: single
              value: 999

• Humidity
  No fitting device type, often added to temperature endpoint

      clusters:
        - id: REL_HUMIDITY_MEASUREMENT
          attributes:
            - attribute_id: 0
              type: U16
              report: true
              value: 200
              device: hum_id
              scale: 100

• illuminance

 endpoints:
    - device_type: LIGHT_SENSOR
      num: 1
      clusters:
        - id: ILLUMINANCE_MEASUREMENT
          attributes:
            - attribute_id: 0
              type: U16
              report: true
              value: 0
              lambda: !lambda "return log10(x)*10000 + 1;"
              device: illum_id

[luar123]

Outputs

• Color dimmable light:
  (dimmable light and on_off light work the same, just use the correct device type and remove unneeded clusters.)

globals:
   - id: color_x
     type: float
     restore_value: no
     initial_value: '0'
   - id: color_y
     type: float
     restore_value: no
     initial_value: '0'

zigbee:
  endpoints:
    - num: 1
      device_type: COLOR_DIMMABLE_LIGHT
      clusters:
        - id: ON_OFF
          attributes:
            - attribute_id: 0
              type: bool
              on_value:
                then:
                  - light.control:
                      id: light_1
                      state: !lambda "return x;"
        - id: LEVEL_CONTROL
          attributes:
            - attribute_id: 0
              type: U8
              value: 255
              on_value:
                then:
                  - light.control:
                      id: light_1
                      brightness: !lambda "return (float)x/255;"
        - id: COLOR_CONTROL
          attributes:
            - attribute_id: 3
              type: U16
              on_value:
                then:
                  - lambda: id(color_x) = (float)x/65536;
                  - light.control:
                      id: light_1
                      red: !lambda "return zigbee::get_r_from_xy(id(color_x), id(color_y));"
                      green: !lambda "return zigbee::get_g_from_xy(id(color_x), id(color_y));"
                      blue: !lambda "return zigbee::get_b_from_xy(id(color_x), id(color_y));"
            - attribute_id: 4
              type: U16
              on_value:
                then:
                  - lambda: id(color_y) = (float)x/65536;
                  - light.control:
                      id: light_1
                      red: !lambda "return zigbee::get_r_from_xy(id(color_x), id(color_y));"
                      green: !lambda "return zigbee::get_g_from_xy(id(color_x), id(color_y));"
                      blue: !lambda "return zigbee::get_b_from_xy(id(color_x), id(color_y));"

[baal86]

• Fan control (0 = off; 1,2,3 = fan speeds)

        - id: FAN_CONTROL
          attributes:
            - attribute_id: 0x0000
              id: fan_mode_attr
              type: 8BIT_ENUM
              report: true
              on_value:
                then:
                  logger.log: 
                    format: "Received state %d" 
                    args: [!lambda "x"]

[luar123]

Color temp see #67

[baal86]

Simple sensor device with analog input cluster and all mandatory attributes except for the description string working. Assuming that support for strings is still broken on the zigbee_esphome side and not investigating this any further.

  endpoints:
    - device_type: SIMPLE_SENSOR
      num: 1
      clusters:
        - id: ANALOG_INPUT
          attributes:
            - attribute_id: 0x0051
              type: BOOL
              value: False
            - attribute_id: 0x0055
              type: SINGLE
              report: true
              value: 100
            - attribute_id: 0x006F
              type: 8BITMAP
              value: 0

[wryandginger]

To elaborate on this, description seems to be working with this endpoint. Also, and more amazingly, you can specify the unit of measurement by using BACNet Enumerations (see here)

Here's a working example of an LD2410 showing the target distance:

    - device_type: SIMPLE_SENSOR
      num: 1
      clusters:
        - id:  ANALOG_INPUT
          attributes:
            - attribute_id: 0x001C
              type: CHAR_STRING
              max_length: 11    #  This needs to match character count of value below
              report: true
              value: Target Dist    #  Custom name for the sensor
            - attribute_id: 0x0051
              type: bool
              value: false
            - attribute_id: 0x0055
              type: single
              report: true
              value: 0
              device: ddistance    #  Sensor ID defined earlier in your ESPHome config
            - attribute_id: 0x0075
              type: 16BIT_ENUM
              value: 118     # BACNet Engineering Unit 118 = centimeters
              report: true
            - attribute_id: 0x006F
              type: 8BITMAP
              value: 0

So, instead of writing quirks/zigbee custom cluster handlers, it might be easier to manually define your sensors this way.

For example, you can specify PM2_5_MEASUREMENT directly, but you should be able to attach this analog input to that same device to get PM10. (Just use 219 as your value for the engineering unit and name it PM10).

[luar123]

Yes that is the best approach for now and string attributes are also supported.
With ZHA it will be auto-discovered if unit or application type is set. Z2m needs an external definition to make it work. See Koenkk/zigbee2mqtt#27926

There is one very small drawback: you can have only one analog input cluster on each endpoint. Normally you would combine pm1, pm2.5, pm10 on the same endpoint. But for adding the device to home assistant that doesn't hurt.

[cameroncros]

Water flow meter:

    - device_type: SIMPLE_SENSOR
      num: 1
      clusters:
        - id: FLOW_MEASUREMENT
          attributes:
            - attribute_id: 0x0 # Actual value, m^3/h
              type: U16
              report: true
              value: 100
              device: water_meter_total
              scale: 100
            - attribute_id: 0x1 # MinMeasuredValue, required
              type: U16
              value: 0xffff # == Not specified
            - attribute_id: 0x2 # MaxMeasuredValue, required
              type: U16
              value: 0xffff # == Not specified

Have gotten it to appear once, but my esp32-c6 boards dont seem to like to reconnect on reboot, so cant be sure it works correctly.

[zipavlin]

Occupancy sensor that I attached to SIMPLE_SENSOR device:

        - id: OCCUPANCY_SENSING
          attributes:
            - id: zb_occupancy # actual state as bit. 0 -> empty; 1 -> occupied 
              attribute_id: 0x000
              type: 8BITMAP
              report: true
              value: 0
              device: sensor_occupancy
              lambda: !lambda "return x ? 1 : 0;" # perhaps not needed
            - attribute_id: 0x0001
              type: 8BIT_ENUM
              report: true
              value: 0x02 #0x00 -> PIR; 0x01 -> sonic; 0x02 -> PIR & sonic

Attribute definitions as well as optional attributes can be found here [page 4-19]

[wryandginger]

Honestly, a custom converter might be the easiest way to go since you are working with a custom template sensor. I think the issue is with your lambda, but it's beyond my knowledge. Without any logs, I can't be much more help. I had similar issues where Zigbee wanted the template data passed as an integer but the lambda is giving a string. Something like that might be happening with your template sensor. You can also try to force update the zigbee attribute. Here's an example of how I am doing it for an air quality sensor:

sensor:
  - platform: template
    id: qualnum1
    lambda: |-
      return static_cast<int>(std::atoi(id(qualnum).state.c_str()));
    update_interval: 120s
    on_value:
      then:
        - zigbee.setAttr:
            id: setqual
            value: !lambda "return x;"
        - zigbee.report: zb

Obviously, you'd want to customize that sensor for your use case and remove the update_Interval.

If you need it to work natively with Z2M, you could try IAS_Zone. It's in 8-3 of the ZCL, page 524. Here's an untested guess. You'll probably have to adjust your template sensor to fit this format:

      clusters:
        - id: IAS_ZONE
          attributes: 
            - attribute_id: 0x0000
              type: 8BIT_ENUM
              value: 0x01
            - attribute_id: 0x0001
              type: 16BIT_ENUM
              value: 0x000d
            - attribute_id: 0x0002
              type: 16BITMAP
              device: combined_presence
              value: 0
              report: true

Sorry I couldn't be more helpful.

[zipavlin]

@steppel sorry, I didn't notice this message. I am doing exactly what you are trying: I combine PIR sensor and mmWave sensor into one template binary sensor. Note that my mmWave sensor is a 'dumb' on/off one, but that should not matter: here is my full config (gist).

What I did notice is that when adding or changing zigbee endpoints/clusters I need to (at least sometimes) force-remove device from zigbee2mqtt, restart Home Assistant and add device once again.

[steppel]

I got it to run with a combined entity. Still seeing 0x406 error in logs even though, but it works. Now I'm wondering if there is a way to control the mmWave sensor settings (sensitive, cool down, distance etc).

[luar123]

You mean like sending settings over zigbee to esphome? Can you even change the settings of this sensor dynamically?
If yes, there are multiple ways to achieve this: 1. Add analog output (float) or binary output (boolean) clusters with on_value trigger. You will need multiple endpoints if you need more than one of each cluster. 2. You could add a custom cluster with exactly the attributes and data types you need. Of course this needs a custom converter in z2m.

[steppel]

You mean like sending settings over zigbee to esphome? Can you even change the settings of this sensor dynamically?

If yes, there are multiple ways to achieve this: 1. Add analog output (float) or binary output (boolean) clusters with on_value trigger. You will need multiple endpoints if you need more than one of each cluster. 2. You could add a custom cluster with exactly the attributes and data types you need. Of course this needs a custom converter in z2m.

Yes exactly. I have entities defined to change mmWave sensor settings via UART commands, works well with just ESPHome. I have to trigger the config change with a separate defined button ("Apply settings").

[gurg1e]

Hacked this together to create an on/off sensor from a photodiode (led_input). In HA i just hide the non-working temperature sensor.

endpoints:
    - num: 1
      device_type: TEMPERATURE_SENSOR
      clusters:
        - id: BINARY_INPUT
          attributes:
            - attribute_id: 0x0055
              id: led_attr
              type: bool
              report: true          
              device: led_input     

[luar123]

Switch from temperature sensor to simple sensor. And you should add the other mandatory attributes 0x51 and 0x6F, like for the analog input cluster a few posts above.

[Jon-Bright]

Including a bit more than just the clusters. This config is tested and working with a Shelly 1 Gen4, but see the note on the first cluster:

zigbee:
  name: "switch-blah"
  debug: true
  id: "zb"
  power_supply: 1
  router: True
  endpoints:
    # Dry contact
    - num: 1
      device_type: ON_OFF_OUTPUT
      clusters:
#        # Ideally, this would be an ON_OFF_SWITCH and include this block, but
#        # If we do that, it doesn't work. (Claims attribute 0x0000 for the ON_OFF
#        # cluster can't be found.)
#        - id: ON_OFF_SWITCH_CONFIG
#          role: SERVER
#          attributes:
#            - attribute_id: 0x0000
#              id: attr_dry_contact_switch_type
#              type: 8bit_enum
#              value: 0 # Toggle switch (as opposed to momentary)
#            - attribute_id: 0x0010
#              id: attr_dry_contact_switch_actions
#              type: 8bit_enum
#              value: 0 # On/off (as opposed to off/on)
        - id: ON_OFF
          role: SERVER
          attributes:
            - attribute_id: 0x0000
              id: attr_dry_contact_on_off
              type: bool
              report: True
              on_value:
                then:
                  - if:
                      condition:
                        lambda: |-
                          return (bool)x;
                      then:
                        - logger.log: "ZB turns dry contact on"
                        - switch.control:
                            id: dry_contact
                            state: True
                      else:
                        - logger.log: "ZB turns dry contact off"
                        - switch.control:
                            id: dry_contact
                            state: False

    # Sensor input
    - num: 2
      device_type: SIMPLE_SENSOR
      clusters:
        - id: BINARY_INPUT
          role: SERVER
          attributes:
            - attribute_id: 0x0055
              id: attr_contact_sensor_state
              type: bool
              report: True

  on_join:
    then:
      - logger.log: "Joined network"

switch:
  # Dry contact output
  - platform: gpio
    id: dry_contact
    name: "Dry contact"
    pin: 5
    on_turn_on:
      then:
        - logger.log: "DC out on!"
        - zigbee.setAttr:
            id: attr_dry_contact_on_off
            value: True
        - zigbee.reportAttr: attr_dry_contact_on_off
    on_turn_off:
      then:
        - logger.log: "DC out off!"
        - zigbee.setAttr:
            id: attr_dry_contact_on_off
            value: False
        - zigbee.reportAttr: attr_dry_contact_on_off

binary_sensor:
  # Contact sensor input
  - platform: gpio
    id: contact_sensor
    trigger_on_initial_state: True
    pin:
      number: 10
      mode:
        input: True
        pullup: False
      inverted: True
    on_state:
      then:
        - zigbee.setAttr:
            id: attr_contact_sensor_state
            value: !lambda "return (bool)x;"
        - zigbee.reportAttr: attr_contact_sensor_state
        - switch.control:
            id: dry_contact
            state: !lambda "return !dry_contact->state;"

[ede1998]

Here's my full yaml. Be aware that i still have issues that the esp often seem to not report anymore after a couple of hours of runtime. Probably related to deep sleep and other stuff I'm doing. Stil trying to figure it out.

esphome:
  name: "esp32c6-bme280"
  friendly_name: esp32c6-bme280
  on_boot:
    then:
      - output.turn_off: rf_switch_enable
      - delay: 100ms
      - output.turn_on: antenna_select
      - wait_until:
          condition:
            lambda: !lambda "return id(my_zigbee).is_connected();"
          timeout: 30s
      - logger.log:
          format: "Zigbee connected after %u ms"
          args: [ "millis()" ]
      - zigbee.report: "my_zigbee"
      - delay: 5s
      - logger.log:
          format: "Zigbee reported after %u ms"
          args: [ "millis()" ]
      - if:
          condition:
            switch.is_off: ota_toggle
          then: deep_sleep.enter

external_components:
  - source: github://luar123/zigbee_esphome
    components: [zigbee]

esp32:
  board: esp32-c6-devkitc-1
  partitions: partitions_zb.csv
  framework:
    type: esp-idf

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "expunged"

ota:
  - platform: esphome
    password: "expunged"

wifi:
  id: my_wifi
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  fast_connect: true
  reboot_timeout: 0s
  enable_on_boot: False

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  # does not work together with zigbee
  #ap:
  #  ssid: "esp32c6-bme280 Fallback Hotspot"
  #  password: "expunged"

#captive_portal:

i2c:
  - id: bus_a
    sda: 22
    scl: 23
    scan: true

sensor:
  - platform: bme280_i2c
    temperature:
      name: "Ambient temperature"
      oversampling: 16x
      id: bme280_temperature
      internal: True
      filters:
          - clamp:
              ignore_out_of_range: True
              min_value: 5.0
              max_value: 40.0
          - sliding_window_moving_average:
              window_size: 10
              send_every: 10
    pressure:
      name: "Atmospheric pressure"
      id: bme280_pressure
      internal: True
      filters:
          - clamp:
              ignore_out_of_range: True
              min_value: 500.0
              max_value: 1500.0
          - sliding_window_moving_average:
              window_size: 10
              send_every: 10
    humidity:
      name: "Air humidity"
      id: bme280_humidity
      internal: True
      filters:
        - clamp:
            ignore_out_of_range: True
            min_value: 0.0
            max_value: 100.0
        - sliding_window_moving_average:
            window_size: 10
            send_every: 10
    address: 0x76
    update_interval: 200ms
    i2c_id: bus_a
  - platform: adc
    pin: GPIO0
    id: battery_voltage
    internal: True
    attenuation: 12db
    update_interval: 200ms
    filters:
       - multiply: 2
       - clamp:
           ignore_out_of_range: True
           min_value: 2.0
           max_value: 5.0
       - sliding_window_moving_average:
           window_size: 10
           send_every: 10
    on_value:
      then:
        - if:
            condition:
              lambda: 'return x <= 2.9;'
            then:
              - logger.log:
                  format: "Voltage level is critical: %.2f V <= 2.9 V (threshold)"
                  level: WARN
                  args: [ 'x' ]
              - deep_sleep.enter:
                  sleep_duration: 10000d
  - platform: template
    name: "Battery Percentage"
    id: battery_percentage
    internal: True
    unit_of_measurement: "%"
    device_class: "battery"
    state_class: "measurement"
    accuracy_decimals: 0
    update_interval: 2s
    # Map voltage to percentage based on a typical Li-ion discharge curve
    lambda: |-
      return id(battery_voltage).state;
    filters:
      - calibrate_linear:
          # (Voltage -> Percentage)
          - 3.0 -> 0
          - 3.5 -> 10
          - 3.7 -> 50
          - 4.0 -> 90
          - 4.2 -> 100
      - clamp:
          min_value: 0
          max_value: 100

switch:
  - platform: template
    id: ota_toggle
    name: "OTA mode"
    icon: mdi:cloud-arrow-down
    internal: True
    lambda: |-
      return !id(my_wifi).is_disabled();
    turn_on_action:
      - logger.log: "OTA mode on"
      - deep_sleep.prevent
      - wifi.enable
    turn_off_action:
      - logger.log: "OTA mode off"
      - wifi.disable
      - deep_sleep.allow

output:
  - platform: gpio
    id: rf_switch_enable
    pin: GPIO3
  - platform: gpio
    id: antenna_select
    pin: GPIO14


deep_sleep:
  #run_duration: 60s
  sleep_duration: 300s

safe_mode:
  boot_is_good_after: 0s

zigbee:
  id: my_zigbee
  power_supply: 0x03
  components:
    - bme280_temperature
    - bme280_pressure
    - bme280_humidity
    - ota_toggle
  endpoints:
    - num: 10
      device_type: SIMPLE_SENSOR
      clusters:
        # https://github.com/simmsb/zigbee_fairy_lights/blob/523f5fa61286923fdb90bfb9b0a3ef64958cbb62/fairylights.yaml#L113
        - id: POWER_CONFIG
          attributes:
            # https://github.com/espressif/esp-zigbee-sdk/blob/a943a91/components/esp-zigbee-lib/include/zcl/esp_zigbee_zcl_power_config.h
            - attribute_id: 0x0020 # ESP_ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_VOLTAGE_ID
              type: u8
              device: battery_voltage
              lambda: !lambda "return x * 10.0;"
            - attribute_id: 0x0021 # ESP_ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_PERCENTAGE_REMAINING_ID
              type: u8
              report: true
              device: battery_percentage
              lambda: !lambda "return x * 200.0 / 100.0;"
            - attribute_id: 0x0031 # ESP_ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_SIZE_ID
              type: u8
              value: 0x02 # ESP_ZB_ZCL_POWER_CONFIG_BATTERY_SIZE_OTHER

time:
 - platform: zigbee
   timezone: Europe/London
   on_time_sync:
     then:
       - logger.log: "Synchronized system clock"

[ede1998]

Oh, and partitions.csv is the standard one from this repo.

[joaomiranda94]

Hello @luar123, I may need some help with my def, I have a shelly 2pm gen4

currently my definition is like this:

esphome:
  name: masterroom-closet-switch
  friendly_name: masterRoom_closet_switch
  on_boot:
    - priority: 800
      then:
        - logger.log: "BOOT STAGE 1 - hardware init"

    - priority: 600
      then:
        - logger.log: "BOOT STAGE 2 - components loading"

    - priority: 300
      then:
        - logger.log: "BOOT STAGE 3 - zigbee about to start"

    - priority: -100
      then:
        - logger.log: "BOOT STAGE 4 - system ready"
        
external_components:
  - source: github://luar123/zigbee_esphome
    components: [zigbee]

esp32:
  variant: esp32c6
  flash_size: 8MB
  partitions: test1.csv
  framework:
    type: esp-idf
    
logger:
  # hardware_uart: UART0
  level: VERY_VERBOSE

safe_mode:
  boot_is_good_after: 0s

output:
  - platform: gpio
    pin: GPIO5
    id: relay_output

switch:
  - platform: template
    id: relay_1
    name: Relay 1
    turn_on_action:
      - output.turn_on: relay_output
    turn_off_action:
      - output.turn_off: relay_output

zigbee:
  id: zb
  router: true
  endpoints:
    - num: 1
      device_type: ON_OFF_OUTPUT
      clusters:
        - id: ON_OFF
          attributes:
            - attribute_id: 0x0000
              id: relay_attr
              type: bool
              report: true
              on_value:
                then:
                  - switch.control:
                      id: relay_1
                      state: !lambda "return (bool)x;"

and the partition I am using is the default from your repo (although I already tried a few variants), however if I try to boot into this, I get no logs and no sign of life is given by the device, but if I flash it without zigbee, it boots correctly, what may I be doing wrong?

[luar123]

How do you connect it to your PC? Try to set hardware_uart: UART0. If that doesn't help see troubleshooting in readme and create a new issue.

[joaomiranda94]

Added this and got some more info, the ESP32C6 was unable to boot to zigbee due to power fluctuations on my CP2102, I added an external PSU. Thanks!

[Maltor]

Hello, @luar123,
I have an ESP32-H2 board that I want to use to control a CWW lamp. My code is below, but in Z2M I can only control the brightness and on/off of the lamp; there is no color temperature control, although there is a color control. Can you help me write the correct code? Thank you.

substitutions:
  device_name: esp32-h2-led
  friendly_name: ESP32-H2 CWW Light

esphome:
  name: $device_name
  friendly_name: $friendly_name

esp32:
  board: esp32-h2-devkitm-1
  variant: ESP32H2
  framework:
    type: esp-idf
  partitions: partitions_zb.csv

logger:
  hardware_uart: UART0

sensor:
  - platform: internal_temperature
    name: "Internal Temperature"
    id: "temp"
    filters:
      - delta: 0.1

external_components:
  - source: github://luar123/zigbee_esphome
    components: zigbee

zigbee:
  id: "zb"
  endpoints:
    - num: 1
      device_type: COLOR_DIMMABLE_LIGHT
      clusters:
        - id: ON_OFF
          attributes:
            - attribute_id: 0
              type: bool
              on_value:
                then:
                  - light.control:
                      id: light_1
                      state: !lambda "return x;"
        - id: LEVEL_CONTROL
          attributes:
            - attribute_id: 0
              type: U8
              value: 255
              on_value:
                then:
                  - light.control:
                      id: light_1
                      brightness: !lambda "return ((float)x)/255;"
        - id: COLOR_CONTROL
          attributes:
            - attribute_id: 7
              type: U16
              value: 500
              on_value:
                then:
                  - light.control:
                      id: light_1
                      color_temperature: !lambda "return (x*(500-153)/100.0) + 153;"        
    - device_type: TEMPERATURE_SENSOR
      num: 2
      clusters:
        - id: TEMP_MEASUREMENT
          attributes:
            - attribute_id: 0x0
              type: S16
              report: true
              value: 100
              device: temp
              scale: 100
  on_join:
    then:
      - logger.log: "Joined network"

output:
  - platform: ledc
    id: ww_color_temp
    pin: GPIO12
  - platform: ledc
    id: cw_color_temp
    pin: GPIO14

light:
  - platform: cwww
    name: $friendly_name
    id: light_1
    cold_white: cw_color_temp
    warm_white: ww_color_temp
    cold_white_color_temperature: 6500 K
    warm_white_color_temperature: 2700 K   
    constant_brightness: true
    restore_mode: RESTORE_DEFAULT_OFF
    effects:
      - random:
      - pulse:
      - strobe:
      - flicker:   

time:
 - platform: zigbee
   timezone: Europe/Bratislava
   on_time_sync:
     then:
       - logger.log: "Synchronized system clock"
```

[luar123]

There are some attributes missing, see #67

Please don't use this discussion for help requests.

[joaomiranda94]

Hello, and sorry for using this topic for help (above).

Anyway, I will share the gist to my currently working config to my Shelly 2PM gen4 (custom ESP32C6 with 8MB flash).

It still is a work in progress and I'll re-enable zigbee functions in the next few changes (I wanted a fresh stable firmware installed so I could gain OTA and rollback functions)

Template.gist

[benjajaja]

MH-Z16 Carbon Dioxide sensor from Seeed

https://wiki.seeedstudio.com/Grove-CO2_Sensor/

zigbee:
  id: "zb"
  router: true
  endpoints:
    - device_type: TEMPERATURE_SENSOR
      num: 1
      clusters:
        # I have it under the endpoint of some other device's clusters, but this shouldn't matter
        - id: CARBON_DIOXIDE_MEASUREMENT
          attributes:
            - attribute_id: 0x0000
              id: zb_co2
              type: SINGLE
              report: true
              device: co2_sensor
              scale: 0.000001
            - attribute_id: 0x0001
              type: SINGLE
              value: 0.0
            - attribute_id: 0x0002
              type: SINGLE
              value: 0.01

uart:
  rx_pin: GPIO17   # connect to MH-Z16 TX
  tx_pin: GPIO16   # connect to MH-Z16 RX
  baud_rate: 9600

sensor:
  - platform: mhz19
    id: mhz16
    co2:
      name: CO2
      id: co2_sensor
    update_interval: 60s
    automatic_baseline_calibration: false

This config with the scaling, which I inferred from other discussions in this repo, correctly creates a CO² sensor in ZHA, Home Assistant.

Thanks for this project ❤️ !