Legacy Zigbee2MQTT Lutron Aurora Dimmer Control

First, huge shout out to drinfernoo. I used their original blueprint and the comments by other community members to debug this blueprint and figure out how to make it work.

This blueprint allows you to control any dimmable light using a Lutron Aurora dimmer knob, integrated via Zigbee2MQTT. Drinfernoo’s blueprint did not work for me, and after a lot of debugging I discovered that my version of zigbee2mqtt was not sending the same mqtt payload as drinfernoo. There seems to be some inconsistencies across the user base, which may be related to the version of HA/mqtt/zigbee2mqtt being run.

I will do my best to reply to posts and if my blueprint does not work for you I encourage you to try drinfernoo’s. If this works for you, let me know your system setup (HA Core|Mosquito Broker|zigbee2mqtt)! I am more interested than anything, but it might let me predict future breaks.

Requirements:

  • Set the aura legacy payload to true
  • Must select the “Brightness” entity not the “Action” entity during setup
  • Dimmable Lights

Blueprint

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.

blueprint:
  name: Legacy 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
        If you have two entity's shown, the 'brightness' entity is the correct one.
      selector:
        entity:
          integration: mqtt
          domain: sensor
          multiple: false
    light:
      name: Light
      description: The light you wish to be affected. Make sure it is a dimmible light
      selector:
        target:
          entity:
            domain: light

mode: queued
max_exceeded: silent

trigger:
  - platform: event
    event_type: state_changed
    event_data:
      entity_id: !input aurora
  - platform: state
    entity_id: !input aurora


action:
  - service: light.turn_on
    target: !input light
    data:
      transition: "{{ 0.7 }}"
      brightness: '{{ trigger.to_state.state }}'

Just wanted to let you know that your blueprint worked perfectly for me. Thank you so much for your efforts! As far as my versions of HA, Z2M, and MQTT, I’m running home assistant 2022.8.7, and the latest stable versions of Z2M and MQTT available as Home Assistant Add-ons. Hopefully this info helps others, and possibly clear up why the payloads differ so dramatically from user to user.

Cheers.

Thanks for looking into this, but now i’m having other issues.
The Aurora brightness entity in z2m is always on 117, the action entity changes state for a brief moment and then dissapears, the logs show:

Zigbee2MQTT:info 2022-08-29 10:21:21: MQTT publish: topic ‘zigbee2mqtt/Living Room Dimmer’, payload ‘{“action”:“brightness_move_to_level”,“action_level”:2,“action_transition_time”:0.02,“brightness”:117,“linkquality”:114,“update”:{“state”:“available”},“update_available”:null}’

And the automation fails with:

“Error rendering data template: UndefinedError: ‘dict object’ has no attribute ‘to_state’”

Can you please help?

Are your Auroras set to legacy = True?
I ask because that payload looks like the non-legacy payload.

I know I saw your post on drinfernos blueprint, its weird that drinfernos blueprint did not work with you since your payload looks like the dict payload vs the state payload.

Glad its working for you! I am still working on some “finishing touches” after using it around the house for the last week. Hopefully will have an update shortly to make operation more smooth.

That did the trick, changing it to legacy started updating the brightness entity. Thanks!