Buying Motorized Shades? Here's the Control Side Nobody Quotes

Motorized shades get quoted as a product: fabric, size, motor, done. What often doesn't get quoted is everything that makes them behave like part of the house rather than a separate gadget with its own remote.

We don't sell shades — that's the window-covering trade, and they should do it. We do the control side, which is why we see what goes wrong when the two are specified separately. Here's what to settle before you order.

The question that decides everything: does anything else need to know about them?

If the answer is no — you'll operate them from their own app or remote, and that's fine — you can stop reading. Buy the shades, have them installed, done.

If the answer is yes — you want them on your keypads, in your scenes, on a schedule, or in the same app as your lights — then the control question has to be answered before you order, because it may change which shades you buy.

This is the split that catches people. Shades chosen purely on fabric and price sometimes can't be integrated with the system already in the house, and by the time anyone notices, they're on the wall.

Two questions to ask the shade supplier

1. What does the control side speak, and how? Some systems are controlled over the network, some by radio, some through a hub or bridge that translates. Which one determines whether your existing system can talk to them at all, and what extra equipment sits in between.

2. Do they report their real position back? This one matters far more than it sounds. A shade that only accepts open, close, and stop — with position estimated from how long the motor ran — looks fine for a week. Then someone uses the manual control, or a shade loses power, and now your system says 40% while the fabric is at the top. Every scene after that is wrong, and no amount of programming fixes it.

True position feedback means the shade tells the system where it actually is. It also means the icon on your touchscreen is telling the truth, which is most of what you're paying for when you integrate them at all.

What's usually missing from the quote

• A bridge or interface so the shade system and your lighting or automation system can talk. Often a real part with a real cost.
• Power where the shades are for mains-powered motors, or a plan for charging or replacing batteries on the ones that aren't. Battery shades in a high window are a job later.
• Programming time to put them into scenes and onto keypads.
• Keypad buttons or engraving, if the shades are meant to be operated the same way as everything else. Engraved buttons are physical parts and have lead times.

None of these are large individually. Together they're the difference between shades that feel integrated and shades that came with another remote.

Grouping: the mistake that annoys people daily

If a room has several shades, they should move as one unless there's a specific reason not to. A room whose shades open in two stages because they were added at different times, or put in separate groups, is irritating every single day.

Same for adding to an existing installation: put the new ones in the group the existing ones are already in, rather than creating a second one. This is a five-minute programming decision that determines whether the room feels finished.

Which windows are actually worth it

Motorising every window is how budgets disappear. The ones that earn it:

• Windows causing glare on a screen or television at a predictable time of day.
• West-facing glass that overheats a room in the afternoon.
• Anything you can't reach — high, over furniture, behind a bath.
• Bedrooms, if you want them on a wake or goodnight scene.

Windows you walk past and could operate by hand in two seconds are usually not worth motorising, and a supplier who agrees with you on that is worth keeping.

If you already have shades and want them integrated

Often possible, occasionally not, and the deciding factor is the same two questions above: how the control side communicates, and whether it reports position.

What we'd need to tell you: the make and model of the shade motors or their hub, whether there's a bridge already, and what system you want them to appear in — plus its processor model and version.

If they can be integrated, it's usually a driver and some programming, done remotely. If they can't, we'll say so rather than sell you an interface that half works.

Two things to settle before anyone leaves

Whoever installs them:

Get the limits set properly and check them. The top and bottom stopping points, on every shade, verified. A shade that stops half an inch short is a thing you'll notice forever.

Get a copy of the project file if the shades were added to an existing system. Your programming lives on the processor, and if nobody else has a copy, that box holds the only record of your house. This applies to every change, not just shades.

And one thing worth measuring twice

Shades are made to order and generally can't be returned. Measure the openings yourself even if they look identical — we've measured three "identical" windows in one room and got three different numbers. Also match the exact fabric and colour name if you're adding to an existing order, and ask about the production run: fabric can shift lighter or darker between runs, and you won't notice until they're all hanging in daylight next to each other.

That's the shade supplier's territory, not ours. But it's the mistake that costs the most, so it's worth saying.

If you're planning shades and want to know what the control side involves before you commit, tell us what system you have and what you're being quoted. We do Control4 and Lutron work remotely, and we'll tell you honestly when the integration isn't worth doing.