Issue when disabling a vtherm with Spook

[doubledrat]

Version of the custom_component

7.1.4

Configuration

hvac_modes: off, auto, heat
min_temp: 10
max_temp: 25
target_temp_step: 0.1
preset_modes: none, frost, eco, comfort, boost
current_temperature: 19.9
temperature: 20
hvac_action: heating
preset_mode: comfort
is_on: true
hvac_mode: heat
type: null
is_controlled_by_central_mode: true
last_central_mode: null
frost_temp: 12
eco_temp: 16
boost_temp: 22
comfort_temp: 20
frost_away_temp: 12
eco_away_temp: 12
boost_away_temp: 18
comfort_away_temp: 12
target_temperature_step: 0.1
ext_current_temperature: 5.3
ac_mode: false
saved_preset_mode: comfort
saved_target_temp: 12
saved_hvac_mode: null
last_temperature_datetime: 2025-02-01T16:49:31.263633+00:00
last_ext_temperature_datetime: 2025-02-01T16:51:28.578959+00:00
minimal_activation_delay_sec: 10
total_energy: 36.88
last_update_datetime: 2025-02-01T16:57:28.557270+00:00
timezone: Europe/London
temperature_unit: °C
is_device_active: true
device_actives: number.trv_bedroom_east_valve_opening_degree, number.trv_bedroom_west_valve_opening_degree
nb_device_actives: 2
ema_temp: 19.89
is_used_by_central_boiler: true
temperature_slope: 0.49
hvac_off_reason: null
max_on_percent: null
have_valve_regulation: true
last_change_time_from_vtherm: 2025-02-01T16:52:28.557833+00:00
presence_sensor_entity_id: binary_sensor.arcadia_presence
presence_state: on
is_presence_configured: true
power_sensor_entity_id: null
max_power_sensor_entity_id: null
overpowering_state: unavailable
is_power_configured: false
device_power: 1
power_temp: null
current_power: null
current_max_power: null
mean_cycle_power: 0.13
motion_sensor_entity_id: null
motion_state: unavailable
is_motion_configured: false
motion_delay_sec: 30
motion_off_delay_sec: 300
motion_preset: comfort
no_motion_preset: eco
window_state: unavailable
window_auto_state: unavailable
window_action: window_turn_off
is_window_bypass: false
window_sensor_entity_id: null
window_delay_sec: null
window_off_delay_sec: null
is_window_configured: false
is_window_auto_configured: false
window_auto_open_threshold: null
window_auto_close_threshold: null
window_auto_max_duration: null
is_safety_configured: true
safety_state: off
safety_delay_min: 60
safety_min_on_percent: 0.5
safety_default_on_percent: 0.1
is_auto_start_stop_configured: false
is_over_climate: true
start_hvac_action_date: null
underlying_entities: climate.trv_bedroom_east, climate.trv_bedroom_west
is_regulated: true
regulated_target_temperature: null
auto_regulation_mode: auto_regulation_valve
regulation_accumulated_error: 0
auto_fan_mode: auto_fan_none
current_auto_fan_mode: auto_fan_none
auto_activated_fan_mode: null
auto_deactivated_fan_mode: null
auto_regulation_use_device_temp: false
follow_underlying_temp_change: true
friendly_name: VT Bedroom
supported_features: 401
underlyings_valve_regulation: 
- - number.trv_bedroom_east_valve_opening_degree
  - number.trv_bedroom_east_local_temperature_calibration
- - number.trv_bedroom_west_valve_opening_degree
  - number.trv_bedroom_west_local_temperature_calibration

on_percent: 0.13
power_percent: 13
on_time_sec: 40
off_time_sec: 259
cycle_min: 5
function: tpi
tpi_coef_int: 0.6
tpi_coef_ext: 0.005
min_opening_degrees: 
valve_open_percent: 13
auto_regulation_dpercent: 0.5
auto_regulation_period_min: 5
last_calculation_timestamp: 2025-02-01T16:51:28.583832+00:00

Describe the bug

If a vtherm is "used by central boiler" and is contributing to the total number of devices calling for heat at the time it is disabled, the count is not decremented. this means the heating will stay on forever (or until the vtherm is enabled again).

e.g. the above vtherm counts as 2 devices calling

steps to reproduce the bug

1. vtherm calling for heat
2. "nb device active for boiler" = 2
3. disable the vtherm
4. "nb device active for boiler" is still = 2. It should be 0 and it will never be 0 as the vtherm is now disabled.

I'm trying to:
disable a vtherm

And I expect:
Once disabled, no longer contribute to the "nb device active for boiler" count

But I observe this ....
Once disabled, still contributes to the "nb device active for boiler" WWWif it was doing so at the time it is disabled.

Debug log

2025-01-31 21:25:45.117 INFO (MainThread) [custom_components.versatile_thermostat.base_thermostat] VersatileThermostat-VT Bedroom - Removing thermostat

logs don't show the device active count unfortunately

[jmcollin78]

Hello,

How did you disable a Vtherm ? Can you show me with screen copy how you do that ?

[doubledrat]

Using spook ``` action: homeassistant.disable_config_entry metadata: {} data: config_entry_id: 01JH95SP9HN81BWYS5V5XDYGTH alias: Disable vt bedroom ```

…

On Sun, 2 Feb 2025, 20:27 Jean-Marc Collin, ***@***.***> wrote: Hello, How did you disable a Vtherm ? Can you show me with screen copy how you do that ? — Reply to this email directly, view it on GitHub <#882 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADZMGBLCKYFL4JFVXBBSL5T2NZ5URAVCNFSM6AAAAABWJQEJ2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRZGU2DENZRHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jmcollin78]

Ah ok. I don't know what spook does. What I use is to disable the VTherm with this menu and it works. I use it for doing some tests.

[jmcollin78]

I will close this because of Spook usage which don't work and transform this into a Q&A discussion.