setting posts programmatically

[doubledrat]

Firstly, thanks for all your great work with this and sorry to be asking yet another question!

I set the comfort preset using the following

action: versatile_thermostat.set_preset_temperature
metadata: {}
data:
  temperature: 20
  preset: comfort
target:
  entity_id: climate.vt_guest2

But on the vtherm it still shows 17

But when I look at the device state, it shows 20, with no mention of 17. So will it be doing 20 or 17? And why the discrepancy

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: 20.2
temperature: 12
hvac_action: "off"
preset_mode: frost
is_on: true
hvac_mode: heat
type: null
is_controlled_by_central_mode: false
last_central_mode: null
frost_temp: 12
eco_temp: 16
boost_temp: 20
comfort_temp: 20
frost_away_temp: 12
eco_away_temp: 12
boost_away_temp: 18
comfort_away_temp: 20
target_temperature_step: 0.1
ext_current_temperature: 4.1
ac_mode: false
saved_preset_mode: frost
saved_target_temp: 14.700000000000001
saved_hvac_mode: heat
last_temperature_datetime: "2025-01-17T22:28:52.019957+00:00"
last_ext_temperature_datetime: "2025-01-17T22:00:00.005901+00:00"
minimal_activation_delay_sec: 10
total_energy: 44.8
last_update_datetime: "2025-01-17T22:29:15.061504+00:00"
timezone: Europe/London
temperature_unit: °C
is_device_active: false
device_actives: []
nb_device_actives: 0
ema_temp: 20.69
is_used_by_central_boiler: false
temperature_slope: -5
hvac_off_reason: null
max_on_percent: null
have_valve_regulation: true
last_change_time_from_vtherm: "2025-01-17T20:15:42.956501+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
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
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_guest
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 Guest2
supported_features: 401
underlyings_valve_regulation:
  - - number.trv_guest_valve_opening_degree
    - number.trv_guest_valve_closing_degree
on_percent: 0
power_percent: 0
on_time_sec: 0
off_time_sec: 300
cycle_min: 5
function: tpi
tpi_coef_int: 0.6
tpi_coef_ext: 0.005
min_opening_degrees: ""
valve_open_percent: 0
auto_regulation_dpercent: 0.5
auto_regulation_period_min: 5
last_calculation_timestamp: "2025-01-17T19:53:57.494776+00:00"

I tried disabling /enabling the vtherm and it still shows 17.

I just set comfort and eco to 10 and 11 in the ui, but in the device tools/states they're both showing as 16

Any ideas?

[doubledrat]

This is really odd. I just set them in the ui to 16 and now in states they're showing as 10 and 11. It seems they are taking the previous values? Or am I not understanding the state inspector? I'm refreshing every time I look...

[jmcollin78]

To change the temperature number of a preset (that is what you want to do if I understand well), you should use the number.set_value action targeting the number entity of the temp preset.

The versatile_thermostat.set_preset_temperature was here before I create thoses temperature entities and I guess this don't work anymore. I will have to remove this (in code and in documentation).

[jmcollin78]

In fact it works as expected but this has temporary effect. The temperature of the preset is changed but when the VTherm is reloaded it keeps its value from the number entity.

So this is expected as describe here: https://github.com/jmcollin78/versatile_thermostat/blob/main/documentation/en/reference.md#modify-the-preset-temperature

If you want permanent effect, change the number entity of the preset.

[doubledrat]

That worked.