Features
Controls all window coverings automatically – by time, brightness, temperature and sun position.
Manual, weekly schedule or fully automatic via sensors.
Optionally, brightness is checked before the first opening and last closing.
Brightness, temperature and sun azimuth – combined with AND or OR as you prefer.
Shading and closed positions freely selectable (0–100 %).
Azimuth preselection by compass direction with automatic min/max calculation.
After manual operation the automation pauses for an adjustable time – or until the end of the day.
The slats automatically move with the blind at the open or closed end positions.
An adjustable check frequency prevents constant up-and-down movement.
How the module works
No automatic control – weekly schedule and automation are inactive.
Switches between open and closed according to the schedule. With the brightness check, the action is delayed until the threshold is reached.
Checks the conditions on every sensor change – taking into account debounce time, lock time and end-of-day lock.
Technical details: instance configuration 21 fields
| Position / actuator ID | Variable for positioning the shutter or blind. |
|---|---|
| Slats / actuator ID | Optional variable for separate slat control. |
| Brightness sensor | Outdoor brightness in lux for weekly schedule and automation. |
| Temperature sensor | Outdoor temperature in °C as a condition in automatic mode. |
| Azimuth sensor | Sun azimuth (0–360°). |
| Weekly schedule creation | No group, one group (Mon–Sun), two groups (Mon–Fri / Sat+Sun) or seven groups (per day). The times can then be adjusted. |
| Activate automatic mode | Enables “Automatic” mode in the WebFront. |
| Azimuth preselection | South (135–225°), south-east (100–160°), south-west (200–260°), east (60–120°), west (240–300°), north (330–30°), north-east (45–90°), north-west (270–315°) or manual entry. |
| Azimuth minimum / maximum | Manual fine adjustment – filled in automatically when a preselection is chosen. |
| Shading level (%) | Default 50 %, adjustable via slider in the object tree. |
| Closed level (%) | Default 100 %, adjustable via slider in the object tree. |
| Lock time (minutes) | Locks the automation after manual operation; 0 means no lock. |
| Automation after manual until end of day | Deactivates the automation after manual intervention until midnight. |
| Weekly schedule: take brightness into account | Checks the brightness at the first opening and last closing and, if necessary, waits for the next change. |
| Brightness threshold for raising (lux) | Minimum brightness for the first opening. |
| Brightness threshold for lowering (lux) | Maximum brightness for the last closing. |
| Automatic lowering (AND) | Brightness ≥ threshold, temperature ≥ threshold and azimuth within range must all be met at the same time. |
| Automatic raising (OR) | Brightness < threshold, temperature < threshold or azimuth outside the range is sufficient. |
| Debounce time (minutes) | Minimum interval between automatic checks, default 5 minutes. |
| Slats at end position | Set slats to 0 % when the shutter is open and to 100 % when it is closed. |
| Threshold variables in the object tree | Optional sliders for temperature and brightness thresholds. |
Setup step by step 6 steps
- Choose the mode in the object tree (Automatic is only visible if it is activated).
- Set the shading level.
- Set the closed level for the weekly schedule.
- Adjust the weekly schedule event below the instance.
- Change thresholds using the sliders.
- If necessary, lift locks with the ResetSperre() function, e.g. via a script.
Frequently asked questions 6 questions
Why doesn’t the shutter come down in automatic mode?
Possible causes are AND conditions that are not met, an active lock time or the end-of-day lock. The lock time can be seen in the IP-Symcon message window (KL_DEBUG).
Why doesn’t the shutter open at the scheduled time?
If the brightness is below the threshold, the module waits for the next change and then makes up for the opening.
What does the debounce time do?
It prevents frequent switching when sensor values fluctuate.
Why isn’t automatic mode visible?
It must be activated in the instance configuration.
How is the lock time reset?
Automatically when it expires, or manually via ResetSperre().
Can slats and position be controlled separately?
Yes, if both variables are entered and the matching end-position options are set.
We adapt modules – e.g. for additional sensors, bus systems or visualisations.
Interested in the Shading module?
We set it up for you and adapt it to your building.