zigbee: components: all

[steppel]

So got my sensor running yesterday then ran into a sudden issue that light component wasn't found and I couldn't compile anymore (I didn't even use a light component). Today I saw there was an update made with "zigbee: components: all ", I added it and now suddenly I have PIR, mmWave and combined Occupancy, my switch to reset the mmWave and the temperature available in Z2M UI. Humidity is not there. Funny thing is I only set Combined Occupancy and the switch to reset mmWave in the zigbee: configuration.

So, does that mean that zigbee: components: all now pulls "all" my entities and creates the part of setting the right attributes, cluster etc?

substitutions:
  uart_tx_pin: GPIO16
  uart_rx_pin: GPIO17

esphome:
  name: presence_sensor_zigbee
  friendly_name: Presence Sensor Zigbee

  on_boot:
    priority: 600
    then:
      - delay: 3s
      - uart.write: "setUartOutput 1 1" 


esp32:
  board: esp32-c6-devkitc-1
  framework:
    type: esp-idf
  

partitions: partitions_zb.csv

external_components:
  - source: github://luar123/zigbee_esphome
    components: [zigbee]
  - source:
      type: git
      url: https://github.com/ssieb/custom_components
    components: [serial]

logger:
  level: VERY_VERBOSE
  logs:
    zigbee: DEBUG
    # binary_sensor: DEBUG
    # text_sensor: DEBUG


uart:
  id: uart_bus
  tx_pin: ${uart_tx_pin}
  rx_pin: ${uart_rx_pin}
  baud_rate: 9600
  parity: NONE
i2c:
  sda: GPIO22
  scl: GPIO23
  scan: true



output:
  - platform: gpio
    pin: GPIO0 
    id: internal_light_output

light:
  - platform: binary
    name: "Internal Light Fix"
    output: internal_light_output
    internal: true

text_sensor:
  - platform: serial
    id: UART_Text
    name: "UART Text"
    uart_id: uart_bus
    internal: true

sensor:
  - platform: bme280_i2c
    temperature:
      name: "Temperature"
      id: bme280_temperature
      oversampling: 16x
      filters: 
        - lambda: "return x - 0.0;"
    pressure:
      name: "Pressure"
      id: bme280_pressure
    humidity:
      name: "Humidity"
      id: bme280_humidity
      filters: 
        - lambda: "return x + 0.0;"
    address: 0x76   # or 0x77 depending on your module
    update_interval: 120s    

# Binary Sensors (PIR and mmWave)
binary_sensor:
  - platform: template
    name: "mmWave Presence"
    id: uart_presence
    device_class: occupancy
    lambda: |-
      // If no UART data yet → default to false
      if (id(UART_Text).state.empty()) {
        return false;
      }

      // Look for DFHPD frame
      if (id(UART_Text).state.rfind("$DFHPD", 0) == 0) {
        // Extract everything after "$DFHPD,"
        auto data = id(UART_Text).state.substr(7);
        // If it starts with "1" → occupied
        if (data.find("1") == 0) {
          return true;
        }
        // If it starts with "0" → clear
        if (data.find("0") == 0) {
          return false;
        }
      }

      // Fallback: no detection
      return false;

  - platform: gpio
    pin: 
      number: 2
      mode: INPUT_PULLDOWN
    name: "PIR Motion"
    id: pir_motion
    device_class: motion
    filters:
      - delayed_off: 10s
    
  
            

  - platform: template
    id: combined_presence
    name: "Combined Occupancy"
    device_class: occupancy
    lambda: |-
      if (id(uart_presence).state || id(pir_motion).state) {
        return true; // Occupied
      }
      return false; // Clear

    # filters:
    #   - delayed_off: 30s 



switch:
  - platform: template
    name: mmWave sensor
    id: mmwave_sensor
    disabled_by_default: True
    entity_category: config
    optimistic: true
    internal: true
    restore_mode: RESTORE_DEFAULT_ON
    turn_on_action:
      - uart.write: "sensorStart"
      - delay: 1s
    turn_off_action:
      - uart.write: "sensorStop"
      - delay: 1s

  - platform: template
    id: factory_reset_trigger
    name: "Factory Reset Trigger"
    turn_on_action:
      - logger.log: "Factory Reset triggered via Zigbee"
      - switch.turn_off: mmwave_sensor
      - delay: 1s
      - uart.write: "resetCfg"
      - delay: 3s
      - switch.turn_on: mmwave_sensor
      # Reset back to OFF so Zigbee doesn’t stay stuck ON
      - switch.template.publish:
          id: factory_reset_trigger
          state: OFF
button:
  - platform: template
    name: Factory Reset mmWave
    icon: mdi:cog-counterclockwise
    id: factory_reset_mmwave
    disabled_by_default: false
    entity_category: diagnostic
    # Action sequence provided by user
    on_press:
      - switch.turn_off: mmwave_sensor
      - delay: 1s
      - uart.write: "resetCfg"
      - delay: 3s
      - switch.turn_on: mmwave_sensor

zigbee:
  id: zb
  components: all
  endpoints:
    - device_type: SIMPLE_SENSOR
      num: 1
      
      clusters:
        - id: OCCUPANCY_SENSING
          attributes:
            - id: zb_occupancy
              attribute_id: 0x0000
              type: 8BITMAP
              device: combined_presence
              report: true
              value: 0
              lambda: "return x ? 1 : 0;"
              on_value:
                then:
                  logger.log: 
                    format: "[INFO OCCUPANCY] Received state %d" 
                    args: [!lambda "x"]
            - attribute_id: 0x0001
              type: 8BIT_ENUM
              report: true
              value: 0x002
        - id: BASIC
          attributes:
            - attribute_id: 4
              type: CHAR_STRING
              value: "ESPHome"
              max_length: 8
            - attribute_id: 5
              type: CHAR_STRING
              value: "Zigbee Presence Sensor"
              max_length: 22

[steppel]

One more observation, even though the Z2M UI shows all my esphome defined entities. The are not showing up in HomeAssistant itself. Only the occupancy, the mmWave sensor reset switch and temp show up. That really confuses me. Any insight would be great, I mean if it can pickup all defined entities and set them up as cluster, thats freaking awesome.

[luar123]

So, does that mean that zigbee: components: all now pulls "all" my entities and creates the part of setting the right attributes, cluster etc?

Yes, that's the idea. See readme for details and limitations. For example Huminity cluster definition is not yet added, so it uses the generic analog input cluster which needs the z2m October release to work.

Regarding homeassistant, I did not try this bit did you try the suggestion from @zipavlin

I need to (at least sometimes) force-remove device from zigbee2mqtt, restart Home Assistant and add device once again.

Or you could use ZHA, which has its own limitations.

[steppel]

So, does that mean that zigbee: components: all now pulls "all" my entities and creates the part of setting the right attributes, cluster etc?

Yes, that's the idea. See readme for details and limitations. For example Huminity cluster definition is not yet added, so it uses the generic analog input cluster which needs the z2m October release to work.

Regarding homeassistant, I did not try this bit did you try the suggestion from @zipavlin

I need to (at least sometimes) force-remove device from zigbee2mqtt, restart Home Assistant and add device once again.

Or you could use ZHA, which has its own limitations.

Well first of all, that freaking awesome! Thanks for all the work.

Yes I tried HA restart too. When I debug and test I remove the device from Z2M and restart Z2M too. So the missing entities in HA is definitely an issue since 99% of users want to use their devices for automation.

[luar123]

Agree, need to look into this.