The list of valve seems incorrect + add Sonoff installation informations in README.

[jmcollin78]

          I had a working setup with the the Sonoff TRVZB with firmware 1.1.X and using a switch as thermostat. 

I have upgraded the firmware to 1.2.1 and I'm tying to setup the thermostat using climate + the SONOFF TRVZB mode but nothing really happens anymore in my system.

For example, I don't understand why in this situation the heating is not on

This is my first attempt to setup Versatile Thermostate, so might be missing something trivial

UPDATE:

Using a valve thermostate and using the valve opening degrees as underlying managed to turn on the boiler + the valves on my thermostates.

Originally posted by @gbasile in #645 (comment)

[jmcollin78]

Hello @gbasile

Let's continue here. Please give me the attributes of your VTher (see https://github.com/jmcollin78/versatile_thermostat/blob/main/README.md#custom-attributes) and if you can some regulation curves (see: https://github.com/jmcollin78/versatile_thermostat/blob/main/README.md#even-better-with-plotly-to-tune-your-thermostat)

[eflye]

@gbasile dit you enable manually Valve closing degree and Valve opening degree on your trv entity in HomeAssistant. You have to do it first in order to have Sonoff TRV native support on Vth.

[jmcollin78]

ok @eflye , this is an important information, by default thoses entities are not visible I understand

[gbasile]

Thanks for creating a dedicated issue for my problem 🙌

@gbasile dit you enable manually Valve closing degree and Valve opening degree on your trv entity in HomeAssistant. You have to do it first in order to have Sonoff TRV native support on Vth.

I have missed this piece of information. Can you point me to the right direction?

[jmcollin78]

Thank you the beers ! Cheers 🍻

You have to go to Parameters / Devices. Find you Sonoff device and click on "more attributes" (or something like that) . Then you will able enable the missing attributes.
Example:

[gbasile]

I think I have misunderstood the previous message (I was looking for an attribute calledmanually valve closing degree)

In my device the following are available, without any manual change from my side:

• Valve opening degree
• Valve closing degree

These attributes are the ones that currently are driving the TRV when configured in valve mode. For some reason when I configure the thermostate as climate mode with the sonoff configuration enabled, the. system is not working anymore

[jmcollin78]

