Integration management - Spook 👻 a scary powerful toolbox for Home Assistant.

Integrations in Home Assistant are the glue between your Home Assistant instance and the devices, services, and platforms you want to integrate with it. Spook enhances the core of Home Assistant by adding to control those integrations.

Actions¶

The following integration management actions are added to your Home Assistant instance:

Disable an integration¶

Disable a single instance of an integration by its config entry.

Screenshot of the Home Assistant disable config entry action in the developer tools.

Open your Home Assistant instance and show your actions developer tools with a specific action selected.

Action properties
Action	Disable an integration 👻
Action name	`homeassistant.disable_config_entry`
Action targets	No
Action response	No response
Spook's influence	Newly added action.
Developer tools	Try this action

Action data parameters
Attribute	Type	Required	Default / Example
`config_entry_id`	string \| list of strings	Yes	`dc23e666e6100f184e642a0ac345d3eb`

Finding the config entry ID

Not sure what the config_entry_id of your integration is?

Use this action in the developer tools, in the UI select the device you want to use and select the Go to YAML mode button. This will show you the config entry ID in the YAML code.

Example action in YAML

1
2
3
action: homeassistant.disable_config_entry
data:
  config_entry_id: "dc23e666e6100f184e642a0ac345d3eb"

Or multiple at once:

1
2
3
4
5
action: homeassistant.disable_config_entry
data:
  config_entry_id:
    - "dc23e666e6100f184e642a0ac345d3eb"
    - "df98a97c9341a0f184e642a0ac345d3b"

Enable an integration¶

Enable a single instance of an integration by its config entry.

Screenshot of the Home Assistant enable config entry action in the developer tools.

Action properties
Action	Enable an integration 👻
Action name	`homeassistant.enable_config_entry`
Action targets	No
Action response	No response
Spook's influence	Newly added action.
Developer tools	Try this action

Action data parameters
Attribute	Type	Required	Default / Example
`config_entry_id`	string \| list of strings	Yes	`dc23e666e6100f184e642a0ac345d3eb`

Finding the config entry ID

Not sure what the config_entry_id of your integration is?

Use this action in the developer tools, in the UI select the device you want to use and select the Go to YAML mode button. This will show you the config entry ID in the YAML code.

Example action in YAML

1
2
3
action: homeassistant.enable_config_entry
data:
  config_entry_id: "dc23e666e6100f184e642a0ac345d3eb"

Or multiple at once:

1
2
3
4
5
action: homeassistant.enable_config_entry
data:
  config_entry_id:
    - "dc23e666e6100f184e642a0ac345d3eb"
    - "df98a97c9341a0f184e642a0ac345d3b"

Disable polling for updates¶

Disable integration polling of a single integration instance by its config entry.

Some integrations frequently poll for updates. In some cases, it can be helpful to disable this temporarily. For example, in case you are not at home and want to stop polling on an integration that consumes a paid API.

Screenshot of the Home Assistant disable polling action in the developer tools.

Action properties
Action	Disable polling for updates 👻
Action name	`homeassistant.disable_polling`
Action targets	No
Action response	No response
Spook's influence	Newly added action.
Developer tools	Try this action

Action data parameters
Attribute	Type	Required	Default / Example
`config_entry_id`	string	Yes	`dc23e666e6100f184e642a0ac345d3eb`

Finding the config entry ID

Not sure what the config_entry_id of your integration is?

Use this action in the developer tools, in the UI select the device you want to use and select the Go to YAML mode button. This will show you the config entry ID in the YAML code.

Example action in YAML

1
2
3
action: homeassistant.disable_polling
data:
  config_entry_id: "dc23e666e6100f184e642a0ac345d3eb"

Enable polling for updates¶

Enable integration polling of a single integration instance by its config entry.

Some integrations frequently poll for updates. In some cases, it can be helpful to enable this just temporarily. For example, in case you are not at home and want to stop polling on an integration that consumes a paid API and want to turn it back on again when you are back.

Screenshot of the Home Assistant enable polling action in the developer tools.

Action properties
Action	Enable polling for updates 👻
Action name	`homeassistant.enable_polling`
Action targets	No
Action response	No response
Spook's influence	Newly added action.
Developer tools	Try this action

Action data parameters
Attribute	Type	Required	Default / Example
`config_entry_id`	string	Yes	`dc23e666e6100f184e642a0ac345d3eb`

Finding the config entry ID

Not sure what the config_entry_id of your integration is?

Use this action in the developer tools, in the UI select the device you want to use and select the Go to YAML mode button. This will show you the config entry ID in the YAML code.

Example action in YAML

1
2
3
action: homeassistant.enable_polling
data:
  config_entry_id: "dc23e666e6100f184e642a0ac345d3eb"

Ignore all discovered devices & services¶

When Home Assistant discovers new devices or services, it will show up on the integration dashboard. You can ignore them one by one, but This action will allow you to ignore all of them at once.

It also supports ignoring all discovered devices from a specific integration. For example, if you want to ignore all discovered devices from the bluetooth integration, you could do that periodically with an automation.

Action properties
Action	Ignore all currently discovered devices 👻
Action name	`homeassistant.ignore_all_discovered`
Action targets	No
Action response	No response
Spook's influence	Newly added action.
Developer tools	Try this action

Action data parameters
Attribute	Type	Required	Default / Example
`domain`	string	No	`bluetooth`

Example action in YAML

1
2
3
action: homeassistant.ignore_all_discovered
data:
  domain: "esphome"

Blueprints & tutorials¶

There are currently no known blueprints or tutorials for the enhancements Spook provides for these features. If you created one or stumbled upon one, please let us know in our discussion forums.

Features requests, ideas, and support¶

If you have an idea on how to further enhance this, for example, by adding a new action, entity, or repairs detection; feel free to let us know in our discussion forums.

Are you stuck using these new features? Or maybe you’ve run into a bug? Please check the page on where to go for help.