Zigbee2MQTT Lutron Aurora Dimmer Control

Tags: #<Tag:0x00007fc415dd1ef0> #<Tag:0x00007fc415dd1e28> #<Tag:0x00007fc415dd1d60> #<Tag:0x00007fc415dd1c70> #<Tag:0x00007fc415dd1b80>

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 :grin:

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

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

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

trigger:
  - platform: state
    entity_id: !input aurora

condition:
  - condition: template
    value_template: '{{ trigger.to_state.attributes[''action''] == ''brightness'' }}'

action:
  - target: !input light
    service: light.turn_on
    data:
      brightness: '{{ trigger.to_state.attributes[''brightness''] }}'

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 :wink: 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 :sweat_smile:) we’ll be able to.

1 Like

What a freakin’ LEGEND! :metal:

I was looking at a completely different tutorial for the past 3 days which explains how to use ZHA instead of Zigbee2MQTT but it used Node Red… So I thought, what the hell, can’t be THAT difficult to get it to work… Anyway, 3 days later says it all :smiley:

I imported your blue print and it just WORKED immediately!

Thank you SO much, was starting to lose hope! :sweat_smile:

1 Like

I’m glad it’s working for you! I’ve been using it since I posted this blueprint, and have been mostly satisfied. There are some “kinks”, like if the light gets turned on/off from HA, rather than the knob, it sometimes takes two knob presses to change it again… but that’s pretty minor.

I’d like this blueprint to work with ZHA as well, but seems it would be a bit trickier to set up… and I’ve also completely migrated to Z2M, so setting up ZHA again just to test would be a bit of a chore at this point :sweat_smile:

Oooh I didn’t even stop to realize that the blueprint is obviously using Z2M and NOT HA as it’s “controlling” mechanism… Lol, I am so new to this still I am just learning as I go and damn, there’s ALOT to learn.

But like you say, it’s a minor thing… I’d rather have 2 clicks occasionally than NOT have the integration working at all :smiley:

So you switched from ZHA to Z2M, was there any specific reason?

The blueprint uses HA to affect the lights, based on input from Z2M.

I switched from ZHA to Z2M for two reasons:

  1. I was getting sick of not really being able to diagnose what was happening in my Zigbee network, which I can do easily by listening to the MQTT data.
  2. I upgraded my Zigbee hub to one that supports Z2M, and figured “why not?” :sweat_smile:

To be fair, I did upgrade to a ZZH stick because I found out that it would support Z2M, and that would solve my first issue :grin:

1 Like

Ahhh what a coincidence, I ended up with the same stick :smiley:

Your reasons make a lot of sense lol.

I also like the fact that it’s Z2M that I can diagnose issues, it REALLY helps a lot.

Again, thank you for the help, it’s been working great! :slight_smile: