Lutron Pico Button Issues

Button numbers do not appear to be sync'd:

I pressed Volume Up on the Pico and then Volume Down:

image

Why is Volume Up being identified at button 2 and Volume Down as button 4?

Is this being defined in button controller?

Your Hubitat to Lutron mapping is off. Hubitat numbers button 1-5 from top to bottom. Lutron does not. Hubitat raise is button 2 and lower is button 4. As compared to Lutron Telnet where raise is 5 and lower is 6. As a Hubitat user you only need to know the Hubitat convention of 1-5, top to bottom. The only reason to know Lutron's mapping is if you want/need to know how to interpret the Telnet output.

Lutron's Telnet documentation:

3 Likes

Thank you.

Now, in the absence of your knowledge and willingness to educate, how on God's good green Earth would I ever know this?

I love how powerful Hubitat is but I feel like I'm constantly having to ask questions because the Documentation is lacking, the UI isn't intuitive, configuration pages don't contain hints or instructions, capabilities are buried deep in menus, etc.

Is it not obvious that we don't need the word "push" three times on a button and that it would be much more helpful to have something like, "HINT: Pico buttons are numbered 1 to 5 from top to bottom."
image

/rant

I don't have a good answer, but thankfully it's a one time issue. You were on the right track to figure it out on your own. Press each button and see what the log output is.

To add another consideration: if you are using the Pico to raise and lower the volume by holding the button you'll need to change the driver to 'Lutron Pico' from 'Lutron Fast Pico'. The fast Pico doesn't do a hold, so if you use it you'll need to repeatedly press the button to change the volume.

Just a note on this: Fast Pico doesn't do held, but it does do released (pushed and released with every button press on the real device)--so you can't just use those two events instead of held and released if you want go get a "while held" kind of thing (I do this for lights; never used it for volume, but if you have commands to start and stop raising/lowering the volume, it should be the same).

The regular Pico driver would give you the advantage of being able to do something different if you're not holding the button, at the expense of that first event taking a bit longer to register (upon release of the button--if you're not holding--rather than the moment it is pushed down).

1 Like

Download the Hubitat app