UI Configuration Entities

In addition to the rather static configuration settings managed through the wizard, the integration’s behavior can be controlled via switches and other UI configuration entities on the device page of the integration instance.

Integration Settings

The entities in this section control how the integration works.

Enabled

Enables or disables the automation. This should be viewed as a on/off switch, a quick way to stop the integration altogether, one step short of deactivating it by Home Assistant’s means.

Simulation Mode

If simulation mode is enabled, the automation runs through all calculations without actually moving the covers.

Verbose Logging

Verbose logging enables or disables detailed logging.

Cover Settings

The entities in this section control the cover movements.

Automatic Reopening

Choose how automation should reopen covers when closing conditions no longer apply. The following settings are available:

Active: Always reopens covers. In this mode, covers that were closed manually are reopened after the manual override duration has elapsed.
Passive: Only reopens covers that were previously closed by automation. In this mode, covers that were closed manually are not reopened.
Off: Disables automatic reopening.

Lock Mode

Lock mode moves the covers to either opened or closed state, or keeps them in their current position. It then locks the covers, keeping them in that position until lock mode is disabled.

Lock mode can be manually set, but is primarily designed to be triggered as an action, e.g., when a wind or hail warning is received from a weather service. Note that such automations are not part of this integration and need to be set up by the user.

Lock mode has the following options:

Unlocked (automation active) [default]
Hold current position
Force open and lock
Force close and lock

Manual Override

Manual override duration specifies how long a cover is skipped after it has been moved manually (0 = no skipping).

Tilt Angle (External Control)

These entities are only created when you select External as tilt angle control mode in the configuration wizard.

Global Entities

If External is configured as the global tilt angle control mode for day and/or night, the integration creates the corresponding global entity:

Tilt angle: external control (day): External tilt angle used during daytime.
Tilt angle: external control (night): External tilt angle used at night, including evening closure.

Use case: you want to calculate the slat angle yourself, for example from your own sun-position logic or a custom shading automation.

Per-Cover Entities

If External is configured as a per-cover tilt angle control mode override, the integration creates a dedicated entity for that cover:

Per-cover Tilt angle: external control (day)
Per-cover Tilt angle: external control (night)

Per-cover external tilt values take precedence over the matching global external tilt values.

Sun & Temperature Settings

The entities in this section control at which temperatures and sun positions the integration automates cover movements.

Sun Azimuth

Sun azimuth tolerance: The maximum horizontal angle at which the sun is considered to be shining on the window (degrees).

Sun Elevation

Minimal sun elevation: The automation starts operating when the sun’s elevation is above this threshold (degrees above the horizon).

Heat Protection Temperature Thresholds

The integration uses both the daily minimum and maximum temperatures to determine whether the weather is hot enough to require heat protection. Configure minimum and maximum temperature thresholds via the following entities:

Heat protection: min. daily high temperature
Heat protection: min. daily low temperature

Weather: Hot? (External Control)

Global Entity

This binary switch is disabled by default. If you enable it, the integration stops using the weather forecast to determine if it’s hot. In its stead, it uses the state of this switch. To go back to the weather forecast, simply disable it again.

Use case: you want to create your own logic for determining when it’s “hot enough” to close the covers, e.g., based on indoor temperature.

Per-Cover Entity

In addition to the global entity, the Weather: hot? state can be externally configured for each cover individually. To that end, the integration creates one (initially disabled) entity per cover.

The integration determines a cover’s Weather: hot? state by checking the following in the given order:

Per-cover Weather: Hot? (External Control) entity (if enabled).
Global Weather: Hot? (External Control) entity (if enabled).
Global calculation based on weather forecast data.

Weather: Sunny? (External Control)

This entity allows you to set the sunny state much more accurately through an external source than is possible by way of the weather forecast.

This binary switch is disabled by default. If you enable it, the integration stops using the weather forecast to determine if it’s sunny. In its stead, it uses the state of this switch. To go back to the weather forecast, simply disable it again.

Use case: you have your own pyranometer or luxmeter and want to use its measurements to tell this integration when it’s “sunny enough” to close the covers.

Practical example: use your PV to determine if the sun is shining.

Time Settings

The entities in this section control externally supplied time values.

Morning Opening (External Control)

This entity is only created when Morning opening: mode is set to External in the configuration wizard.

The integration then uses the configured time as the earliest time at which covers closed by evening closure may reopen again.

Use case: you want to determine the morning opening time from your own automation, for example based on household schedules, alarm times, or another Home Assistant integration.

Next Steps

After configuration, see the Troubleshooting Guide for common issues and solutions.