self regulation issue with the managemen of Open Window sensor status

[alsmaison]

I have several Daikin AC. Because of temperature issue with the internal sensor, I have configured several Versatile Thermostat to be able to use external temperature sensors.

As I have Velux connected equipments, I can know if windows are opended or not. I use this information to stop heating during house ventilation through open windows.

I see that if my Versatile Thermostat use a "self regulation" configuration, the management of the open window sensor is not correct. Indeed, the Versatile Thermostat go to frost configuration when the window is open BUT my Daikin AC stay with the current instruction and never go to frost.

There is no problem if my Versatile Thermostat has a "self regulation' to "none". On this case, the frost mode is applied to Versatile Thermostat and my Daikin AC.

[jmcollin78]

Hello,

Why do you think it is a VTherm issue ? Vtherm "just" sent the new temperature target to your Daikin. If it is working for Eco it should be working as is for Frost. There is no difference on VTherm side.

Maybe you can have a look in the logs and search for Daikin error

[alsmaison]

I have tested on the same Daikin AC 2 different configurations of the Versatile Thermostat. If the Self regulation is configured as "none'", the Open Windows logic works perfectly. Versatile Thermostat has the frost value and the Daikin AC also. If I change the Self regulation to another value, my physical Daikin AC continue to work with the current temperature value and the Versatile Thermostat has the frost value.

This is why I think there is a issue in the Versatile Thermostat.

[jmcollin78]

Not reproduced and you don't give me the attributes of your Vtherm nor logs. So I have nothing to investigate.

I guess it is a matter of regulation period (see here: https://github.com/jmcollin78/versatile_thermostat/blob/main/documentation/en/self-regulation.md#other-self-regulation). If you have a regulation period configured, this prevent VTherm to send too much command to the underlying device. This could leave to ignore some change done in Vtherm.

Can you set it to 0 and try to reproduce the case ?
Can you send me the attributes (https://github.com/jmcollin78/versatile_thermostat/blob/main/documentation/en/reference.md#custom-attributes) and the logs when this issue is reproduce on your environment. See here to get the logs: https://github.com/jmcollin78/versatile_thermostat/blob/main/documentation/en/troubleshooting.md#enable-logs-for-the-versatile-thermostat

Don't forget to install the last release 7.1.2 when I write this lines.

Thank you for your help.

[alsmaison]

I have tested with the last release. Unfortunetly, this is still not working.
Please find my configuration here :

hvac_modes: fan_only, dry, cool, heat, heat_cool, off
min_temp: -20
max_temp: 50
target_temp_step: 0.1
friendly_name: Thermostat Chambre Parentale
supported_features: 441
current_temperature: 18.1
temperature: 19.5
is_on: true
hvac_action: heating
hvac_mode: heat
preset_mode: none
type: null
is_controlled_by_central_mode: true
last_central_mode: null
frost_temp: 10
eco_temp: 18.5
boost_temp: 20
comfort_temp: 19.7
frost_away_temp: 10
eco_away_temp: 18
boost_away_temp: 19
comfort_away_temp: 19
target_temperature_step: 0.1
ext_current_temperature: 5.6
ac_mode: true
saved_preset_mode: none
saved_target_temp: 19.5
saved_hvac_mode: null
last_temperature_datetime: 2025-01-16T12:54:22.855840+01:00
last_ext_temperature_datetime: 2025-01-16T12:38:31.580415+01:00
minimal_activation_delay_sec: 240
total_energy: 1164561.28
last_update_datetime: 2025-01-16T12:54:22.861713+01:00
timezone: Europe/Paris
temperature_unit: °C
is_device_active: true
device_actives: climate.chauffage_chambre_parentale
nb_device_actives: 1
ema_temp: 17.95
is_used_by_central_boiler: false
temperature_slope: 1.36
hvac_off_reason: null
max_on_percent: null
have_valve_regulation: false
last_change_time_from_vtherm: 2025-01-16T12:54:06.056374+01:00
presence_sensor_entity_id: input_boolean.etat_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: 2500
power_temp: 18
current_power: null
current_max_power: null
mean_cycle_power: null
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: binary_sensor.etat_chambre_parentale_ouverture
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: 5
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.chauffage_chambre_parentale
is_regulated: true
regulated_target_temperature: 19.5
auto_regulation_mode: auto_regulation_light
regulation_accumulated_error: 1.6999999999999993
auto_fan_mode: auto_fan_turbo
current_auto_fan_mode: auto_fan_turbo
auto_activated_fan_mode: null
auto_deactivated_fan_mode: null
auto_regulation_use_device_temp: false
follow_underlying_temp_change: false
preset_modes: none, frost, eco, comfort, boost
fan_modes: Auto, Silence, 1, 2, 3, 4, 5
swing_modes: Off, Vertical, Horizontal, 3D
fan_mode: 2
swing_mode: Off