Skip to content

Entities

Jason Rhubottom edited this page May 21, 2026 · 5 revisions

Entities

The integration dynamically adds multiple entities based on the used features.

Note on Entity Naming:

Entity IDs follow the pattern: {domain}.{device_name}_{entity_name}

Where {device_name} is the slugified version of the device name you configured during setup.

Example: For a device named "Adaptive Living Room Blind":

  • sensor.adaptive_living_room_blind_cover_position
  • switch.adaptive_living_room_blind_automatic_control
  • binary_sensor.adaptive_living_room_blind_sun_infront

These entities are always available:

Looking for diagnostic sensors? The full reference for every diagnostic sensor and binary sensor the integration exposes β€” decision_trace, control_status, last_cover_action, last_skipped_action, sun_position, position_verification, motion_status, force_override_triggers, and more β€” lives on Diagnostic Sensors.


sensor.{device_name}_cover_position (displayed as "Target Position")

State: current target position (%) determined by the integration.

Attribute Description
reason Which pipeline rule is driving the position (e.g. "no active condition β€” default position 100%").
control_method The winning pipeline handler: solar, default, manual_override, force_override, weather_override, cloud_suppression, custom_position, glare_zone, motion_timeout, summer, or winter.
position_explanation How the final position number was derived (e.g. "Sun Tracking (67%) β†’ Max Position Limit β†’ 80%").

For position-derivation attributes (raw_calculated_position, edge_case_detected, safety_margin, effective_distance, actual_positions, all_at_target), see Diagnostic Sensors.


sensor.{device_name}_climate_status (only when Climate Mode is configured)

State: Summer Mode, Winter Mode, or Intermediate. See Diagnostic Sensors for the full attribute table (temperatures, presence, sunny/lux/irradiance flags).

Note on is_sunny vs. cloud suppression: Cloud suppression can be triggered by any of four independent signals: weather state not sunny, lux below threshold, irradiance below threshold, or cloud coverage above threshold. If you only use the cloud coverage percent sensor, is_sunny will remain true (no weather entity to check) while cloud suppression still fires correctly via the cloud coverage threshold. The two signals are independent and do not conflict.


Entities Default Description
sensor.{device_name}_control_method solar Cover Position Driver: the winning pipeline handler as a single string. See Diagnostic Sensors for every possible value and what each means.
sensor.{device_name}_start_sun Shows the starting time when the sun enters the window's view, with an interval of every 5 minutes.
sensor.{device_name}_end_sun Indicates the ending time when the sun exits the window's view, with an interval of every 5 minutes.
binary_sensor.{device_name}_manual_override off Indicates if manual override is engaged for any blinds.
binary_sensor.{device_name}_sun_infront off Indicates whether the sun is in front of the window within the designated field of view.
switch.{device_name}_integration_enabled on Master kill switch. When OFF: any ACP-in-flight cover moves are stopped immediately (cover.stop_cover, capability-checked), no further commands are sent under any circumstances, including Force Override, Weather, and reconciliation. Use this when you need ACP completely silent (e.g. child safety, maintenance, testing). Diagnostic sensors continue updating. Re-enabling resumes on the next natural update cycle; covers are not snapped back to a calculated position.
switch.{device_name}_automatic_control on Solar tracking toggle. When OFF, the integration stops sending solar, climate, custom-position, motion-timeout, and end-of-time-window Return-to-Default commands. Force Override (priority 100) and Weather Override (priority 90) still fire because they are safety handlers; they must act regardless of whether sun-tracking is paused. Use Integration Enabled (above) if you need those blocked too.
switch.{device_name}_manual_override on Manual Override Detection Switch: Enables automatic detection of manual position changes. When enabled, the integration monitors your covers and pauses automatic control if you manually adjust a cover's position (via physical controls, app, or automation). The cover remains in manual mode for the configured duration (default: 2 hours), after which automatic control resumes. This allows you to temporarily take control without disabling automation entirely. Turn this switch off to disable manual override detection and always apply calculated positions.
switch.{device_name}_return_to_default_when_disabled (vertical & horizontal only) off When enabled, covers return to their default position immediately when you turn Automatic Control OFF (a one-time reposition on the toggle event). Distinct from the end-of-time-window Return-to-Default (return_sunset option), which fires at the configured end time and is itself gated on Automatic Control; see Operational Hours.
switch.{device_name}_motion_control (only when motion sensors configured) on Motion Control Switch: Enables or disables motion-based automatic positioning. When off, the motion timeout handler is skipped (lower-priority handlers such as climate and solar remain active). Useful for temporarily disabling occupancy-based control without removing the sensor configuration.
button.{device_name}_reset_manual_override on Resets manual override tags for all covers; if switch.{device_name}_automatic_control is on, it also restores blinds to their correct positions.
sensor.{device_name}_manual_override_end_time Timestamp when the manual override expires. unknown when no override is active. See Diagnostic Sensors for the per_entity attribute.

Clone this wiki locally