#blueprint input selector condition: How does it work? "Stopped because of unknown reason"

1 messages · Page 1 of 1 (latest)

light mist
#

I've recently discovered condition-selectors and I'm trying to replace template-selectors.
The problem starts when trying to figure out why it isn't working: Stopped because of unknown reason at February 21, 2025 at 14:26:54 (runtime: 0.00 seconds)

My example:
'''
blueprint:
input:
enabler:
name: Enabler
default: []
selector:
condition:

variables:
enablers: !input enabler
enabler: "{{ enablers | select | list }}"
is_enabled: "{{ (enablers | count == 0) or (enabler | count > 0) }}"
trigger:

  • platform: template
    value_template: "{{ is_enabled }}"
    '''

how can I figure out what is going wrong? HA is not telling me anything useful.

reef mason
#

a condition selector allows you the user of the blueprint to input a condition. This can be any condition, so a state condition, or template condition or whatever.
The output of that selector will be a list of conditions, which can be used in the automation

Example

#
blueprint:
  input:
    enabler:
      name: Enabler
      default: []
      selector:
        condition:

conditions: !input enabler
triggers:
  - trigger: state
    entity_id: input_boolean.test
light mist
reef mason
#

You can't trigger from it, there is a trigger selector for that

light mist
#

For now I have doubled the mechanism: enabler_trigger which is a template simply containing all states and enalber_condition which does the complex conditions. I guess I could reduce it down to a list of entities that should be checked.