Automation
Motorized shades frequently fail the practical test of daily living when they fight the occupants. An automated shade that drops while someone is looking out the window or refuses to budge after a manual adjustment quickly creates friction. The goal of this automation is to regulate passive solar heating and ensure evening privacy across living spaces without locking occupants into rigid, unyielding routines.
### The Goal and Core Logic The automation adjusts window covers dynamically to balance two conflicting needs: harvesting daylight and reducing HVAC load during extreme outdoor temperatures, while securing visual privacy after dusk or when leaving the house. By using Matter-over-Thread motors, commands execute locally on the home network, avoiding cloud latency or external dependency.
### Triggers The automation monitors four distinct trigger points in Home Assistant: 1. **Sun Position Changes:** Solar elevation and azimuth thresholds tailored to the orientation of specific window banks (e.g., southern or western exposures). 2. **Indoor/Outdoor Temperature Deltas:** State changes on local thermal sensors indicating the room has exceeded cooling setpoints while direct sun is present. 3. **Occupancy and Ambient Light:** Motion or presence detection transitioning to occupied after sunset, or lux dropping below a baseline threshold. 4. **Perimeter Lock State:** Exterior deadbolts locking for the night or the home switching to an away security profile.
### Conditions and Interlocks Before dispatching motor commands, the automation checks several defensive conditions: - **Contact Sensor Interlock:** A contact sensor on sliding patio doors or operable windows must report `closed`. Lowering a shade while a door is ajar risks catching the hem bar on handles, tearing fabric, or jamming the roller. - **Manual Override Status:** A dedicated helper entity (`input_boolean.shade_manual_override_[room]`) must be `off`. If a resident manually moved the shade via a wall remote, physical button, or dashboard within the past two hours, automated adjustments are bypassed. - **Thermal Benefit Check:** In summer, shades drop only if indoor temperature exceeds target comfort and outdoor solar radiation is hitting that specific facade. In winter, the logic inverts to allow solar gain during peak daylight hours.
### Actions When conditions pass, Home Assistant calls the `cover.set_cover_position` service over the local Thread mesh: - **Glare and Thermal Defense:** Set shades to 20–30% open, blocking direct upper-angle solar penetration while preserving floor-level ambient light. - **Privacy and Night State:** Set shades to 0% (fully closed) when exterior door locks engage after sunset or occupancy is detected in illuminated street-facing rooms. - **Morning Reset:** Raise shades to 100% (fully open) at sunrise or when the morning schedule clears the night mode, provided the manual override flag has reset.
### Safeguards and Manual Fallback Physical agency must always supersede automation logic. Every motorized shade should retain a paired local Thread or RF wall switch. A secondary automation monitors the shade position attribute: if the position changes without an automation trigger, Home Assistant toggles the manual override helper `on` for a configurable duration (such as 120 minutes), preventing the system from immediately fighting the user's manual preference.
If the smart infrastructure fails entirely, physical battery-operated remotes paired directly to the shade motors continue to function even if the Home Assistant server or Thread border router is offline.
### Failure Behavior If a Thread endpoint drops offline or a motor battery depletes, Home Assistant logs an unreached state but does not loop or retry aggressively, which would drain battery reserves. Motor internal limit calibrations remain stored on the physical shade hardware; an offline event does not cause the shade to over-travel or lose its top/bottom stops.
### Privacy and Maintenance Matter-over-Thread keeps all telemetry and operational commands local to the home border routers (such as Apple HomePods, Home Assistant Yellow, or dedicated Thread border routers), preventing window state data from leaking to third-party cloud analytics. Maintenance is minimal: monitor battery percentages via a low-battery alert threshold (e.g., under 15%), inspect solar charging panels semi-annually for dust accumulation, and inspect side channels or hem bars for alignment drift twice a year.