From 4f2dae4cc6b3833d09c684a6a12e6b39559509a4 Mon Sep 17 00:00:00 2001 From: OldSurferDude Date: Thu, 30 Apr 2026 20:32:09 -0700 Subject: [PATCH 1/2] Update section titles and descriptions for clarity Changed "Triggering" to "Controlling" where appropriate (caused confusion) Example did not work, missing line " data: " and properly indented the "group" line --- source/_integrations/insteon.markdown | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index 5240b4b048d9..b333300df842 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -80,7 +80,7 @@ In order for any two Insteon devices to talk with one another, they must be link ### Managing Insteon scenes -Insteon scenes can be created, changed or deleted using the **Scenes** tab of the [Insteon configuration panel](#insteon-configuration-panel). To trigger an Insteon scene see [Triggering Insteon Scenes](#triggering-insteon-scenes) below. +Insteon scenes can be created, changed or deleted using the **Scenes** tab of the [Insteon configuration panel](#insteon-configuration-panel). To trigger an Insteon scene see [Controlling Insteon Scenes](#controlling-insteon-scenes) below. ### Device properties @@ -120,9 +120,9 @@ Editing a device's All-Link Database can cause the device to become unresponsive - **Configure device overrides**: Add or remove device overrides. See [Device overrides](#device-overrides) below. - **Delete device**: Delete an Insteon device from the network using the device's Insteon address. -## Triggering Insteon scenes +## Controlling Insteon scenes -Triggering an Insteon scene on or off is done via automations. Two actions are provided to support this feature: +Controlling an Insteon scene on or off is done via automations. Two actions are provided to support this feature: - **insteon.scene_on** - **group**: (required) The Insteon scene number to trigger. @@ -131,11 +131,12 @@ Triggering an Insteon scene on or off is done via automations. Two actions are p ```yaml automation: - # Trigger an Insteon scene 25 + # Control an Insteon scene 25 - alias: "Turn on scene 25" actions: - action: insteon.scene_on - group: 25 + data: + group: 25 ``` ## Events and Mini-Remotes From 1fc27e13c2d24377a5b2b10d26784fb64de1befd Mon Sep 17 00:00:00 2001 From: OldSurferDude Date: Thu, 30 Apr 2026 22:14:38 -0700 Subject: [PATCH 2/2] Update source/_integrations/insteon.markdown Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- source/_integrations/insteon.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/insteon.markdown b/source/_integrations/insteon.markdown index b333300df842..2825dae99c0f 100644 --- a/source/_integrations/insteon.markdown +++ b/source/_integrations/insteon.markdown @@ -80,7 +80,7 @@ In order for any two Insteon devices to talk with one another, they must be link ### Managing Insteon scenes -Insteon scenes can be created, changed or deleted using the **Scenes** tab of the [Insteon configuration panel](#insteon-configuration-panel). To trigger an Insteon scene see [Controlling Insteon Scenes](#controlling-insteon-scenes) below. +Insteon scenes can be created, changed, or deleted using the **Scenes** tab of the [Insteon configuration panel](#insteon-configuration-panel). To control an Insteon scene, see [Controlling Insteon scenes](#controlling-insteon-scenes) below. ### Device properties