Lutron Caseta Pico (Core Integration Only)

[erikg (Erik)]

@stephack

Allowing multiple pico remote options isn’t the point of concern for me though. It’s with regard to how confusing the UI will become and also how bloated the yaml structure would become for such a simple automation. Having used a few other consumer automation platforms has made me a firm believer in the KISS principle.

Absolutely agree with KISS.

In this case, though, the 2-button remote can work with this blueprint without any modifications to the trigger/action sections. Obviously any actions you assign to the middle/raise/lower buttons will have no effect for the 2-button remote, but the rest of it works as-is. That’s why I was looking for a way to allow both types of remotes to be selected in the input selector.