Versatile Thermostat over_climate - Souci sur l'application des consignes au sous-jacent

Bonjour à tous,
ante-scriptum : c’est ma 1ère demande d’aide, soyez indulgents :innocent:

Ce que je cherche à faire

J’ai une PAC Toshiba très mal régulée (intégrée dans HA) et je souhaite utiliser l’auto-régulation du versatile thermostat, ainsi que les présets (eco/etc… appliqué par scheduler) tout en conservant si possible les commandes directes à la PAC : telco & app mobile (WAF)

Pour la 1ère mise en service j’ai désactivé les fonctions intelligentes du Vtherm.
Je n’ai laissé que la détection de présence… et dans un 1er temps j’avais laissé actif « Thermostat Salon Follow underlying temp change » pour répondre a mon besoin de double commande.

Edit: j’avais oublié de préciser que l’intégration Toshiba c’est du Cloud

Mon problème

Sur certains changement de preset, la consigne ne passait pas toujours au « climate » sous-jacent et le Vtherm passait alors en mode « manuel/none » quelques secondes plus tard. Donc j’ai désactivé le « Follow underlying temp change » pour mieux comprendre.

Désormais, le climate sous-jacent suis la consigne du Vtherm + de 50% du temps mais certaines fois rien ne se passe. Lorsque cela arrive on note un « Error executing service: » dans le LOG

J’ai activé le Debug du log mais on en apprend pas plus. Tout les autres thermostats over_switch vont bien et le over_climate montre le même contenu d’erreur avec ou sans le Debug

Sur le Git j’ai l’impression qu’il y a une issue du même type, la #996 avec un log très proche
Mais pour ma part le PB n’est pas systématique.

LE LOG de ce jour 14h, passage en confort
2025-03-28 13:59:20.931 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 13:59:20.931 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 13:59:20.931 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 13:59:20.931 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:00:00.002 ERROR (MainThread) [homeassistant.core] Error executing service: <ServiceCall climate.set_temperature (c:01JQEDD0415QPT3SAXMCAJTYDP): entity_id=['climate.pac_salon'], temperature=18.5>
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/core.py", line 2814, in _run_service_call_catch_exceptions
    await coro_or_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 2837, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1007, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
        hass, entity, func, data, call.context
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1079, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/climate/__init__.py", line 954, in async_service_temperature_set
    await entity.async_set_temperature(**kwargs)
  File "/config/custom_components/toshiba_ac/climate.py", line 120, in async_set_temperature
    await self._device.set_ac_temperature(set_temperature)
  File "/usr/local/lib/python3.13/site-packages/toshiba_ac/device/__init__.py", line 275, in set_ac_temperature
    state.ac_temperature = val
    ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/toshiba_ac/device/fcu_state.py", line 407, in ac_temperature
    self._ac_temperature = ToshibaAcFcuState.AcTemperature.to_raw(val)
                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/local/lib/python3.13/site-packages/toshiba_ac/device/fcu_state.py", line 50, in to_raw
    return temp_to_raw[temperature]
           ~~~~~~~~~~~^^^^^^^^^^^^^
KeyError: 18.5
2025-03-28 14:00:00.147 WARNING (MainThread) [homeassistant.components.zwave_js.services] This service is deprecated in favor of the ping button entity. Service calls will still work for now but the service will be removed in a future release
2025-03-28 14:02:22.304 WARNING (MainThread) [custom_components.unraid.api.disk_state] Both SMART and hdparm failed to determine state for jupiter (smart_exit=2, hdparm_output=''), assuming ACTIVE
2025-03-28 14:02:22.350 WARNING (MainThread) [custom_components.unraid.api.disk_state] Both SMART and hdparm failed to determine state for jupiter (smart_exit=2, hdparm_output=''), assuming ACTIVE
2025-03-28 14:02:22.924 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:02:22.924 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:02:22.924 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:02:22.925 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:02:22.926 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:02:22.926 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:02:22.926 ERROR (MainThread) [custom_components.unraid.unraid] Command failed: open failed
2025-03-28 14:04:34.385 ERROR (MainThread) [toshiba_ac.device] State reload failed: 

Cela pourrait-il venir des paramètres que j’ai choisis ?
ou du climate sous-jacent ? (en commande directe il a l’air de répondre 100% du temps)

version de l’intégration 7.2.7

