Lutron Aurora Blueprint

[the0duke0]

I'm not sure where this belongs, so I'm starting here. The config for my Lutron Aurora switch recently stopped working. After a lot of digging, I figured out that the action_transition_time conditions in the blueprint no longer matched my switch. The blueprint has values of 0.07 (button) and 0.02 (rotation). My switch now seems to be reporting 0.7 (button) and 0.2 (rotation). I updated my blueprints/switch_manager/zigbee2mqtt-lutron-aurora.yaml and restarted HA and it is working again. I would put in a PR to update the blueprint, but I'm not exactly sure why this value changed, and if it changed for others. It may be related to a Z2M update, but I'm not positive.

[macpit]

You are right that it is a Zigbee2MQTT change, and it is not specific to your switch.

zigbee-herdsman-converters #12675 "Change action_transition_time unit to seconds" changed the conversion from transtime / 100 to transtime / 10. The Zigbee value is in tenths of a second, so the new value is the correct one and the old one was simply off by a factor of 10. Your Aurora sends transtime 7 for a press and 2 for a rotation, which is why you now see 0.7 and 0.2.

Where the change landed:

	converters	action_transition_time
Z2M 2.12.1	26.76.0	/100 -> 0.07 / 0.02
Z2M 2.13.0	26.90.0	/10 -> 0.7 / 0.2

Exactly between converters 26.81.0 and 26.82.0, so everyone lands on the new values as soon as they update to Z2M 2.13.0.

Fixed values in the blueprint can therefore only ever work for one Z2M generation, so the blueprint now matches both:

- title: press
  conditions: "{{ data.action_transition_time | float(0) in [0.07, 0.7] }}"
- title: rotate
  conditions: "{{ data.action_transition_time | float(0) in [0.02, 0.2] }}"

This is in the next release. Since I do not have an Aurora here, a confirmation from you once it is out would be very welcome - your locally edited blueprint will be overwritten by the update, so you can just remove your change and check that it still works.

Thanks for digging into this and reporting it so precisely.

[the0duke0]

I just updated to 4.3.3 and I can confirm that the new blueprint works with my Aurora and Z2M 2.13.0-1 without any modifications. Thank you!