From 4f344e7b166ec72d88ac683f837b457c42722bfd Mon Sep 17 00:00:00 2001 From: John Ogle Date: Sat, 20 Dec 2025 15:24:24 -0800 Subject: [PATCH] Fix inovelli_mode_cycling blueprint trigger for event entities Correct the trigger mechanism to match how Home Assistant event entities actually work. Event entities trigger on state changes and expose the actual event type as an attribute, not as event_data. Changes: - Replace platform:event trigger with platform:state - Add condition to check event_type attribute for 'config_single' - Remove incorrect event_data and state_changed event_type usage This matches the working pattern used in production automations and ensures the blueprint triggers correctly when the config button is pressed on Inovelli switches. --- blueprints/automation/inovelli_mode_cycling.yaml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/blueprints/automation/inovelli_mode_cycling.yaml b/blueprints/automation/inovelli_mode_cycling.yaml index 01e4cf4..f012186 100644 --- a/blueprints/automation/inovelli_mode_cycling.yaml +++ b/blueprints/automation/inovelli_mode_cycling.yaml @@ -53,11 +53,14 @@ mode: single max_exceeded: silent trigger: - - platform: event - event_type: state_changed - event_data: - entity_id: !input switch_action_event - new_state.state: "config_single" + - platform: state + entity_id: !input switch_action_event + +condition: + - condition: state + entity_id: !input switch_action_event + attribute: event_type + state: "config_single" action: - variables: