#Duplicate Automation from BP - 2nd Won't Fire
1 messages · Page 1 of 1 (latest)
name: Z2M Mod Lutron Aurora Dimmer
description: Control any light with the Lutron Aurora remote, integrated by Zigbee2MQTT.
domain: automation
input:
aurora:
name: Aurora
description: The Lutron Aurora you wish to use to control this light. Use of the 'action' or 'brightness' entity is recommended.
selector:
entity:
integration: mqtt
domain: sensor
light:
name: Light
description: The light you wish to be affected.
selector:
target:
entity:
domain: light
mode: queued
max_exceeded: silent
variables:
attrs: "{{ trigger.to_state.attributes }}"
action: '{{ attrs["action"] }}'
action_level: '{{ attrs["action_level"] }}'
transition_time: '{{ attrs["action_transition_time"] }}'
trigger:
- platform: state
entity_id: !input aurora
to: "brightness_move_to_level"
condition:
- condition: template
value_template: '{{ "brightness" in action }}'
action:
- choose:
- conditions:
- condition: template
value_template: "{{ action_level == 0 }}"
sequence:
- service: light.turn_off
data:
transition: "{{ transition_time }}"
target: !input light
default:
- service: light.turn_on
target: !input light
data:
transition: "{{ transition_time }}"
brightness: "{{ action_level }}"```
The original is here: https://community.home-assistant.io/t/zigbee2mqtt-lutron-aurora-dimmer-control/287379
I've been troubleshooting the original BP with the OP (drinfernoo) in another thread in the #zigbee-archived channel. The modified code works perfect for one device, but if I make a second automation with the BP then I'm unable to execute the automation even if I try to 'run actions' from browser
@uneven rampart @peak roost
I see that you have (drinfernoo) helping you. That's the best help you can get because it appears he has dissected this and has the hardware. I don't see any difference in the code you posted here or the link, so not sure about that.
My advice would be to check the inputs on the 2nd one that's not working. Make sure there is not something like the legacy switch that's different giving you different attribute sets.
As for as specifics I don't see any problems. (from here)