Ma config du Vtherm - (copie de Etat à 15h14)
hvac_modes: off, auto, cool, heat, dry, fan_only
min_temp: 12
max_temp: 30
target_temp_step: 0.5
fan_modes: Auto, Quiet, Low, Medium Low, Medium, Medium High, High
preset_modes: none, frost, eco, comfort, boost
swing_modes: Off, Swing Vertical, Swing Horizontal, Swing Vertical And Horizontal, Fixed 1, Fixed 2, Fixed 3, Fixed 4, Fixed 5
current_temperature: 21.2
temperature: 19
fan_mode: Auto
hvac_action: heating
preset_mode: comfort
swing_mode: Swing Horizontal
is_on: true
hvac_mode: heat
type: null
is_controlled_by_central_mode: true
last_central_mode: null
frost_temp: 13
eco_temp: 16
boost_temp: 21
comfort_temp: 19
frost_away_temp: 13
eco_away_temp: 16
boost_away_temp: 17
comfort_away_temp: 16
target_temperature_step: 0.5
ext_current_temperature: 14.405
ac_mode: true
saved_preset_mode: comfort
saved_target_temp: 16
saved_hvac_mode: null
last_temperature_datetime: 2025-03-28T14:00:00.004232+01:00
last_ext_temperature_datetime: 2025-03-28T15:07:25.895800+01:00
minimal_activation_delay_sec: 10
minimal_deactivation_delay_sec: 0
total_energy: 0
last_update_datetime: 2025-03-28T15:09:01.162253+01:00
timezone: Europe/Paris
temperature_unit: °C
is_device_active: true
device_actives: climate.pac_salon
nb_device_actives: 1
ema_temp: 21.16
is_used_by_central_boiler: false
temperature_slope: 0
hvac_off_reason: null
max_on_percent: null
have_valve_regulation: false
last_change_time_from_vtherm: 2025-03-27T15:19:01.051208+01:00
presence_sensor_entity_id: binary_sensor.thermostat_presence_maison
presence_state: on
is_presence_configured: true
power_sensor_entity_id: sensor.conso_maison_ccasn
max_power_sensor_entity_id: input_number.conso_maison_max
overpowering_state: unavailable
is_power_configured: false
device_power: 2050
power_temp: 16
current_power: 862
current_max_power: 8000
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: null
window_delay_sec: 30
window_off_delay_sec: 15
is_window_configured: false
is_window_auto_configured: false
window_auto_open_threshold: 3
window_auto_close_threshold: 0
window_auto_max_duration: 30
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.pac_salon
is_regulated: true
regulated_target_temperature: 18.5
auto_regulation_mode: auto_regulation_light
regulation_accumulated_error: -10
auto_fan_mode: auto_fan_medium
current_auto_fan_mode: auto_fan_medium
auto_activated_fan_mode: null
auto_deactivated_fan_mode: null
auto_regulation_use_device_temp: false
follow_underlying_temp_change: false
friendly_name: Thermostat Salon
supported_features: 441

Ma configuration


System Information

Résumé
version core-2025.3.4
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.13.2
os_name Linux
os_version 6.12.18-haos
arch x86_64
timezone Europe/Paris
config_dir /config
Home Assistant Community Store
GitHub API ok
GitHub Content ok
GitHub Web ok
HACS Data ok
GitHub API Calls Remaining 5000
Installed Version 2.0.5
Stage running
Available Repositories 1678
Downloaded Repositories 12
Home Assistant Cloud
logged_in false
can_reach_cert_server ok
can_reach_cloud_auth ok
can_reach_cloud ok
Home Assistant Supervisor
host_os Home Assistant OS 15.0
update_channel stable
supervisor_version supervisor-2025.03.3
agent_version 1.7.2
docker_version 28.0.1
disk_total 30.8 GB
disk_used 14.9 GB
healthy true
supported true
host_connectivity true
supervisor_connectivity true
ntp_synchronized true
virtualization kvm
board ova
supervisor_api ok
version_api ok
installed_addons Samba share (12.5.0), Studio Code Server (5.18.3), Terminal & SSH (9.16.0), ESPHome Device Builder (2025.3.2), Get HACS (1.3.1)
Dashboards
dashboards 5
resources 5
views 13
mode storage
Network Configuration
adapters lo (disabled), enp1s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), vetheb31a39 (disabled), veth0faf6ec (disabled), veth5a86341 (disabled), veth96f9c9c (disabled), veth6e2bfa9 (disabled), vethaadaadd (disabled), vethd0399dd (disabled), veth2bb599d (disabled)
ipv4_addresses lo (127.0.0.1/8), enp1s0 (192.168.0.167/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vetheb31a39 (), veth0faf6ec (), veth5a86341 (), veth96f9c9c (), veth6e2bfa9 (), vethaadaadd (), vethd0399dd (), veth2bb599d ()
ipv6_addresses lo (::1/128), enp1s0 (fe80::82bc:d67a:623f:36a6/64), docker0 (fe80::4454:5eff:fefc:793/64), hassio (fe80::f41e:2eff:feae:c734/64), vetheb31a39 (fe80::d040:b6ff:fe31:480c/64), veth0faf6ec (fe80::70de:5bff:fe25:2092/64), veth5a86341 (fe80::88f0:feff:fe3e:6e65/64), veth96f9c9c (fe80::b829:4bff:fe96:a2c6/64), veth6e2bfa9 (fe80::51:45ff:fe7f:d0dc/64), vethaadaadd (fe80::9c8a:e3ff:fe98:7fa2/64), vethd0399dd (fe80::c48a:7aff:fea4:2a15/64), veth2bb599d (fe80::4054:dbff:fe06:9905/64)
announce_addresses 192.168.0.167, fe80::82bc:d67a:623f:36a6
Recorder
oldest_recorder_run 15 mars 2025 à 20:17
current_recorder_run 27 mars 2025 à 14:59
estimated_db_size 1012.91 MiB
database_engine sqlite
database_version 3.48.0
Xiaomi Miot Auto
component_version 1.0.15
can_reach_server ok
can_reach_spec ok
logged_accounts 1
total_devices 1
` ___

Hello,
Problème en éliminé à défaut d’être élucidé/réglé.

J’ai supprimé le climate Toshiba basé sur le cloud. J’ai remplacé le module wifi du fabricant par un module esphome pour une commande locale de la clim.

Plus de « Error executing service: ».
désormais les commandes du vtherm émises ne génèrent plus d’erreurs.

J’ai d’autres soucis (liés au « Follow underlying temp change ») mais chaque chose en son temps :innocent:

Ce sujet a été automatiquement fermé après 2 jours. Aucune réponse n’est permise dorénavant.