Installation method: Home Assistant OS
Core: 2026.2.1
Supervisor: 2026.02.2
Operating System: 17.0
Frontend: 20260128.6
Insteon Integration: Uploaded 15 Feb 2026 (How does one determine its version?)
First off, I did RTFM.
I set up and Insteon Scene (which functions differently than an HA scene)
Settings–>Devices & services–>Insteon–>[gear]–>(tab)Insteon Scenes–>Add Scene–>Named scene and added [switch.keypad_dimmer_4d_32_04_button_c]–>Save scene
Scene 20 now appears in scene list
I attempt to create a script
Settings–>Automations & scenes–>(tab)Scripts–>(+ Create Script)–>Create new script–>[three vertical dots]–>Edit in YAML
alias: Test Insteon Scene
description: ""
sequence:
- action: insteon.scene_on
group: 20
–>(Save)–>(enter name Test Insteon Scene)–>(Save)
Alas, an error message Message malformed: extra keys not allowed @ data[‘sequence’][0][‘group’]
Moving on …
It appears that Insteon devices are now lights and switches and work the same as any other light or switch. This is a good thing!
I ended up here because I was trying to find out how employ the double tap (fast on) and the hold which is used to dim or brighten a light. Looking at the
Settings–>Developer tools–>(tab)States
It appears that these attributes are not included.
I write in hopes that there is someone that knows what the Insteon integration is designed to do and would take the time to enlighten us.
No the action doesn’t work because the script was never saved because of the error.
After a couple of hours of search for a list of insteon. commands I came across this page with
This works
alias: Test Insteon Scene
description: ""
sequence:
- action: insteon.scene_on
data:
group: 20
I do not know if Insteon devices have always been lights and switches. An example would have been helpful.
Two years ago I noted a couple of other issues with the page, for example, the use of “Triggering” (to mean controlling) which lead to confusion. I used the link to report and suggest changes and submitted some example code. Just recently I got a notification that since there was no activity on the report it was deemed not worthy of changes and subsequently closed. Thus, I have no confidence that efforts to make improvements will bear fruit.
I’ve fixed a few things personally. Found a problem. Edited a few lines, submitted it, and in a month it was fixed.
If you are just suggesting changes, there is the additional burden besides proving there is a problem but then you need to get a persons time to do it.
I just finished deployment of my HA system including Insteon lighting. Some things I found:
Insteon Scene calls:
- service: insteon.scene_on
data:
group: 31
Action does not work for me but Service does. Action returned no errors, but also nothing happened. Service works great… I use a lot of Insteon scenes in automations
I migrated from another controller known for its complete feature support of Insteon PLM communications and those capabilities are not fully in the HA Insteon Integration yet. I know its a work in progress:
I can’t get double taps to work here, or fade up / down response from a switch
I have lamps that use a fade up/down scene from an automation before dusk, but the device setting for the lamps is on/off from an Insteon paddle. Because I brought the devices and scenes with me and they were already programmed, the fade/up down scene can be called from HA and works as expected, but I don’t know of a way to create new Fade up/down scenes using the Insteon Integration (that I know of)
Device default can be set to fade up/ down, but that doesn’t help me
Could make no sense out of the battery notifications for leak sensors on HA. It was my plan to move all Insteon sensors to Yolink and I did that
Looking at the git repo, a few things changed that are foundational to Insteon like the switch.py. I read the notes…it is related to switches but I’m not the best at deciphering git updates at 10,000’… eg where can the changes be felt?
Since I just finished a large deployment I’m skipping these recent updates till I can figure that out
