Zigbee2mqtt - EnOcean PTM 215Z On-Off-Dimming

[Kroning]

A input boolean must be created, named dimming occured (with a underscore between dimming and occured, cant insert that here ?)

blueprint:
  name: zigbee2mqtt - EnOcean PTM 215Z On-Off-Dimming
  description: Top buttons on/off and dimming of light. Bottom buttons control on/off and dimming of light
  domain: automation
  input:
    switch:
      name: Switch
      description: on/off/dimming sensor
      selector:
        entity:
          domain: sensor

    light_top:
      name: Light_top
      description: The light to control with top buttons
      selector:
        target:
          entity:
            domain: light

    light_buttom:
      name: Light_buttom
      description: The light to control with bottom buttons
      selector:
        target:
          entity:
            domain: light
mode: restart
max_exceeded: silent
trigger:
  - platform: state
    entity_id: !input "switch"
    attribute: action
condition:
  - condition: template
    value_template: '{{ trigger.to_state.attributes.action in ("press_1","release_1","press_2","release_2","press_3","release_3","press_4","release_4") }}'
action:
  - variables:
      command: "{{ trigger.to_state.state }}"

  - choose:
  
      - conditions:
          - "{{ command == 'press_2' }}"
        sequence:
          - service: light.turn_on
            target: !input "light_buttom"
            data: {}
          - delay: "0.5"
          - repeat:
              count: "7"
              sequence:
                - service: light.turn_on
                  data:
                    brightness_step_pct: 15
                    transition: 0
                  target: !input "light_buttom"
                - delay: "0.5"

      - conditions:
          - "{{ command == 'release_4' }}"
        sequence:
          - choose:
              - conditions:
                  - condition: state
                    entity_id: input_boolean.dimming_occured
                    state: "off"
                sequence:
                  - service: light.turn_off
                    data: {}
                    target: !input "light_buttom"

              - conditions:
                  - condition: state
                    entity_id: input_boolean.dimming_occured
                    state: "on"
                sequence:
                  - service: input_boolean.turn_off
                    target:
                      entity_id: input_boolean.dimming_occured
                    data: {}

      - conditions:
          - "{{ command == 'press_4' }}"
        sequence:
          - delay: "0.5"

          - service: input_boolean.turn_on
            target:
              entity_id: input_boolean.dimming_occured
            data: {}

          - repeat:
              count: "7"
              sequence:
                - service: light.turn_on
                  data:
                    brightness_step_pct: -15
                    transition: 0
                  target: !input "light_buttom"
                - delay: "0.5"


      - conditions:
          - "{{ command == 'press_1' }}"
        sequence:
          - service: light.turn_on
            target: !input "light_top"
            data: {}
          - delay: "0.5"
          - repeat:
              count: "7"
              sequence:
                - service: light.turn_on
                  data:
                    brightness_step_pct: 15
                    transition: 0
                  target: !input "light_top"
                - delay: "0.5"

      - conditions:
          - "{{ command == 'release_3' }}"
        sequence:
          - choose:
              - conditions:
                  - condition: state
                    entity_id: input_boolean.dimming_occured
                    state: "off"
                sequence:
                  - service: light.turn_off
                    data: {}
                    target: !input "light_top"

              - conditions:
                  - condition: state
                    entity_id: input_boolean.dimming_occured
                    state: "on"
                sequence:
                  - service: input_boolean.turn_off
                    target:
                      entity_id: input_boolean.dimming_occured
                    data: {}

      - conditions:
          - "{{ command == 'press_3' }}"
        sequence:
          - delay: "0.5"

          - service: input_boolean.turn_on
            target:
              entity_id: input_boolean.dimming_occured
            data: {}

          - repeat:
              count: "7"
              sequence:
                - service: light.turn_on
                  data:
                    brightness_step_pct: -15
                    transition: 0
                  target: !input "light_top"
                - delay: "0.5"

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

I am a bit confused my friend.
Is this a finished blueprint you are sharing or a not working blueprint that you have a question with?

[wmaker (Tommy Long)]

Just passing along if anyone is interested…

Zigbee2MQTT enOcean PTM 215Z (Friends of Hue) switch

Hi Guys, I’ve created a Zigbee2MQTT blueprint for Friends Of Hue switches based on the enOcean PTM 215Z switches (Like Senic Gira, NIKO, Bush Jeager, EcoDim and others alike) This blueprint is based on the great work of Nick but based on MQTT instead of the legacy sensor created by z2m. Also using mode restart instead of single for easier dimming. Make sure you enable Elapsed in the z2m advanced settings. This is used to prevent a release after a short press to restart the automation premature…

[alexsaas]

@wmaker
Hi, may I ask if you’re still using this blueprint from Vandalon? I unfortunately get warnings in the log after every full system reboot. Maybe you had this too and have a solution? Here I explain the message:

Warning after reboot. TypeError: argument of type 'NoneType' is not iterable

After every reboot HA shows this warning: Logger: homeassistant.components.automation Source: components/automation/__init__.py:1020 Integration: Automatisierung (documentation, issues) First occurred: 07:40:34 (2 occurrences) Last logged: 07:40:34 Error evaluating condition in 'NameOfMyAutomation1': In 'condition': In 'template' condition: TypeError: argument of type 'NoneType' is not iterable Error evaluating condition in 'NameOfMyAutomation2': In 'condition': In 'template' condition: TypeEr…

[wmaker (Tommy Long)]

Hi,
No I actually never used it. I was transitioning from Philips Hue to Z2M and was doing research on the PTM215Z I have for use with Z2M. I came across his Blueprint while doing this research, and so when I came across this thread I was just passing the information along.

[alexsaas]

Okay, too bad. But thanks for the feedback. Are you using a different blueprint that works well?

[wmaker (Tommy Long)]

In my case, I only want to turn lights ON and OFF (no dimming needed) so the automations are simple and I made them myself.

[alexsaas]

Ok. Then I have to keep looking. But it was worth a try. Thank you again.

[sumsaricum]

Hi alexsaas, please let me/us know what you ended up with after researching

[alexsaas]

Hi @sumsaricum

In the end I stuck with the blueprint and added another condition:

Warning after reboot. TypeError: argument of type 'NoneType' is not iterable

Hi. I (hopefully for the last time) return to the topic. I found a better (maybe the right) solution for me. The previous solution with the additional automation was not entirely satisfactory for me. But now I have found a way to edit the blueprint so that the error messages in question no longer appear. I have supplemented the relevant section of the blueprint with another condition (in front of the existing one). This is what it looks like now: condition: - condition: template value_t…

After a complete reboot, the error messages no longer appear. But still after a quick restart. Since I know this, I’ll simply delete them afterwards. These are not real errors, just messages. I’ve come to terms with it because the blueprint works well.

Maybe not the best solution, but I can live with it.