Has anyone succeeded in working with response_variables?

[petro]

No, this 100% works if you keep it within the proper scope. I’m using it. Whatever you’re doing is not correct. Here’s a full example:

  - variables:
      calendar: calendar.xxx
  - service: calendar.get_events
    data:
      start_date_time: "{{ today_at() }}"
      end_date_time: "{{ today_at().replace(year=now().year + 2, day=1, month=1) }}"
    target:
      entity_id: "{{ calendar }}"
    response_variable: raw_events
  - variables:
      gathered: >
        {{ {'events': raw_events[calendar].events} }}

So please post your code. I’ll help you fix it.

EDIT: If you’re referring to this post:

Define a different response_variable in conditionals doesn't work

I have a called script that may stop or continue at different points, depending on some conditions, and return some information to the calling script whenever it stops, using the response_variable. But the problem is that if the stop command is within a conditional if, the calling script doesn’t get the response_variable, although it works perfectly when the stop command is on the the first level, not within a conditional. I know it sounds like and XY problem, but I really want to understand th…

If statements are a nested items. It won’t work with if statements, hence why you have to do…

@petro

  - variables:
      limit: >
        {% if ... %}
          {{ {'value': 1200 } }}
        {% else %}
          {{ ... }}
        {% endif }}