Autonomous sounds like giving up control. For someone used to being in charge it can feel uncomfortable: a system that does things on its own. But autonomy doesn't mean you lose control – it moves to a better level. With Pendax SOLO you still decide, on two levels.
The worry: a system I can't control
It's a reasonable worry. The word "autonomous" implies that someone else – the machine – has taken over, and that you're left on the sidelines. Nobody wants to discover that the shading does the opposite of what the business needs, with no way to intervene. So let's be clear about where control actually sits.
Level 1: the user can always take over
In the moment, on site, anyone can override the automation. A press on the keypad or a command in the mobile app takes over immediately; the automation pauses for a set time and then resumes. Nobody is stuck with a shade that won't obey – the override is always there as a safety net.
Level 2: the organisation steers the autonomy
The more important control, though, isn't fiddling with every movement – it's deciding how the system behaves in the first place. You do that by choosing the decision model and setting parameters: thresholds, wait times, comfort levels, how cautiously or actively the shade should act. You don't micromanage; you set the rules, and the units follow them. That's control at scale.
To see how it's done, try the configuration tool; to understand what the model and parameters do, read How does the decision engine work?
Our kind of "custom programming"
Here's the crux. A system that does exactly what you want is usually assumed to require custom programming. At Pendax SOLO, "custom programming" means something else: your own choice of decision model and your own parameters. You tailor the behaviour – but by configuring the unit, not by writing unique code for it.
The difference is decisive. All tailoring happens within the same, proven firmware that every SOLO runs. If a single unit instead needed its own code, that code would have to exist on every unit for the standard chain between SOLO and CONDUCTOR to hold together. Then you're back in a black box – hard to upgrade, document and support (see How a shading system is built and What do you do with an old system that's no longer supported?).
By expressing all tailoring as configuration, you get the best of both worlds: behaviour that suits your particular building, and a system that stays standardised, upgradeable and controllable centrally across the whole portfolio.
In short: you decide – at the right level
- In the moment: anyone can take over with the keypad or app.
- At the core: you choose the decision model and parameters for how the automation acts.
- Over time: the same standard on every unit lets you adjust and control the whole portfolio from one place.
The autonomy does the work. You stay in control.
And when an individual still isn't happy with their own shade? See the follow-up: What do you do when someone isn't happy with their shade?