[{"data":1,"prerenderedAt":44},["ShallowReactive",2],{"$ff3m1M_HQmiBG57dxYpGJ45IGAL--eiur7gpoQhNrSkQ":3},{"id":4,"title":5,"tags":6,"view_count":8,"vote_count":9,"answer_count":10,"has_accepted_answer":11,"accepted_reply_id":12,"created_at":13,"last_activity_at":14,"thumbnail_url":15,"is_technical":11,"has_solution_keywords":11,"related_thread_id":16,"author":17,"author_avatar":18,"body":19,"replies":20},48,"Lutron HomeWorks QSX keypad not triggering motorized shades",[7],"lutron-homeworks-qsx-keypad-not-triggering-motorized-shades",2467,64,8,true,2,"2026-03-15T13:23:54.785221","2026-03-15T13:23:54.785231","https:\u002F\u002Fpicsum.photos\u002Fseed\u002Fthread-48\u002F1024\u002F768",null,"SmartHomePro2026","https:\u002F\u002Fui-avatars.com\u002Fapi\u002F?name=SmartHomePro2026&background=random&color=fff","Hey everyone,\n\nI'm pulling my hair out on this one. I have a HomeWorks QSX system installed about 8 months ago and everything was working fine until last week. Now the keypad in the master bedroom (seeTouch) won't trigger the Sivoia QS motorized shades in that room. The weird thing is:\n\n- The shades work fine from the Lutron app\n- The shades work fine from Alexa voice commands\n- The same keypad controls the lights in the room perfectly\n- Other keypads in the house can control these same shades\n\nIt's literally just this one keypad to these specific shades. I've tried rebooting the processor and no luck. Any ideas before I call my integrator back out? Thanks!",[21,25,28,31,34,36,39,42],{"username":22,"body":23,"is_accepted":24},"LutronProMike","Classic symptom. Have you checked if the button assignment got corrupted somehow? Sometimes a firmware update or power event can cause the programming to get wonky. Can you access the Designer software or is this dealer-locked?",false,{"username":26,"body":27,"is_accepted":24},"ShadeGuyTX","Had something similar last month. Turned out the button LED feedback was still programmed but the actual shade control got unlinked. Check in the app under that keypad's button config - is the shade still showing as assigned to that button?",{"username":29,"body":30,"is_accepted":24},"OP_ResidentTechDad","Thanks for the quick replies. I don't have access to Designer - my integrator set everything up. In the Lutron app I can see the button is supposed to control \"Master Shades\" but pressing it does nothing. The LED on the keypad does light up when I press it though.",{"username":32,"body":33,"is_accepted":11},"HomeAutoSolutions_Jim","The fact that the LED responds but the shade doesn't move tells me the keypad itself is fine. This is almost certainly a programming\u002Fdatabase issue on the processor side. One thing you CAN try without Designer access:\n\n1. Go to Settings > Integration > Integration Report in the app\n2. Look for any errors related to that zone\n3. Try removing the shade from the button assignment and re-adding it through the app (if your integrator gave you that level of access)\n\nIf none of that works, your integrator will need to pull up the project in Designer and check the conditional logic. Sometimes there's a timelock or occupancy condition that gets triggered incorrectly.",{"username":29,"body":35,"is_accepted":24},"Jim - you're a genius! I checked the integration report and there was an error about \"conditional conflict\" on that button. I don't have permission to edit button assignments but I forwarded the report to my integrator. He remoted in and apparently there was a vacation mode conditional that got stuck active somehow. Fixed in 5 minutes. Thank you!",{"username":37,"body":38,"is_accepted":24},"AVInstaller_Chicago","Vacation mode strikes again! I always tell my clients to be careful with those conditionals. Glad you got it sorted without a truck roll.",{"username":40,"body":41,"is_accepted":24},"SmartHomeSarah","Filing this away for future reference. We have HomeWorks QSX going in next month and this is exactly the kind of troubleshooting info I need. Thanks for posting the solution!",{"username":22,"body":43,"is_accepted":24},"Good catch on the conditional. For what it's worth, I always recommend integrators set up a \"kill all conditionals\" button somewhere hidden (like a 5-tap on a specific keypad) for exactly these situations. Saves a lot of headaches.",1784825298089]