Yes. For some reason the Caseta docs call it a “Pico Remote”, while in other Lutron systems, which support more keypads, it’s generally called a “Pico Keypad”. But either way it’s the same thing. You’ll want to use the “pico” thing to interface to it.
BTW - The two models that Caseta supports are the -2B (for 2 button) and the -3BRL (for 3 button with raise/lower).
I am looking for some guidance to figure out what I should put in my model, what are DOs and DONTs, and maybe even things like “I have a ‘Porch light’ in hue that is associated to a ‘Porch (room)’” do I want to import both? And that’s not even looking at the fact that “Kitchen” is probably defined by all my systems: hue, Lutron Caseta, and Google Home/Assistant… Where should I start reading with a 3.0.0 focus in mind?
I’m afraid I can’t help you much there! The OH3 UI is still very new, and while I’ve played around with it in the context of binding development and like what I’ve seen so far, I haven’t tried to use semantic modeling in it yet. The docs for 3.0 are still being developed, but there are some draft versions floating around on the forum. I’d suggest searching the forum for “Getting Started with OH3”, and they should come up. In particular, you may want to look at this one: