Crestron Lutron Keypad Emulation

[chazman88]

Hi,

We're currently working on a big Lutron & Crestron project and having an issue with the crestron emulating/controlling/triggering a button press on a physical keypad.

Keypad is setup as toggles with 1 button per circuit (each with cycle dim), button 1 on each keypad also has a double tap for a predefined scene and the last button on every keypad is a single action "room off"

Ive programmed the Crestron and have set the mode as PressHoldRelease.

When tapping the button via the Crestron the LED on the matching keypad button just flashes and does not toggle the circuit on. (Its like the Lutron believes/is acting like the button has been held?)
When the circuit is already on and you press+hold the button on the crestron then the applicable circuit does cycle dim.
Double tapping the button on the Crestron also just causes the LED on the keypad to flash and the lights don't toggle.

The single press "Room Off" does work from the Crestron.

Any thoughts?

[Audible]

Since you failed to state the systems I'll make assumptions. This is QSX and you are using the Control Concepts QSX modules and programming in Simpl.
You also do not describe the Crestron device you are using to emulate the Lutron Keypad. If it's a wireless device there can be a hysteresis introduced to the system that you will need program around. Wireless can introduce a small lag that can cause some timing issues or fail to smoothly generate release commands. The other issue to look at is what are the settings for "hold" in the Lutron program. If you go to tools/project/programming how is hold time defined? Default is .5s and that could be a bit too fast for 3rd party integration via wireless. I'd change that hold time setting to 1s.

Troubleshooting.
You seem to be basing your conclusions on how the physcial keypad behaves. That just tells you integration is not working.
I would use debugger to see that the Crestron system is generating the commands on the Crestron side and terminal on the Lutron side to check that the the command works and is received.

I would also ignore the double tap logic and concentrate on the toggle logic. Check you have the button IDs correct. Check that the QSX modules all initialize. You should check the system is initialize argument in the QSX Command processor module. If it's not high, which of the modules have failed to initialize. When I threw double tap into terminal it defined the button as multi-tap. I am less interested in LED logic than I am in commands. If the command is recived from Crestron it should respond in terminal. Once you get the toggle logic working you can move on to the double tap logic.

If you are emulating a physical keypad try putting that logic on a phantom keypad. This gives you the space to play with button programming without altering the device the client touches

[Vu Nguyen]

Hi, I read your reply and I have a question. I'm using Lutron QSX with Palladiom keypad, and I am finding way to integrate Crestron into Lutron. My idea is "press" Palladiom keypad, Lutron turn on lighting, Crestron playing music. However I tested Control Concepts QSX modules, it only takes signal from Crestron to do something in Lutron such as pressing keypads. Their modules not get signal from Lutron keypad ( such as press buttons, hold buttons, ...) to do another commands in Crestron. Do you know the way to integrate Crestron into Lutron as my mentioned idea

[johnmax]

Hi, I read your reply and I have a question. I'm using Lutron QSX with Palladiom keypad, and I am finding way to integrate Crestron into Lutron. My idea is "press" Palladiom keypad, Lutron turn on lighting, Crestron playing music. However I tested Control Concepts QSX modules, it only takes signal from Crestron to do something in Lutron such as pressing keypads. Their modules not get signal from Lutron keypad ( such as press buttons, hold buttons, ...) to do another commands in Crestron. Do you know the way to integrate Crestron into Lutron as my mentioned idea

Did you try the QSX Button Control module? I am using that on several jobs to get the Lutron keypad button press into my Crestron program. Works fine. Use the Button_xx_Press_Fb signal outputs which represent when a button is pressed.

[Vu Nguyen]

Did you try the QSX Button Control module? I am using that on several jobs to get the Lutron keypad button press into my Crestron program. Works fine. Use the Button_xx_Press_Fb signal outputs which represent when a button is pressed.

Yes I tried. It is feedback when pressing button, not for holding button. So sad, my required system is holding Lutron button will command Crestron devices.

[johnmax]

You have to set the button press Fb mode to Actual and make sure you have no programming on the button on the Lutron side. Make it a regular press in Designer and then do your press and hold logic in Simpl.

From the module help:

Setting determines the functionality of the Button_[XX]_Press_Fb outputs:
• Actual: Signals transition based on Lutron feedback. Lutron button programming
must be blank for true press/release feedback.
• Press Only: Signals pulse on the press event.

[Vu Nguyen]

You have to set the button press Fb mode to Actual and make sure you have no programming on the button on the Lutron side. Make it a regular press in Designer and then do your press and hold logic in Simpl.

From the module help:

Setting determines the functionality of the Button_[XX]_Press_Fb outputs:
• Actual: Signals transition based on Lutron feedback. Lutron button programming
must be blank for true press/release feedback.
• Press Only: Signals pulse on the press event.

Yes I did program as your guide. It works. However this method is completely depended on Crestron system, there is no programming keypad on the Lutron side. It's so risk if there is connection issue between Lutron and Crestron, keypad won't turn on any lighting. I found that QS module has output signals for Lutron keypad, but can't use it for QSX system

[johnmax]

Yea thats the only issue. However I have never had a problem witht he two communicating. I do have this in an email from the guys at Control Concepts. Maybe try changing the button to Dual Action:

Thank you for using our Lutron QSX control module. Depending on how the button is programmed in Lutron, release feedback is not always sent so the signal gets stuck high.

Scenarios:
• When you need programming in Lutron on that button, change the button type to Dual Action.
• If there is no need for programming on the Button in Lutron, clear the programming logic in Lutron and set the button type to single press.

[Vu Nguyen]

Yes. I also get email from Control Concepts, they also guide me to blank programming in Lutron keypad, they didn't mention to change Dual Action for keypad button. So I will try to programming with Dual Action as you said. Thanks a lot