Compléments et intégrations

VTherm Climate Replication is a Home Assistant custom integration for Versatile Thermostat.

It links a physical thermostat entity to a Versatile Thermostat climate entity and forwards the physical thermostat state changes to the target VTherm. The goal is to use a real thermostat as a physical remote control for a VTherm.

This plugin for Home Assistant is designed to control your pellet stove. Create an over_switch VTherm and link it to this integration to have special regulation algorithm specially designed for pellet stove.

SmartPI is an advanced PI-based thermal control algorithm built around a first-order thermal model (1R1C) rather than a classic PID loop.

It learns your room's heating capability, heat loss rate and dead time, then uses that model to compute a much more accurate heating command than fixed-time proportional controllers.

Documentation

A standalone web application to explore and visualize data history of any Home Assistant entity and its attributes

Features:

Entity Browser: Search and select any entity from your Home Assistant instance Interactive Charts: Zoom, pan, and explore entity history with ECharts Attribute Explorer: Click on chart points to view all entity attributes Custom Date Range: Select the time period you want to analyze Data Export: Export entity or attribute history to JSON for external analysis Multi-language: Available in English and French Entity Filtering: Whitelist/blacklist entities for security

Equinox is a custom Lovelace card for Home Assistant. It is designed for Versatile Thermostat while keeping compatibility with standard climate entities.

This integration provides a simple hysteresis-based heating algorithm packaged as an external integration for Versatile Thermostat.

This repository also serve as project scaffold for Vtherm plugins development.

For every over_climate VTherm exposing fan_modes, the plugin creates a set of configuration entities and, at each control cycle:

1. Computes the temperature gap dtemp = target − current. 2; Selects the underlying fan_mode whose activation threshold is the greatest one that is > 0 and ≤ |dtemp|, provided it is coherent with the current HVAC mode (heating/cooling/off).
2. Otherwise it applies the configured rest fan_mode.
3. The chosen fan_mode is only sent to the underlying when it actually changes.

Each fan_mode gets its own user-configurable threshold (a threshold of 0 means the fan_mode never participates), so non-normalized fan_modes (e.g. on_low / on_high / auto_low / off) are supported out of the box.