Commit Graph

6 Commits

Author SHA1 Message Date
b209b70467 Make force ON entity optional for Climate Device Controller.yaml
All checks were successful
Gitea Actions Demo / Explore-Gitea-Actions (push) Successful in 3s
2026-01-25 16:10:29 +03:00
9885d3f8e9 Add hysteresis and force ON override to Climate Device Controller
All checks were successful
Gitea Actions Demo / Explore-Gitea-Actions (push) Successful in 3s
- Add hysteresis window to prevent rapid on/off cycling
  Device turns OFF at target, ON at (target - window)
- Add Force ON switch for manual override capability
- Restructure control logic with explicit priority checks
- Default action now maintains state in hysteresis zone
- Update documentation with hysteresis example
2026-01-25 15:31:13 +03:00
565cde77f6 [Claude] - Let's analyze Climate Device Controller.yaml blueprint. Can we somehow make it more flexible, but removing tight connection to switch entity type. What if, for example, I want to control air conditioner via smart remote. Can you offer something for that case and make appropriate changes to the blueprint? But the new logic should to control a switch as currently. 2026-01-22 03:22:07 +03:00
fb642ee7d6 Fixed author for Climate Device Controller.yaml 2026-01-22 02:24:49 +03:00
c76339a4a6 [Claude] - Analyze Climate Device Controller.yaml file designed to work as automation blueprint for Home Assistant OS. Refactor it improving overall code quality, fix obvious or critical bugs/mistakes, fix spelling if required and add comments that will make the code more easy to read and understand. 2026-01-22 02:24:27 +03:00
35f11d7e30 Initial commit with existing blueprints 2026-01-22 01:46:04 +03:00