Velair 1.7.0

Velair 1.7.0

Velair 1.7.0 brings the work refined throughout the beta series into a stable release. It adds Manual adjustment handling, a local Diagnostics workspace, improved Room Assist control, external schedule execution, faster schedule cloning, and four new languages.

✨ Highlights

• Managed climates can now detect changes made outside Velair. The default Keep automatic policy preserves Velair control, while optional policies can enter Manual adjustment until the next schedule block, for a configured duration, or until automatic control is resumed.
• Added a local, read-only Diagnostics workspace with scheduler and per-climate health, bounded runtime history, configurable categories, privacy-safe support reports, a global status sensor, and automation events.
• Compatible zones can publish their effective Default, Profile, or Mode schedule to an external controller.
• The first supported external system is Evohome through ramses_cc, validated with feedback from a real installation.
• Schedule cloning now includes Mon–Fri, Weekend, All days, and Clear selection shortcuts.
• Added complete contextual translations for Italian, Polish, Brazilian Portuguese, and European Portuguese.
• Completed and reviewed the maintained German, French, Dutch, Russian, and Spanish catalogues.

🌡️ Room Assist

• Room Assist now has its own per-climate deadband.
• Fixed heating and cooling use a stateful hysteresis cycle between the configured limits.
• Automatic modes and native temperature ranges retain their appropriate neutral or boundary-margin behavior.
• The live graph clearly represents the active limits and keeps the complete translated deadband legend centered on the represented range.
• Existing effective values migrate automatically without requiring manual changes.

🔌 External schedule execution

Externally executed zones remain schedule-only. Velair publishes the effective weekly schedule but does not send Boost, pause, resume, Manual adjustment, Room Assist, Adaptive Preconditioning, or other direct climate actions while the external controller owns execution.

For Evohome through ramses_cc:

• Schedules use scalar heating targets.
• Switchpoints use a 5-minute grid.
• A maximum of six translated switchpoints is supported per day.
• An implicit midnight continuity point counts towards that limit when required.
• Published means that the external integration accepted the service call. Velair does not claim physical application from a cached readback, poll the controller, or retry automatically.

🚀 Interface improvements

• Overview, Settings, Schedules, Room Assist, and Diagnostics now provide clearer execution ownership, publication state, controller limits, operational notices, and responsive layouts.
• External schedule editors show daily controller usage, including editable blocks and any implicit midnight continuity point.
• External controller information integrates naturally with the existing Overview indicators.
• Documentation, screenshots, and website assets have been updated to reflect the final stable behavior.
• Fixed the active Boost animation extending outside its timeline block after resizing the panel or using a narrow screen.

❤️ Thank you

Thank you to everyone who has supported Velair, tested the beta releases, reported issues, shared ideas, and helped refine both existing behavior and new features.

A particularly sincere thank you goes to the people who have chosen to support Velair through its first donations. Velair started as something I created from scratch to solve a need in my own home, and it is incredibly satisfying to see other people use it, find genuine value in it, and even decide to contribute financially to its continued development.

Velair remains completely free and open source. Every test, suggestion, discussion, recommendation, and donation helps the project continue to improve.

💬 Join the discussion

GitHub Discussions is now available as a shared place to talk about Velair, exchange experiences, suggest improvements, propose new use cases, and help other members of the community.

Community feedback has been part of Velair’s decisions from the beginning. Several features and refinements in this release were shaped directly by real-world experiences shared by users, and that collaboration will continue to guide the project.

If you use Velair, please feel welcome to participate. You do not need to be a developer or have deep technical knowledge: describing how you use climate control at home, what works well, what feels unclear, or what could make Velair more useful can provide valuable direction.

Join Velair Discussions

🧭 Before updating

• Existing installations retain automatic Velair authority by default.
• Existing schedules, Profiles, Modes, Room Assist settings, and external-adjustment behavior require no manual migration.
• External execution is optional and only appears when a supported Home Assistant integration and its required services are available.
• External-change attribution depends on the climate integration exposing sufficient Home Assistant context and state information.

After updating through HACS, restart Home Assistant and refresh the browser or Companion app. If the previous interface remains visible, perform a hard refresh or clear the site cache.