Z-wave remote throws multiple instance of autoamtion?

Configuration Z-Wave
1

so, my automation works fine, to begin with :slight_smile: , but due to some other isseus i am trying to tackle as much warnings and errors that i get, so what i see is that my z-wave 8 button remote, gets a wanring every time i use it.

Logger: homeassistant.components.automation.ab_keuken
Bron: helpers/script.py:1805
integratie: Automatisering (documentation, issues)
First occurred: 16:36:07 (56 gebeurtenissen)
Laatst gelogd: 19:37:33

ab-keuken: Already running.

this is the automation, i cannot see where the problem might be, anyone got an gooed idea?

alias: ab-keuken
description: instellingen van alle knoppen van de ab-keuken
trigger:
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 001
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 002
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 003
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 004
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 005
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 006
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 007
  - platform: device
    device_id: e1702c065c9529ac6d053ceec0839dcb
    domain: zwave_js
    type: event.value_notification.central_scene
    property: scene
    command_class: 91
    value: 0
    endpoint: 0
    subtype: Endpoint 0 Scene 008
condition: []
action:
  - variables:
      scene_id: "{{ trigger.event.data.property_key }}"
  - service: scene.turn_on
    target:
      entity_id: |
        {% set scene_map = {
          '001': 'scene.remotec_1_lampen_keuken_wit_aan',
          '002': 'scene.remotec_1_lampen_keuken_uit',
          '003': 'scene.lampen_keuken_aqua_aan',
          '004': 'scene.lampen_keuken_oranje_aan',
          '005': 'scene.remotec_1_lampen_keuken_paars_aan',
          '006': 'scene.lampen_keuken_regenboog_aan',
          '007': 'scene.lampen_keuken_warm_licht_aan',
          '008': 'scene.lampen_keuken_dimlicht_aan'
        } %} {{ scene_map[scene_id] }}
mode: single
2

That is simply a warning because you use

mode: single

You can add

max_exceeded: silent

to suppress that warning

1 Like
3

That’s because after the automation gets triggered it is getting triggered again before it is done.

So you have a decision and some thinking to do.

If you want the automation to run when that second trigger happens, set the mode as queued. This will queue them up, so that when the first one finishes, the second one will run and so forth.

Or if you want to ignore the second trigger sent it to silent as @francisp suggests.

1 Like
4

@francisp @PeteRage will try both suggestions beginning with queed and see how its works out, thanks