Bonsoir a tous,
je galere depuis 2 jours pour active le heat de ma vanne connecter car celle-ci reste en auto.
voici la config de ma vanne
hvac_modes:
- 'off'
- heat
- auto
min_temp: 5
max_temp: 30
target_temp_step: 0.5
preset_modes:
- none
- away
current_temperature: 21.9
temperature: 24
preset_mode: none
anti_scaling: 'ON'
away_mode: 'OFF'
battery_low: false
child_lock: UNLOCK
current_heating_setpoint: 24
frost_detection: 'ON'
linkquality: 158
local_temperature: 21.9
local_temperature_calibration: 0
system_mode: auto
window_detection: 'ON'
friendly_name: '0x804b50fffe4467bb'
supported_features: 17
J’aimerais avoir une automatisation qui le dit que si j’ai ma ‹ current temperature › qui est inferieur a ma ‹ temperature › ou ‹ current_heating_setpoint › j’appele le service ‹ climate.set_hvac_mode › en je passe en mode ‹ heat ›.
j’ai fais ca mais il doit me manquer un truc
alias: Nouvelle automatisation
description: ''
trigger:
- platform: template
value_template: |-
{{ (state_attr('climate.0x804b50fffe4467bb', 'temperature') >
state_attr('climate.0x804b50fffe4467bb', 'current_temperature')) }}
condition: []
action:
- service: climate.set_hvac_mode
target:
entity_id: climate.0x804b50fffe4467bb
data:
hvac_mode: heat
mode: single
Je ne suis pas expext dans les template
version
core-2021.4.6
installation_type
Home Assistant Supervised
dev
false
hassio
true
docker
true
virtualenv
false
python_version
3.8.7
os_name
Linux
os_version
4.19.0-16-amd64
arch
x86_64
timezone
Europe/Paris
Home Assistant Community Store
GitHub API
ok
Github API Calls Remaining
4358
Installed Version
1.11.3
Stage
running
Available Repositories
781
Installed Repositories
53
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
Debian GNU/Linux 10 (buster)
update_channel
beta
supervisor_version
supervisor-2021.04.1
docker_version
20.10.5
disk_total
113.6 GB
disk_used
11.4 GB
healthy
true
supported
true
supervisor_api
ok
version_api
ok
installed_addons
Samba share (9.3.1), Duck DNS (1.12.5), MQTT Server & Web client (1.2.0), File editor (5.2.0), Terminal & SSH (9.1.0), ESPHome (1.16.2), Spotify Connect (0.8.2), Grafana (6.3.2), Portainer (1.4.0), Node-RED (9.0.0), Tydom2MQTT - Beta (release_1.01), Zigbee2mqtt (1.18.2-1), Zigbee2mqtt Edge (edge), InfluxDB (4.0.6)
Lovelace
dashboards
1
resources
36
views
13
mode
storage
Spotify
api_endpoint_reachable
ok
Qu’est ce qui ne va pas ?
L’automatisation se déclenche t’elle ?
Ou est-ce l’action qui ne fonctionne pas ?
Le service que tu appelles fonctionne t’il dans les Outils de développement → Onglet SERVICES ?
nonome1:
{{ (state_attr('climate.
Salut Clemalex,
j’ai bien l’automatisation qui se lance. j’ai mon mode confort qui se mets a la temperature cible ‹ 23° › et le heat qui s’enclenche, puis apres il se remets a 20° et mode auto 2s apres et j’ai aucun parametre a 20° dans ma config
C’est comme ci ma vanne avait des parametres en memoires
La vanne a un programme deja en memoire en auto 16° la nuit, 21° sur 2 tranche de la journée et 19 pendant les creux. Donc je vais commander un hub zigbee tuya et je vais regarder le programme. je vais voir si je peux l’annuler.
J’ai donc creer 2 input booleen confort 21° et nuit 19°.
2 automatisations pour piloter les vannes et la chaudieres.
2 schedule avec l’addons hacs ( nuit ou absent et en chauffes
ca fonctionne mais c’est une usine
voici les codes :
auto confort
alias: auto vanne invite confort
description: ''
trigger:
- platform: template
value_template: |-
{{ (state_attr('climate.0x804b50fffe4467bb', 'current_heating_setpoint') <
state_attr('climate.0x804b50fffe4467bb', 'current_temperature')) }}
condition:
- condition: and
conditions:
- condition: state
entity_id: input_boolean.confort
state: 'on'
- condition: state
entity_id: input_boolean.nuit
state: 'off'
- condition: or
conditions:
- condition: state
entity_id: climate.netatmo_thermostat_generale
attribute: hvac_modes
state: idle
- condition: state
entity_id: climate.netatmo_thermostat_generale
state: auto
attribute: hvac_modes
action:
- service: climate.set_hvac_mode
data:
hvac_mode: auto
target:
entity_id:
- climate.netatmo_thermostat_generale
- service: climate.set_hvac_mode
data:
hvac_mode: 'off'
target:
entity_id: climate.0x804b50fffe4467bb
- service: automation.turn_off
target:
entity_id: automation.auto_vanne_invite_dupliquer
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
- service: input_boolean.turn_off
target:
entity_id: input_boolean.confort
- delay:
hours: 0
minutes: 0
seconds: 3
milliseconds: 0
- service: input_boolean.turn_on
target:
entity_id: input_boolean.confort
mode: single
et auto nuit
alias: auto vanne invite nuit
description: ''
trigger:
- platform: template
value_template: |-
{{ (state_attr('climate.0x804b50fffe4467bb', 'current_heating_setpoint') <
state_attr('climate.0x804b50fffe4467bb', 'current_temperature')) }}
condition:
- condition: and
conditions:
- condition: state
entity_id: input_boolean.confort
state: 'off'
- condition: state
entity_id: input_boolean.nuit
state: 'on'
- condition: or
conditions:
- condition: state
entity_id: climate.netatmo_thermostat_generale
attribute: hvac_modes
state: idle
- condition: state
entity_id: climate.netatmo_thermostat_generale
state: auto
attribute: hvac_modes
action:
- service: climate.set_hvac_mode
data:
hvac_mode: auto
target:
entity_id:
- climate.netatmo_thermostat_generale
- service: climate.set_hvac_mode
data:
hvac_mode: 'off'
target:
entity_id: climate.0x804b50fffe4467bb
- delay:
hours: 0
minutes: 0
seconds: 5
milliseconds: 0
- service: input_boolean.turn_off
target:
entity_id: input_boolean.nuit
- delay:
hours: 0
minutes: 0
seconds: 3
milliseconds: 0
- service: input_boolean.turn_on
target:
entity_id: input_boolean.nuit
mode: single
