This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| indigo_2025.1_documentation:action_group_class [2025/10/22 15:17] – [Execute] jay | indigo_2025.1_documentation:action_group_class [2026/02/19 17:54] (current) – [Move To Folder] davel17 |
|---|
| |direct parameter| Yes | integer |id or instance of the action group to execute| | |direct parameter| Yes | integer |id or instance of the action group to execute| |
| |event_data| No | dict |a dictionary instance that will get passed to all actions in the action group for processing| | |event_data| No | dict |a dictionary instance that will get passed to all actions in the action group for processing| |
| | |
| | A note on ''event_data'' - Indigo will automatically add a ''source'' key to your dictionary to represent where the action execution came from: |
| | |
| | * "server" if it's something generated from the server itself (schedule execution, built-in trigger, etc) |
| | * "python" if it's something that comes through IPH that doesn't already have a source attached (scripts, plugins) |
| | * "api-http" if it came from the HTTP API and there wasn't already an included "source" |
| | * "api-websocket" if it came from the websocket API and there wasn't already an included "source" |
| | |
| | However, if you include a ''source'' key in your ''event_data'', we will not overwrite it, we'll just pass through whatever your value is. |
| | === Get Dependencies === |
| | |
| | Use this command to retrieve all the Indigo objects dependent on the action group. The command will return an //''indigo.Dict''// containing all the dependencies. |
| | |
| | ^ Command Syntax Examples ^ |
| | |<code>indigo.actionGroup.getDependencies(123)</code>| |
| | |
| | ^ Parameters ^^^^ |
| | ^ Parameter ^ Required ^ Type ^ Description ^ |
| | |direct parameter| Yes | integer |id or instance of the action group| |
| | |
| === Move To Folder === | === Move To Folder === |
| |