Strange behavior version 5.1.0

[Bergoglio]

Version of the custom_component

5.1.0

Configuration

My VTherm attributes are the following:

hvac_modes: heat, off
min_temp: 7
max_temp: 35
target_temp_step: 0.1
preset_modes: none, frost, eco, comfort, boost
current_temperature: 22.1
temperature: 22
hvac_action: idle
preset_mode: none
is_on: true
hvac_mode: heat
type: null
frost_temp: 0
eco_temp: 20
boost_temp: 23.5
comfort_temp: 22.5
frost_away_temp: 17
eco_away_temp: 19.5
boost_away_temp: 22.5
comfort_away_temp: 21.5
power_temp: null
target_temperature_step: 0.1
ext_current_temperature: 17.5
ac_mode: false
current_power: null
current_power_max: null
saved_preset_mode: comfort
saved_target_temp: 22
saved_hvac_mode: null
window_state: off
motion_state: null
overpowering_state: null
presence_state: off
window_auto_state: off
window_bypass_state: false
security_delay_min: 60
security_min_on_percent: 0.7
security_default_on_percent: 0.25
last_temperature_datetime: 2023-12-22T13:32:58.639198+01:00
last_ext_temperature_datetime: 2023-12-22T13:30:14.910058+01:00
security_state: false
minimal_activation_delay_sec: 300
device_power: 0.1
mean_cycle_power: null
total_energy: 22.61
last_update_datetime: 2023-12-22T13:32:58.653874+01:00
timezone: Europe/Rome
window_sensor_entity_id: binary_sensor.finestra_letto_nonna_opposto
window_delay_sec: 30
window_auto_enabled: false
window_auto_open_threshold: null
window_auto_close_threshold: null
window_auto_max_duration: null
motion_sensor_entity_id: null
presence_sensor_entity_id: person.renata_busso
power_sensor_entity_id: null
max_power_sensor_entity_id: null
temperature_unit: °C
is_device_active: false
ema_temp: 22.1
is_over_climate: true
start_hvac_action_date: null
underlying_climate_0: climate.letto_caldo_nonna
underlying_climate_1: null
underlying_climate_2: null
underlying_climate_3: null
auto_fan_mode: auto_fan_none
current_auto_fan_mode: auto_fan_none
auto_activated_fan_mode: null
auto_deactivated_fan_mode: null
friendly_name: Riscaldamento letto Nonna
supported_features: 17

Describe the bug

I have 5 Versatile Thermostats that are over 5 generic thermostats (one for one) I created 5 cards in the dashboard (one for each Versatile Thermostat) I also have Simple Scheduler component that change temp presets (comfort, eco or boost) on VTherm (time program) All worked fine before yesterday that I made upgrade to Versatile 5.1.0 from series 4 Now all cards show me not comfort, eco or boost but manual and the target temperatures settled are different from the presets (22°C for all thermostats) I changed (not only once) from manual to the right preset and after one or max two minutes, all Versatile Thermostats change them again in manual and 22°C

I read the documentation on the README.md file and I don't find any relevant information about this issue.

[jmcollin78]

Hello @Bergoglio ,

This is a very strange behavior. After installation of the 5.0.0 did you define a Central Configuration ? Did your VTherm use this central configuration.

Now all cards show me not comfort, eco or boost but manual and the target temperatures settled are different from the presets (22°C for all thermostats)

This could mean that all preset temperature are 0. But if I look at the attributes they are not null.

all Versatile Thermostats change them again in manual and 22°C

This seems really, really strange. The only way to affect all VTherm at the same time is to use a presence sensor for all Vtherm. May be this is what you have:

presence_sensor_entity_id: person.renata_busso
presence_state: off

So you are marked as absent. What is the preset used when nobody is present ?

I notive something which is badly configured:

frost_temp: 0
...
frost_away_temp: 17

Your frost protection temp is set to 0 and that is not normal.

I can suggest you to check the logs, may be something goes wrong.

[Bergoglio]

Hi @jmcollin78

I didn't use central configuration.

The problem is the same with presence_state on or off.

When nobody is present the preset is the same (eco, boost or comfort), only 1 degree less.

I didn't set the frost_temp

I will watch the logs, but now I put away all VTherm because my installation is for normal use and I cannot mantain a no working system (it is winter.....); so, i switched all to standard Home Assistant generic thermostats and I cannot make more tests.......

[jmcollin78]

And what about reverting the 5.0.1 if it was working normally ? There is nothing very important between 5.0.1 and 5.1.0. The only thing which could be related is the : [5.0.1] Preset not saved - https://github.com/jmcollin78/versatile_thermostat/issues/284

But it should touch only the configuration part. Have you try to reconfigure one or more VTherm ?

Maybe you should keep just one alive so that we will be able to test.

[Bergoglio]

I tried to reconfigure one then all VTherm, but no changes.

I'm a noob : how can I downgrade to 5.0.1 ?

I will create a VTherm for tests, but in these days I haven't a lot of time..... (I'm sorry)

[jmcollin78]

I'm a noob : how can I downgrade to 5.0.1 ?

You can go to HACS, select the VTherm and in the upper right menu, select the third menu (retelecharger in FR - re-download). Then you can specify the release you want to use.

Was it ok with 5.0.1 or did you go directly from 4.x to 5.1.0 (that could be an explanation) ?

[Bergoglio]

I went directly

[jmcollin78]

ok. What I suggest is to install the last that was working fine (4.x.0), then install the 5.0.1 check if all seems right. and only if is ok, go to 5.1.0. I will add a warning if it is the case.

[Bergoglio]

Ok, version 4.3.0 , made test VTherm + Generic Thermostat + input boolean for test

Now I will see.

[Bergoglio]

Ok, I made all possible tests.

I started from VTherm 4.3.0 and I recreated same conditions in the bug > no bug Then I made all the upgrades 4.3.0 > 5.0.0 > 5.0.1 > 5.1.0 and tested every version No bug in no version I cannot understand what happened today, but now there isn't any bug. The only idea that I have is that I made an upgrade directly from 5.0.0 to 5.1.0 and it was a problem. I'm sure, it is possible to close.

[jmcollin78]

Ok that is a good news.

The only idea that I have is that I made an upgrade directly from 5.0.0 to 5.1.0 and it was a problem.

This should have work. Upgrading from 4.x to 5.1.0 may cause some issues (but I never heard about this, just a supposition). The most likely I suppose there was an installation issue and you have some logs about what happens.

I close the issue then.