Lutron QS and AMX slow feedback
RicardoSiqueira Posts: 373
I am using the Duet AMX module in a project with Lutron QS lighting and Shading. I have 147 Lighting circuits and 50 shades. Everything is working but the feedback is slower than Lutron Illumination via RS-232. I am wondering if the problem is with the AMX Duet module or the QS network traffic. Anybody out there has similar experiences with slow feedback. On the previous Lutron non QS systems the feedback is almost instantaneous. On this current system, rooms with many lighting circuits take a while to report the Room OFF status in a Phantom keypad, something like 8 seconds. On rooms with 1 or 2 lighting circuits, 2 seconds. I am basically monitoring the OFF scene or OFF button status to report LED feedback of the room on AMX touch panels. I am also wondering, since QS is IP based, if network traffic is also an issue, which is contributing for the slow feedback. Client also wanted Levels feedback/control, which I am also monitoring and controlling, 180 levels. Is this too much maybe? Has anyone created a non Duet module that also supports feedback for LED (Button Status) who is willing to share it or is there any 3rd party module available for sale? How do you trap the feedback using the Lutron protocol. I am not sure if I will have time or have the expertise to write my own module at this time as client is moving in soon, and this is my first experience with QS. That's why I am seeking help here... Thanks!
My solution was to ditch any idea of an all-encompassing module, and just supply a wrapper to maintain the IP connection and queue commands. My commands to the module are really just pass-throughs to the QS processor. I'm not handling feedback in my module at all. I'm just parsing what comes out of the QS directly for what I'm interested in. Stripped down like that, it's acceptably responsive, but I wouldn't want to control a huge estate that way. I'm limiting myself to a few rooms of lighting and keypad control, not turning on and off every lighting load individually.
Be aware of firmware v4 and up. Somehow they made changes that are affecting processing of Duet modules that work well under v3 firmwares. Like any other dealer/programmer, I have a set of modules that have been working well for the past few years, but now they don't work as well. I called AMX tech support and they say that v4 firmware should work better, but so far on my experience some duet modules (Lutron QS & Pentair) work best under v3 firmwares. Any similar experiences?
Just curious, if you have time, update to v4 firmware and wee what happens to the speed of the feedback.
I tested my code on a V4 system before transferring to a new system with V3. My test controller is running V4, and while I didn't have the RRII hooked up to it, I simulated feedback and it was quick. Not sure if I'll be able to test it with a real system, since I am not updating live systems to V4 yet. But I hesitate to think that a new firmware could affect feedback for only one device. I would think you would see slow feedback for everything not just Lutron QS devices. After hitting a button, how long does LIGHTSYSTEMSTATUS take to show up in notifications?