This blueprint allows you to control any dimmable light using a Lutron Aurora dimmer knob, integrated via Zigbee2MQTT. My main reasoning behind creating this blueprint in the first place is because it appears that some bulbs (these Sengled ones, in my case) do not appear to update their state in Z2M when they are controlled directly via a bound remote, so while controlling them with the dimmer knob works, the state inside HA doesn’t always get updated, and causes a disparity between the physical state of the bulb and the reported state inside HA. If you have seen similar issues, this blueprint is for you! As an added bonus, this should be able to control any dimmable light entity (not just Zigbee ones), including light groups 
Requirements:
- At least one Lutron Aurora, integrated via Zigbee2MQTT
- Any other (dimmable) light
What doesn’t work:
- Lutron Aurora knobs integrated via Zigbee Home Automation
FAQ:
Which entity should I use?
This blueprint should work with any of the sensor entities created for the Aurora (‘action’, ‘brightness’, ‘linkquality’, or ‘update state’), but for clarity in your automations, I would recommend using either the ‘action’ or ‘brightness’ entities.
Should I bind the knob and bulb?
When the dimmer knob is bound to the bulb, this blueprint does not function correctly, so make sure to unbind the knob and bulb if you want to use this blueprint. Instructions for unbinding can be found here.
Blueprint
blueprint:
name: Zigbee2MQTT Lutron Aurora Dimmer Control
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 }}"
I would like to find a way to narrow down the selector to only show the entities associated with the Aurora’s themselves, so if anyone can point me in the right direction, that would be appreciated, and I can update the blueprint 
It seems to me that the selector parameters won’t allow me to get quite that detailed at this time, but hopefully in the future (or possibly now 
) we’ll be able to.
I don’t believe there have been any device firmware updates either… Mine say firmware build date is