7.1.0 - full rework on Load-shedding (power management)

What's Changed

• (chore) Lint base_* files by @cova-fe in #769
• Issue #770 - Change percent_open calculation method by @zepala in #772
• Issue #766 - enhance_power_management by @jmcollin78 in #778

See: documentation En, Fr

New Contributors

• @cova-fe made their first contribution in #769
• @zepala made their first contribution in #772

Full Changelog: 7.0.0...7.1.0

---

⚠️ Breaking change :

1. because the power management is now centralized, you should have a central configuration with the power feature activated and configured,
2. the non-central power sensor parameters are removed,
3. a delay of 20 sec is possible between the last power measurement is received and the load-shedding run.

In case of power exceeded, Versatile Thermostat will now do shedding for all the VTherm with power management activated. It will set to overpowering VTherms at first with the one which current temperature is near the target temperature, until the power is reach.

If power comes available, the un-overpowering is done in reverse order (the more far away for the target first).
Regularly, the active Vtherm may change following the preceding rules.

To add debug logs you should add this lines into your logger.yaml:

custom_components.versatile_thermostat.feature_power_manager: debug
custom_components.versatile_thermostat.central_feature_power_manager: debug

7.1.0.beta3

Fix overpowering is set even if other heater have on_percent = 0

Fix too much shedding in over_climate

Add logs

Add temporal filter for calculate_shedding

Fix restore overpowering_state

Full Changelog: 7.1.0.beta1...7.1.0.beta3

7.1.0.beta1

-- DO NO INSTALL. A BUG HAVE BEEN DETECTED --

What's Changed

• implementation of the #766 issue - enhance the power management

See in the issue what have been done.

⚠️ Breaking change :

1. because the power management is now centralized, you should have a central configuration with the power feature activated and configured,
2. the non central power sensor parameters are still there but no more used (will be remove for the release).

In case of power exceeded, Versatile Thermostat will now do shedding for all the VTherm with power management activated. It will set to overpowering VTherms at first with the one which current temperature is near the target temperature, until the power is reach.

If power comes available, the un-powering is done in reverse order (the more far away for the target first).
Regularly, the active Vtherm may change following the preceeding rules.

To add debug logs you should add this lines into your logger.yaml:

custom_components.versatile_thermostat.feature_power_manager: debug
custom_components.versatile_thermostat.central_feature_power_manager: debug

Full Changelog: 7.0.0...7.1.0.beta1

7.0.0

What's Changed

• Issue #739 - refactor-to-modularize by @jmcollin78 in #742
• Add installation link by @romainvv in #762
• Issue #754 - hvac_reason_of is not restored at startup.

New Contributors

• @romainvv made their first contribution in #762

Full Changelog: 6.8.4...7.0.0

---

#739 have a big impact on code:

• Add a Presence Feature manager
• Add a Power Feature manager
• Add a Window Feature manager
• Add Auto-start/stop feature manager
• Add safety feature manager
• Update documentation and release
• Use python 3.13 as required by HA now

This will allow clarification and increase maintainability and testability of the integration. Further PR done by community should be easier to implement and to test.

Notes:

1. You have to update the VTherm UI Card to release 1.1.0: https://github.com/jmcollin78/versatile-thermostat-ui-card/releases/tag/1.1.0
2. Until the window/presence/power/... is not evaluated it is considered as state UNKNOWN,
3. All states that end with _states are now states ('on', 'off', 'unknown', 'unavailable') and not boolean,
4. no functional improvements have been done. This release is only a technical release.

7.0.0.beta1

Do not install this pre-release if you are not invited to do so.

Content

A preview of a massive technical refactor (should be mainly iso).
Main changes are: until the window/presence/power/... is not evaluated it is considered as state UNKNOWN.
All states that ends with _states are now states ('on', 'off', 'unknown', 'unavailable').

Pull request : #742

Full Changelog: 6.8.4...7.0.0.beta1

Community fixes - 6.8.4

What's Changed

• [feature] for 'It's not possible to set regulation mode to Expert using Automations' by @Edwintenhaaf in #718
• [feature] Add attribute with active underlyings for easier tracking and setup by @s256 in #658
• Issue #698 nb device active for boiler not updating by @jmcollin78 in #728
• [feature] #722 - Add a minimum opening degree for valve regulation by @jmcollin78 in #729
• Issue #690 - VTherm don't follow underlying change with lastSeen activated by @jmcollin78 in #732
• issue #683 - incorrect temperature reversion on window close (*) by @jmcollin78 in #734
• issue #733 - VTherm over_climate not following TRV device setpoint when step if < 1 by @jmcollin78 in #736
• issue #713 - config_entry is deprecated by @jmcollin78 in #738
• issue #702 - crash after 2024.12 Attribute error

(*) the open window detection behavior have been changed: now if you try to change the preset or the target temperature while the window is open (and window action is configured to Anti-fronzen), VTherm will keep the froze temperature. The new preset or temperature will be applied when the window will be detected as closed.

New Contributors

• @Edwintenhaaf made their first contribution in #718
• @s256 made their first contribution in #658

Full Changelog: 6.8.3...6.8.4

6.8.4.beta3

What's Changed

• Add attribute with active underlyings for easier tracking and setup by @s256 in #658
• Issue #698 nb device active for boiler not updating by @jmcollin78 in #728
• Feature #722 - Add a minimum opening degree for valve regulation by @jmcollin78 in #729
• Issue #690 - VTherm don't follow underlying change with lastSeen activated by @jmcollin78 in #732
• issue #683 - incorrect temperature reversion on window close by @jmcollin78 in #734
• issue #733 - VTherm over_climate not following TRV device setpoint when step if < 1 by @jmcollin78 in #736
• issue #713 - config_entry is deprecated by @jmcollin78 in #738

New Contributors

• @s256 made their first contribution in #658

Full Changelog: 6.8.4.beta1...6.8.4.beta3

6.8.4.beta2

What's Changed

• Add attribute with active underlyings for easier tracking and setup by @s256 in #658
• Try to fix #698 - nb_device_active don't work for climate without hvac_action

You have a new attrbutes in the nb_device_active entities which lists the active entities. Thank to @s256

New Contributors

• @Edwintenhaaf made their first contribution in #718
• @s256 made their first contribution in #658

Full Changelog: 6.8.3...6.8.4.beta2

6.8.4.beta1

What's Changed

• fix for 'It's not possible to set regulation mode to Expert using Automations' by @Edwintenhaaf in #718
• Try to fix Issue #702 (2nd try)

New Contributors

• @Edwintenhaaf made their first contribution in #718

Full Changelog: 6.8.3...6.8.4.beta1

6.8.3

What's Changed

• issue #702 - migrate to HA 2024.12 by @jmcollin78 in #708

Full Changelog: 6.8.2...6.8.3