search on this group, we had a conversation about it, but basically the LED comes from a different module and different lutron ID

Thanks, but my question isn't about the LED feedback......

It's about the ability for Crestron to be able to send press + press and hold functions.?

开云体育

Try turning the cycle dim off in the lutron program and see if you are able to control the lights again.

开云体育

Curious... did you try "Auto" mode?

Feel free to Control Concepts for support:



support.controlconcepts.net

Jeff

@Jeff

Where would I find "Auto" mode?

Thanks
Charlie

Just wanted to see if there was a resolution to this issues.? It does whether I am using v1.0 or v1.2 modules.

Phantom button is a Press for scene/Hold for cycle dim.

depending on the parameter setting? of the module.? I either get the Scene recall or I get the cycle dim function, but not both.

parameter set for press/release = Scene recall and no cycle dim
parameter set for press/hold/release = Cycle Dim and no scene recall.? Unless the button doesn't have cycle dim option, then the scene recall works.

I had some issues with the modules and I reached out to Mike Spadafora at Control Concepts (who created the modules) and he was very helpful. Hopefully he doesnt mind me sharing his email:?
mikes at controlconcepts.net

Where's the best place to download the latest modules??

Nevermind, I found them on the App Market...I assume that these are the latest/best???

I had this issue recently with just one button of 64.
I found a quick work around just to leave on a Friday.
I used an SIO and send (not exact as I'm camping, and doing this from memory) #Device,<deviceID>, 4/n
Usually a 3 is sent for press.
A 4 is sent for release, And works every time.
If your looking for hold or double tap, good luck.

Has anyone figured this cycle dimming problem out?? Press/Release with cycle dims on loads doesnt work.? Press/Release/Hold just creates all sorts of madness.? v1.2

Hey there! I'm a developer for Control Concepts and we actually wrote this module suite. If you're still experiencing issues with this, we'd love to take a look and give you a hand.?
Here's how you can get in touch:?

Thanks Mike!? I left you a voicemail this morning.? Give me a shout back when you get a chance.

Does anybody know if there is a solution for this?
Back on another site and having the exact same issue.?
Had hoped this would have been sorted by now........

On Fri, Aug 11, 2023 at 05:03 AM, charliehibbins wrote:

Does anybody know if there is a solution for this?
Back on another site and having the exact same issue.?
Had hoped this would have been sorted by now........

I worked with Jen E. from ControlConcepts on this and we bounced around a bunch of attempts.? Unfortunately, we weren't able to get a resolution from the modules themselves.? I don't exactly recall why, something to do with the feedback the Lutron QSX system is kicking back.? There is a way to do the press/hold dimming concept outside of the module, unfortunately it created a lot of work for this particular project having to monitor load levels and determining when a load was >0 or =0.? Basically, put a press and hold on the button itself, if held and the level = 0, hold the dim+ command.? If load > 0 dim- command.? The caveat to this was the Lutron system doesn't report its actually load level until ramping is complete so there is some more juggling you need to do for seamless UI presentation.

We just had way too many loads to do this with on this project and I didn't want to spend the time working it all out ($$$).? We ended up just doing on/off's for each load then setting a High, Medium, Low preset scene for each room.

We have a couple QSX systems coming up here this month (for some reason we have been lucky in getting QS systems this summer, probably due to backorders) so I will be revisiting this topic soon and most likely will strip down the CC module and build it out to accomplish this.? From what Jen told me, they didn't plan on updating their module quite yet.

Hope this helps.

I have not done any QSX systems yet, just QS (which works well).
I'm curious for future use:
It is fair to say that Lutron has fundamentally changed their protocol or at least how certain *standard* functions work that would require a completely new approach to integrating with them?? TIA!

On Fri, Aug 11, 2023 at 01:41 PM, ckangis wrote:

I'm curious for future use:
It is fair to say that Lutron has fundamentally changed their protocol or at least how certain *standard* functions work that would require a completely new approach to integrating with them?? TIA!

Answering my own question...in a word...YES...:(
And not in a good way, IMO...