-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
Closed
Labels
Description
The problem
When using the calendar.get_events action i'm unable to use a response_variable. The automation goal is to get my events in a form that ESPhome can ingest them
I've also tried a few example of automations from the forums where people have marked it as solved and the same errors occur
What version of Home Assistant Core has the issue?
core-2025.3.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
alias: Fetch Calendar Events
description: ""
triggers:
- minutes: /10
trigger: time_pattern
actions:
- target:
entity_id: calendar.house
data:
duration: "168:00:00"
response_variable: events
action: calendar.get_events
- target:
entity_id: input_text.calendar_events
data:
value: "{{ events | to_json }}"
action: input_text.set_value
Anything in the logs that might be useful for us?
HA Logs:
2025-03-10 19:11:21.508 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Invalid data for call_service at pos 1: Script does not support 'response_variable' for service 'response_variable' which does not support response data.
2025-03-10 19:11:21.508 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [131120586673600] Error handling message: Script does not support 'response_variable' for service 'response_variable' which does not support response data.. Got {'type': 'execute_script', 'sequence': [{'action': 'calendar.get_events', 'data': {'duration': {'hours': 7, 'minutes': 0, 'seconds': 0}}, 'target': {'entity_id': ['calendar.house']}, 'response_variable': 'test'}], 'id': 154} (invalid_format) Jonny from 10.69.69.8 (Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:136.0) Gecko/20100101 Firefox/136.0)
Additional information
No response