Shades (motors) showing as lights

[sergiobaiao]

Hi there,

I'm a Lutron integrator and i'm setting up Home Assistant on a customer which has some motor modules (LQSE-4M) that controls his shades. When i setup the lutron integration on HA it got everything but the shades correctly. Shades are being shown as Lights, and i cannot control them in anyway, not even the on/off to be open/close behavior. If on/off worked i would only create a Helper template and be ok with this, but it seems like the command being sent to Lutron's processor is not correct.

If i send the command to close/open the shade over telnet it correctly show the status, but when i click on the on/off button nothing happens, not even the monitoring feedback appers on the terminal

You can see it here:
https://youtu.be/v7MpVqRnum0

[cdheiser]

Can you post your dbxmlinfo.xml somewhere we can take a look? Instructions are here: https://assets.lutron.com/a/documents/hwqs_xml_extraction_faq.pdf

[sergiobaiao]

was about to save the comment when you posted.

DbXmlInfo.xml

[sergiobaiao]

My intern (Claude) showed me already, but i'm sure you know your way...

here are all 8 motor outputs with their Integration IDs:

Integration ID | Name | Area
56 | Cortina | Home Theater
57 | Cortina | Escritório
58 | Cortina | Suite Master
59 | Cor Isabel | Quarto Isabel
60 | Cortina | Quarto Gabriel
61 | Cortinas da Porta | Sala de Estar
62 | Cortinas | Sala de Jantar
63 | Cortinas da Janela | Sala de Estar

[cdheiser]

Can you set the level with #OUTPUT,57,1,0 or 100 to open/close it?

From what I can see, an old PR added detection for Motors as SHADEs, but the Home Asisstant code just treats it like a dimmable. Only it looks like this module doesn't support setting a level, and the default brightness setting in home assistant is 50%. So when you reboot, it won't come on at 50%, but turning it off should at least move it to the closed position. Does that not work? Does explicitly setting the "brightness" to 100% not move it to the opened position?

[txwindsurfer]

This Lutron HACS implementation may address the shades: https://github.com/rzulian/lutron_lip

[sergiobaiao]

Can you set the level with #OUTPUT,57,1,0 or 100 to open/close it?

No, it does not work.
QNET> #OUTPUT,57,1,0
~ERROR,4, Not a valid command for Motor type zone
QNET> #OUTPUT,57,1,100
~ERROR,4, Not a valid command for Motor type zone

From what I can see, an old PR added detection for Motors as SHADEs, but the Home Asisstant code just treats it like a dimmable. Only it looks like this module doesn't support setting a level, and the default brightness setting in home assistant is 50%. So when you reboot, it won't come on at 50%, but turning it off should at least move it to the closed position. Does that not work? Does explicitly setting the "brightness" to 100% not move it to the opened position?

That doesn't work. No command on the shades work from HA.

Per Lutron's Integration Protocol, motors can be controlled by:
Set (#) Start Raising 2
Set (#) Start Lowering 3
Set (#) Stop Raising or Lowering 4

So it would be #OUTPUT,57,2 or #OUTPUT,57,3 to open/close and #OUTPUT,57,4 to stop.

[cdheiser]

That's strange. Page 100 of the integration protocol guide says it should work: for LQSE-4M https://assets.lutron.com/a/documents/040249.pdf Guess it's another lutron quirk. We can try the simple thing to make a breaking change in home assistant to model motors as covers.

…

On Tue, Apr 7, 2026 at 5:44 AM Sergio Baiao ***@***.***> wrote: *sergiobaiao* left a comment (thecynic/pylutron#124) <#124 (comment)> Can you set the level with #OUTPUT,57,1,0 or 100 to open/close it? No, it does not work. QNET> #OUTPUT,57,1,0 ~ERROR,4, Not a valid command for Motor type zone QNET> #OUTPUT,57,1,100 ~ERROR,4, Not a valid command for Motor type zone From what I can see, an old PR added detection for Motors as SHADEs, but the Home Asisstant code just treats it like a dimmable. Only it looks like this module doesn't support setting a level, and the default brightness setting in home assistant is 50%. So when you reboot, it won't come on at 50%, but turning it off should at least move it to the closed position. Does that not work? Does explicitly setting the "brightness" to 100% not move it to the opened position? That doesn't work. No command on the shades work from HA. Per Lutron's Integration Protocol, motors can be controlled by: Set (#) Start Raising 2 Set (#) Start Lowering 3 Set (#) Stop Raising or Lowering 4 So it would be #OUTPUT,57,2 or #OUTPUT,57,3 to open/close and #OUTPUT,57,4 to stop. — Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQARWVW5IZXOIXYRRLFGN34UTZ3BAVCNFSM6AAAAACXOZYMXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCOJZGAZDSNJQGU> . You are receiving this because you were assigned.Message ID: ***@***.***>

[sergiobaiao]

It does accept actions 2 and 3, maybe stick with that?

[cdheiser]

Can you file a bug against home assistant? pylutron is behaving properly. It's home assistant that needs to be fixed.

…

On Tue, Apr 7, 2026 at 4:30 PM Sergio Baiao ***@***.***> wrote: *sergiobaiao* left a comment (thecynic/pylutron#124) <#124 (comment)> It does accept actions 2 and 3, maybe stick with that? — Reply to this email directly, view it on GitHub <#124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQARWQQCREJG27IZTQPNGD4UWFRVAVCNFSM6AAAAACXOZYMXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMBSHAYDCOJSGA> . You are receiving this because you were assigned.Message ID: ***@***.***>

[sergiobaiao]

just did that...

home-assistant/core#167640
along with
#128