Bonjour,
Mon problème
Le trigger se déclenche.
Le choice qui est basé sur entity issu du trigger ne fonctionne pas.
Exemple, voici deux automatismes qui sont quasiment identiques:
alias: Ouverture Portail - USER1
description: ""
triggers:
- trigger: webhook
allowed_methods:
- GET
local_only: false
webhook_id: USER1@XXXXXXX
id: webhook
- trigger: mqtt
topic: JPI/sms/reception/3361111111
id: mqtt_sms
conditions: []
actions:
- choose:
- conditions:
- condition: trigger
id:
- webhook
sequence:
- action: script.turn_on
metadata: {}
data: {}
target:
entity_id:
- script.ouverture_portail_tempo
- conditions:
- condition: trigger
id:
- mqtt_sms
- condition: template
value_template: "{{ trigger.payload_json['number'] == phone_number }}"
- condition: template
value_template: "{{ trigger.payload_json['message'] == sms_password }}"
sequence:
- action: script.turn_on
metadata: {}
data: {}
target:
entity_id:
- script.ouverture_portail_tempo
- action: mqtt.publish
metadata: {}
data:
retain: false
topic: JPI/sms/envoi
payload: >-
{ "action": "sendSms", "number": "{{
trigger.payload_json['number'] }}", "message": "{{ welcome_msg |
random }}" }
mode: single
variables:
name: USER1
phone_number: "+3361111111"
sms_password: USER1
welcome_msg:
Le deuxième:
alias: Ouverture Portail - USER2
description: ""
triggers:
- trigger: webhook
allowed_methods:
- GET
local_only: false
webhook_id: USER2@XXXXXXXXXX
id: webhook
- trigger: mqtt
topic: JPI/sms/reception/33622222222
id: mqtt_sms
conditions: []
actions:
- choose:
- conditions:
- condition: trigger
id:
- webhook
sequence:
- action: script.turn_on
metadata: {}
data: {}
target:
entity_id:
- script.ouverture_portail_tempo
- action: mqtt.publish
metadata: {}
data:
retain: false
topic: JPI/sms/envoi
payload: >-
{ "action": "sendSms", "number": "{{ phone_number }}",
"message": "{{ welcome_msg | random }}" }
- action: notify.mobile_app_iphone_1
metadata: {}
data:
message: "{{ name }}"
title: Ouverture portail
- action: notify.mobile_app_iphone_2
metadata: {}
data:
message: "{{ name }}"
title: Ouverture portail
- conditions:
- condition: trigger
id:
- mqtt_sms
- condition: template
value_template: "{{ trigger.payload_json['number'] == phone_number }}"
- condition: template
value_template: "{{ trigger.payload_json['message'] == sms_password }}"
sequence:
- action: script.turn_on
metadata: {}
data: {}
target:
entity_id:
- script.ouverture_portail_tempo
- action: mqtt.publish
metadata: {}
data:
retain: false
topic: JPI/sms/envoi
payload: >-
{ "action": "sendSms", "number": "{{
trigger.payload_json['number'] }}", "message": "{{ welcome_msg |
random }}" }
- action: notify.mobile_app_iphone_1
metadata: {}
data:
message: "{{ name }}"
title: Ouverture portail
- action: notify.mobile_app_iphone_2
metadata: {}
data:
message: "{{ name }}"
title: Ouverture portail
mode: single
variables:
name: USER2
phone_number: "+33622222222"
sms_password: USER2
welcome_msg:
Et j’en ai une bonne dizaine du même genre.
Certains fonctionnent et d’autres non.
Je vois bien le déclenchement du trigger quand je fais des tests, mais après au moment du choice, ça échappe et fini l’automatisme.
Voici les historiques d’exécutions:
Pourquoi le choix ne se fait pas?
J’ai redémarré HA plusieurs fois.
Vu qu’il n’y avait pas d’évolution. J’ai mis à jour HA.
Mais cela ne fonctionne toujours pas. Pendant des mois, ça tournait comme une horloge.
Si quelqu’un à une idée.
Merci d’avance
Ma configuration
System Information
version | core-2026.2.2
– | –
installation_type | Home Assistant Container
dev | false
hassio | false
docker | true
container_arch | aarch64
user | root
virtualenv | false
python_version | 3.13.11
os_name | Linux
os_version | 6.12.47+rpt-rpi-2712
arch | aarch64
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 | 2767
Downloaded Repositories | 6
Home Assistant Cloud
logged_in | false
– | –
can_reach_cert_server | ok
can_reach_cloud_auth | ok
can_reach_cloud | ok
Dashboards
dashboards | 4
– | –
resources | 2
views | 7
mode | storage
Recorder
oldest_recorder_run | 6 février 2026 à 07:37
– | –
current_recorder_run | 23 février 2026 à 17:41
estimated_db_size | 2265.31 MiB
database_engine | mysql
database_version | 11.8.3