Skip to content

Releases: jmcollin78/versatile_thermostat

Issue #820 - improve power shedding algorithm

13 Jan 17:53
Compare
Choose a tag to compare

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

This pre-release tries to fix this issue:

Issue #820 - improve power shedding algorithm

It adds a check at VTherm underlying device startup to check if power is available. If not the Vtherm wil be shed.

7.1.3

12 Jan 17:08
Compare
Choose a tag to compare

What's Changed

  • Issue #804 - cannot set preset when follow is activated by @jmcollin78 in #812
  • Issue #779 - error in ValveOpenPercent sensor at startup by @jmcollin78 in #814
  • Allow to enter 3 digits after dot values in coef_ext.
  • some documentation improvements

Full Changelog: 7.1.2...7.1.3

Try to fix #804 (bis)

12 Jan 11:14
Compare
Choose a tag to compare
Try to fix #804 (bis) Pre-release
Pre-release

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

This pre-release is another rty to fix the #804 issue.

Try to fix #804

12 Jan 09:39
Compare
Choose a tag to compare
Try to fix #804 Pre-release
Pre-release

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

This pre-release tries to fix the issue #804 - cannot set preset when follow is activated.

It adds some logs and add the missing reset _last_regulation_change datetime when the setpoint is sent to the underlying device.

7.1.2 - community fixes and improvements

12 Jan 08:58
43d8e5e
Compare
Choose a tag to compare

What's Changed

Full Changelog: 7.1.1...7.1.2

7.1.2.beta1

11 Jan 21:51
Compare
Choose a tag to compare
7.1.2.beta1 Pre-release
Pre-release

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

What's Changed

Try to fix #807 .

Full Changelog: 7.1.1...7.1.2.beta1

7.1.1

08 Jan 07:29
Compare
Choose a tag to compare

What's Changed

  • issue #790 - hvac-off-reason is not restored after restart by @jmcollin78 in #793
  • issue #789 - add auto-start/stop precision in documentation

Full Changelog: 7.1.0...7.1.1

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

05 Jan 17:18
Compare
Choose a tag to compare

⚠️ Please update the Versatile Thermostat UI Card to the latest release, if you install this release.

What's Changed

See: documentation En, Fr

New Contributors

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

7.1.0.beta1

04 Jan 18:15
Compare
Choose a tag to compare
7.1.0.beta1 Pre-release
Pre-release

-- 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