ok. Then can you give me the attribute of the VTherm ? (see: https://github.com/jmcollin78/versatile_thermostat/blob/main/README.md#custom-attributes)

[eflye]

maybe Diagnostic one should be enabled? In order to get curent value

It creates sensor._valve_opening_degree and sensor._valve_closing_degree
wheras the one you see on the Configuration are
number._valve_opening_degree and number._valve_closing_degree

Which want do you use @jmcollin78

[gbasile]

The VTherm state

hvac_modes:
  - "off"
  - auto
  - heat
min_temp: 7
max_temp: 35
target_temp_step: 0.5
friendly_name: Living Room debugging
supported_features: 401
current_temperature: 22.8
temperature: 24.5
hvac_action: "off"
is_on: true
hvac_mode: heat
preset_mode: none
type: null
is_controlled_by_central_mode: true
last_central_mode: null
frost_temp: 10
eco_temp: 19
boost_temp: 24
comfort_temp: 22
frost_away_temp: 0
eco_away_temp: 0
boost_away_temp: 0
comfort_away_temp: 0
power_temp: null
target_temperature_step: 0.5
ext_current_temperature: 18.24
ac_mode: false
current_power: null
current_power_max: null
saved_preset_mode: none
saved_target_temp: 24.5
saved_hvac_mode: heat
motion_sensor_entity_id: null
motion_state: null
power_sensor_entity_id: null
max_power_sensor_entity_id: null
overpowering_state: null
presence_sensor_entity_id: null
presence_state: null
window_state: "off"
window_auto_state: "off"
window_bypass_state: false
window_sensor_entity_id: null
window_delay_sec: null
window_auto_enabled: false
window_auto_open_threshold: null
window_auto_close_threshold: null
window_auto_max_duration: null
window_action: window_turn_off
security_delay_min: 60
security_min_on_percent: 0.5
security_default_on_percent: 0.1
last_temperature_datetime: "2024-11-21T23:03:54.966667+01:00"
last_ext_temperature_datetime: "2024-11-21T23:03:54.973145+01:00"
security_state: false
minimal_activation_delay_sec: 10
device_power: 1
mean_cycle_power: null
total_energy: 0
last_update_datetime: "2024-11-21T23:03:54.974857+01:00"
timezone: Europe/Madrid
temperature_unit: °C
is_device_active: false
ema_temp: 22.8
is_used_by_central_boiler: true
temperature_slope: 0
hvac_off_reason: null
max_on_percent: null
is_over_climate: true
start_hvac_action_date: null
underlying_entities:
  - climate.mqtt_trv_1_living_room
auto_fan_mode: auto_fan_high
current_auto_fan_mode: auto_fan_high
auto_activated_fan_mode: null
auto_deactivated_fan_mode: null
auto_regulation_use_device_temp: false
auto_start_stop_enable: true
auto_start_stop_level: auto_start_stop_medium
auto_start_stop_dtmin: 15
auto_start_stop_accumulated_error: 1.6999999999999993
auto_start_stop_accumulated_error_threshold: 5
follow_underlying_temp_change: false
preset_modes:
  - none
  - frost
  - eco
  - comfort
  - boost
is_over_sonoff_trvzb: true
underlying_sonoff_trvzb_entities:
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_1_living_room_valve_opening_degree
  - number.mqtt_trv_1_living_room_valve_opening_degree
  - number.mqtt_trv_1_living_room_valve_opening_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.01
valve_open_percent: 0
auto_regulation_dpercent: 0.5
auto_regulation_period_min: 5
last_calculation_timestamp: "2024-11-21T23:03:45.821005+01:00"

[gbasile]

@eflye I have enabled them now

[jmcollin78]

Oooh there is a problem:

underlying_entities:
  - climate.mqtt_trv_1_living_room

...
underlying_sonoff_trvzb_entities:
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_2_office_valve_opening_degree
  - number.mqtt_trv_1_living_room_valve_opening_degree
  - number.mqtt_trv_1_living_room_valve_opening_degree
  - number.mqtt_trv_1_living_room_valve_opening_degree

This should be not possible. there is trv2 and too many underlying_sonoff_trvzb_entities.

This is clearly a bug. I think you will have to recreate it from scratch.

[gbasile]

I'm happy to give it and recreate the entire configuration from scratch.
Just to be on the same page, I will:

• Remove all the devices from the Versatile Thermostat integration
• Recreate a central configuration and the single thermostats

I will not:

• Unpair/Pair again the MQTT devices
• Factory reset the physical devices

Is that correct?

[jmcollin78]

No need to recreate the central configuration. Only the VTherm which uses the Sonoff TRVZB (in beta). And only the one who is incorrect. No need to removes the others if you have and if they works fine

The others points are correct.

[gbasile]

Well, in that case I don't think much will change: this Thermostat has been recreated now as part of the effort of understanding the problem with the climate mode.

Basically my journey today has been:

• configure the thermostat with climate + sonoff config (not working)
• delete this thermostat and recreate it with valve (working)
• [as part of the investigation for this issue, 30 minutes ago] delete the thermostat and recreate it with climate + sonoff in order to share the attributes

[gbasile]

Update: all of a sudden the thermostat started to work 🎉

This is despite the multiple entries inunderlying_sonoff_trvzb_entities

At the moment my best guess is that the diagnostic sensor that @eflye recommended to enable might have been key to solve the problem.

I'm going to verify this assumption with my other thermostat as following:

• Remove the existing device
• Create a climate thermostat with sonoff config
• Verify if the thermostat is working
• Expose the diagnostic sensors
• Verify if the thermostat is working

[jmcollin78]

Nice but there is a bug in the list.

[gbasile]

Exposing xxx_opening_degree and xxx_closing_degree from the diagnostic makes the thermostat valves to move in the system.

I wonder whatever we should:

• Investigate if possible to avoid the manual step of exposing these attributes
• Update the documentation and/or the UI of the sonoff config to warn the user about this requirement

[gbasile]

For the moment I have removed the duplications from the list to see if the system works as expected without those duplicates.

There are still some behaviours that I don't fully understand. Are these as expected or not?

1. I turn the thermostat to 24 degree (1.6 higher then room temperature)
2. Valves opens to 100% ✅
3. Thermostat is not requesting for heating ❌
4. Boiler is off ❌

Screenshot for more context

Adding the plot as in the documentation, as it might be easier for you to review

[jmcollin78]

• Update the documentation and/or the UI of the sonoff config to warn the user about this requirement

Yes !

[jmcollin78]

3. Thermostat is not requesting for heating ❌

Yes, there is still a bug on this reported in the main thread. It is requested for heat if the valve is open, but the display seems wrong.

4. Boiler is off ❌

Yes this is a consequence of the point /3. The boiler is started if VTherm are requested for heat.

[jmcollin78]

Maybe we can keep this thread only for documentation and valve list and come back the main thread because you have solve your main issue. Your points can interest the others.

[gbasile]

Regarding the valve list:

• Yesterday night I have clean-up the configuration to remove the duplicates (set state)
• Today the list is corrupted again

I am able to reproduce in this way:

1. Clean the duplications and set new state
2. Reload the VTherm thermostat from the integration page
3. Duplication re-appear again

[msd3287]

Hi,
I have Sonoff TRVZB in 1.2.1 release too and I note that now, I'm quite sure it worked fine before, If I manually change the wished temperature on the valve itself, this change is not reflected on the associated versatile Thermostat. Same on the Versatile Thermostats of my daughter's house (different HA instance).
If I change the wished temperature on the V-th, it's well change on the valve.

[gbasile]

If I manually change the wished temperature on the valve itself, this change is not reflected on the associated versatile Thermostat.

I have the same issue as well

Update: false negative: wrong configuration on my side.

[jmcollin78]

Hello @gbasile , @msd3287 ,

Did you check the "Follow underlying temperature change" entity (in the VTherm device) ?

[gbasile]

I guess this is the setting you are talking about, right? In that case, yes

[jmcollin78]

No. I'm talking about this one:

[gbasile]

ah, I was not aware of that control in the service 😓
Of course IT DOES WORK when that option is set.

[jmcollin78]

It is a recent addition: https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.7.0

That is because you don't read the release notes 😉 (and it is badly documented that is true)

[msd3287]

[jmcollin78]

T'as un peu squatté le thread là. Celui-là c'était pour la liste qui ne s'affichait mal. Je vais le fermer dans qqes heures et ta question va disparaitre. Attend, je vais faire une mise à jour importante qui corrige pas mal de choses. Avec un peu de chance ça va marcher maintenant.

[msd3287]

Ok, merci :)
Désolé pour le squat mais j'avais l'impression qu'il s'agissait du même problème.