The Lutron Caseta integration allows Pico remotes to be triggers for automations in HA, but not hardwired Caseta switches. I would like to see this same functionality added to hardwired switches/dimmers/fan controls as well. There are many use cases for this. Here are a few examples:
Double-tapping OFF on a switch near a door will turn off all lights inside the house and lock the door.
Double-tapping ON at the garage entry door will turn on all lights leading into the kitchen.
Tapping ON when a light is already on will turn on the rest of the lights in the area.
Other home automation hubs have this functionality because they support telnet communication with Caseta smart hubs, not just the new LEAP communication. Could we add telnet as an option for those Caseta smart hubs that support it to add even more features to this integration?
Isnât this similar to connecting locally or via the cloud like other integrations do? Setup would dictate which is used and then youâre stuck with one or the other.
No. Itâs all local. Just different connection methods to the Lutron hub. LEAP is the new API now used across all(most?) Lutron products. âTelnetâ uses an older API, it still works with older products, at least for now, but reportedly not for the newer products. I donât know if Lutron has any plans to fully remove it or not.
Great idea! I use the couple Picoâs I have to turn all light on or off in a zone, never thought about double tap on normal switches.
I also think itâs weird that only single and double tap are on so many things, there must be a good reason that isnât infinitely scalable to however many pushes you wanted to track.
From a quick skim of the github commits, it looks like there was a period the integration was using multiple connect methods. Still, I doubt they would go backwards to something that only works with the older products. I would err on the side of being consistent.
Hopefully there is something hidden in LEAP that can be found.
LEAP is not just cloud integration, it can be local or cloud; common industry alliances in this market are all going local (C4, Crestron, etc)
Lutron is working with a wide variety of 3rd party companies for support of QSX LEAP integration. Most of the big name companies already have integration or have QSX integration coming in the very near future.
If there is a company or product that people would like to see us integrate with, they can email [email protected] and it will get evaluated by the business
I have template code for Picos that exposes multiple clicks. It falls into the ugly, âthere must be a better wayâ category and throws errors in the logs. When I look at it now it gives me a headache, but so far works well enough I havenât bothered to go back to clean it up.
Only enumerated it out to âquadâ clicks, but that is arbitrary.
I have the same setup and my logs show the same thing, mainly the âthis automation is already runningâ item since the automation is triggered on every button press even if itâs the second press in a âdouble-tapâ.