All temperature sensors in Climate mode must use the same unit. If your Indoor Temperature Entity reports Celsius, the Outdoor Temperature Entity and both comfort thresholds must also be Celsius. The integration does not convert between units, and mixing °F and °C produces incorrect results.

To fix a mismatch, point all sensors at a source using the same unit, or use template sensors to convert. See Climate configuration for where to point the entities.

Configure and test Basic mode first, confirm your covers respond correctly to sun position, then add Climate mode. Climate mode adds temperature thresholds, presence detection, and weather conditions; troubleshooting is significantly harder when both are active at once.

Home Assistant cover entities control only one dimension at a time, position or tilt angle, not both simultaneously. For venetian blinds that support both vertical movement and slat tilting, create two separate Adaptive Cover Pro instances pointing at the same cover entity:

1. Vertical instance: controls up/down position
2. Tilt instance: controls slat angle

Example: "Adaptive Office Blind Vertical" and "Adaptive Office Blind Tilt" both target cover.office_blind. Each monitors the sun independently and sends its own commands to the same physical device.

For the full venetian dual-axis sequencer, manual-override timing, and tilt back-rotation behaviour, see Venetian Blinds.

Weather entities may lag actual conditions by an hour or more and don't always distinguish cloud types accurately. Lux and irradiance sensors give better real-time signal for cloud suppression. If you rely on a weather entity, verify it updates at least every 5–15 minutes.

Sensors unavailable at startup (common with Zigbee2MQTT and Z-Wave, which often take 20–60 seconds to initialize) don't block the integration. It uses safe defaults until sensors come online:

• Missing lux/irradiance sensors: defaults to "light available", falls back to weather-based operation
• Missing temperature sensors: defaults to the comfortable range, uses basic glare calculations
• Missing weather sensors: uses sun position only

If a sensor stays unavailable and behavior looks wrong after startup, see Troubleshooting Step 7.

Covers that support only OPEN and CLOSE commands are handled with threshold-based control:

• The integration calculates position as normal (0-100%)
• If calculated position ≥ threshold → cover opens
• If calculated position < threshold → cover closes
• Default threshold is 50% (adjustable in Automation configuration, 1-99%)

Limitations:

• Granular position control is not possible
• Intermediate positions are not available
• Tilt covers must support SET_TILT_POSITION (open/close mode not supported)

Example use cases:

• Simple roller shutters with only up/down buttons
• Garage doors with open/close only
• Budget blinds without position feedback

Inverse state with open/close-only covers:

The "Inverse the state" option inverts the calculated position before comparing it to the threshold:

• Without inverse: Position 30% → 30% < 50% → CLOSE command
• With inverse: Position 30% → inverted to 70% → 70% ≥ 50% → OPEN command

Enable this if your cover's OPEN and CLOSE commands appear to work backwards.

Custom-position Minimum Mode is a pipeline-layer floor. It constrains the position ACP itself sends to a cover, but it cannot intercept direct cover.set_cover_position calls made from dashboards, scripts, or external automations — those calls reach the cover unchanged and also mark the cover as manually overridden, pausing ACP automation.

If you need automations to honour the active floor, call adaptive_cover_pro.set_position instead. It clamps the requested position up to the highest active minimum-mode floor before sending the command. Tilt is not affected.

Time window transitions (start/end times): covers respond within 1 minute. Log messages show "Time window state changed: inactive → active" when transitions occur.

Sun position, temperature, weather, and presence sensor changes trigger immediate updates. The delta position and delta time settings then determine how frequently covers actually move.

After Home Assistant restart: covers are repositioned on the first refresh (typically within 30 seconds). Position verification begins immediately.

Position verification: every minute the integration confirms covers reached their target position and retries up to 3 times if not.

Start/end times define a daily operational window, not a precision timer. For time-critical events, use a Home Assistant automation with a time trigger instead.

If a cover is unresponsive within the expected window, see Troubleshooting Step 3.