💡 Sensor Light - Motion Sensor - Door Sensor - Sun Elevation - LUX Value - Scenes - Time - Light Control - Device Tracker - Night Lights

That is such a profound realization, that you might consider adding a toggle-helper widget, by default, to your blueprint. It can always be deleted, right? Maybe it could be a virtual-only dial-entity, called a blacky.

The blacky would be a home screen widget with a rotary-dial ist of labelled states, for an entiry or device that only exists virtually. Picos would pair to the blacky, and would be the only thing that could change the blacky’s state. Much better than using a physical $120 Lutron plug-in dimmer which is othewise not physically in use.

Not sure how relevant these posts are, but this implies Lutron pig- used to show up in HA without this.

EDIT: Lutron Pico remote switches are zigbee. So, If you unpair them from the non-pro version of the Lutron Bridge/Hub (because it uses HA-incompatible-SSH, not HA-friendly-Telnet), then you can connect these picos to HA via LEAP. This requires some kind of CASETA LEAP ADD-ON thingy, I am still researching that… Stay tuned.