Z2M: Lutron Aurora Dimmer

PinkFloydEffect · February 12, 2025, 11:47pm

I have been trying to get Lutron Aurora dimmer switches integrated via Zigbee2MQTT for several months now, nobody in the Facebook group has been able to help.

I’m really struggling to understand how blueprints work. Tried creating an automation from 2 different Lutron Aurora dimmer blueprints but they do not work and when you view them in yaml they do not appear to contain nearly enough info to link an event to a device action.

Experimental events and legacy actions are enabled in Z2M. If I go into the Z2M-UI I do see the info needed in the state tab, just not sure how to write an automation from this…if I could just get a 0 & 255 - Off & On I would be happy without using the dimmer function:

{
    "battery": 100,
    "linkquality": 105,
    "update": {
        "installed_version": 3080,
        "latest_version": 3080,
        "state": "idle"
    },
    "action": "",
    "action_group": 28285,
    "action_level": 255,
    "action_transition_time": 0.07,
    "brightness": null
}

476237624_3948500838697539_204959719211283373_n

wmaker · February 13, 2025, 10:41pm

Here is an automation that reportedly works

github.com/Koenkk/zigbee2mqtt

Lutron Aurora dimmer knob (Z3-1BRL) not delivering Brightness value on 2.0.0

opened 02:39AM - 05 Jan 25 UTC

apiontek

problem

### What happened? I have a couple Lutron Aurora dimmer knobs (Z3-1BRL). I ha…d them working with Home Assistant, in a "Legacy" mode. After updating to Z2M 2.0.0 I'm seeing two problems: 1. Device in Z2M shows "Brightness" under "Exposes" but the value never updates. However, I can see State messages updating under "State." I think the issue is that the payload itself always shows `"brightness": null` -- the value one expects to see as "brightness" is delivered in payload as `"action_level": 44` for example, with `"action": "brightness_move_to_level"` ```json { "linkquality": 152, "update": { "installed_version": 3080, "latest_version": 3080, "state": "idle" }, "action": "brightness_move_to_level", "action_group": 30374, "action_level": 44, "action_transition_time": 0.02, "brightness": null } ``` 2. There used to be a Device setting to enable a "Legacy" mode. This is no longer available, and reference was removed from [the device page](https://www.zigbee2mqtt.io/devices/Z3-1BRL.html). I assume this is related to the general removal of legacy features in 2.0, and that's fine, but I'm noting here since it requires changing automations. It's also worth noting because when Legacy mode is enabled, the State payload has the `"brightness"` value, for example: ```json { "brightness": 255, "linkquality": 216, "update": { "installed_version": 3080, "latest_version": 3080, "state": "idle" } } ``` In fact, this seems to have been [reported previously](https://github.com/Koenkk/zigbee2mqtt/issues/12291) but the advice then was to _disable_ Legacy mode (I think the opposite would have been true), but that's no longer an option. It would be good to just get the Brightness state updating from the `"action_level"` payload value. There's nothing more complicated with this device. ### What did you expect to happen? Brightness state should update with `action_level` value from device. ### How to reproduce it (minimal and precise) Reset and pair a Lutron Aurora dimmer knob. Default behavior is as described above. ### Zigbee2MQTT version 2.0.0 ### Adapter firmware version 7.4.4 [GA] via EmberZNet ### Adapter SONOFF Zigbee 3.0 USB Dongle Plus-E ### Setup Docker container ### Debug log I can upload this if it seems helpful.

PinkFloydEffect · February 23, 2025, 6:10pm

This finally got me up and running!! Thank you so much!!

Only thing I would like to figure out now is how to set a condition value “range” such as {{ action_level == 3-254 }} or similar without having an entry for every single value between 2 numbers.

Right now I just use 255 for on, 0 for off and 2 for lowest brightness (rotate left until it bottoms out at 2).