jmcollin78/versatile_thermostat 8.0.0.beta1

on GitHub

What's Changed

THIS IS A PRE-RELEASE. DON'T INSTALL IT IF YOU ARE NOT INVITED TO DO SO. The documentation is updated in this branch

A special discussion link is available if you need more explanations or if you want to report an issue with this release: #1201

Release 8.0

This is a major release. It rewrites a significant part of the internal mechanisms of Versatile Thermostat by introducing several new features:

1. requested state / current state: VTherm now has 2 states. The requested state is the state requested by the user (or Scheduler). The current state is the state currently applied to the VTherm. The latter depends on the different VTherm functions. For example, the user can request (requested state) to have heating on with Comfort preset but since the window has been detected open, the VTherm is actually off. This dual management always preserves the user's request and applies the result of the different functions on this user request to get the current state. This better handles cases where multiple functions want to act on the VTherm state (window opening and power shedding for example). It also ensures a return to the user's initial request when no detection is in progress anymore,
2. time filtering: the time filtering operation has been revised. Time filtering prevents sending too many commands to a controlled equipment to avoid consuming too much battery (battery-powered TRV for example), changing setpoints too frequently (heat pump, pellet stove, underfloor heating, ...). The new operation is now as follows: explicit user (or Scheduler) requests are always immediately taken into account. They are not filtered. Only changes related to external conditions (room temperature for example) are potentially filtered. Filtering consists of resending the desired command later and not ignoring the command as was previously the case. The auto_regulation_dtemp parameter allows adjusting the delay,
3. hvac_action improvement: the hvac_action reflects the current activation state of the controlled equipment. For an over_switch type it reflects the switch activation state, for an over_valve or valve regulation, it is active when the valve opening is greater than the minimum valve opening (or 0 if not configured), for an over_climate it reflects the underlying climate's hvac_action if available or a simulation otherwise.
4. custom attributes: the organization of custom attributes accessible in Developer Tools / States has been reorganized into sections depending on the VTherm type and each activated function. More information here.
5. power shedding: the power shedding algorithm now takes into account equipment shutdown between two measurements of home power consumption. Suppose you have power consumption feedback every 5 minutes. If a radiator is turned off between 2 measurements then turning on a new one may be authorized. Before, only turn-ons were taken into account between 2 measurements. As before, the next power consumption feedback will possibly shed more or less.
6. auto-start/stop: auto-start/stop is only useful for over_climate type VTherm without direct valve control. The option has been removed for other VTherm types.
7. VTherm UI Card: all these modifications allowed a major evolution of the VTherm UI Card to integrate messages explaining the current state (why does my VTherm have this target temperature?) and if time filtering is in progress - so the underlying state update has been delayed.
8. log improvements: logs have been improved to simplify debugging. Logs in the form --------------------> NEW EVENT: VersatileThermostat-Inversed ... inform of an event impacting the VTherm state.

⚠️ Warning

This major release includes breaking changes from the previous version:

• versatile_thermostat_security_event has been renamed to versatile_thermostat_safety_event. If your automations use this event, you must update them,
• custom attributes have been reorganized. You must update your automations or Jinja templates that use them,
• the VTherm UI Card must be updated to at least V2.0 to be compatible,

Despite the 342 automated tests of this integration and the care taken with this major release, I cannot guarantee that its installation will not disrupt your VTherms' states. For each VTherm you must check the preset, hvac_mode and possibly the VTherm setpoint temperature after installation.

Other contributions

• Update CONTRIBUTING-de.md by @FMainz in #1136
• feat(i18n): add Russian translation by @sergeybelozorov in #1142
• Update IT translation by @silviopen in #1149
• Revision of German translation by @FMainz in #1165
• Update german translation by @FMainz in #1174
• [Versatile Thermostat] Polish Version is Ready-to-Use by @Krzysztonek in #1179
• Fix Polish translation for minimal_deactivation_delay by @Krzysztonek in #1191
• Fix typo in presence description in Polish translation by @Krzysztonek in #1192
• Rename README-pl.MD to README-pl.md by @Krzysztonek in #1194
• README.md <=> README-pl.md Update ready to be merged by @Krzysztonek in #1188
• Fix link format in troubleshooting documentation by @jebabin in #1196
• Link Updates by @FMainz in #1198

New Contributors

• @sergeybelozorov made their first contribution in #1142
• @silviopen made their first contribution in #1149
• @Krzysztonek made their first contribution in #1179

Full Changelog: 7.4.1...8.0.0.beta1