There is another automation I have added and that shows up in the GUI. I also tried to add this in the GUI but was getting errors having to do with “group”.
When I restart my HA server I see in the logs :
"Log Details (ERROR)
Logger: homeassistant.config
Source: config.py:410
First occurred: 8:56:17 PM (1 occurrences)
Last logged: 8:56:17 PM
Invalid config for [automation]: [group] is an invalid option for [automation]. Check: automation->action->0->group. (See /config/configuration.yaml, line 9)."
Here is the scene as it is in automations.yaml
- id: trigger_scene_55_on
alias: Turn on scene 55
action:
- service: insteon.scene_on
group: 55
This is the part of my configuration.yaml that I believe the log is referring to:
Thank you for this, and I was able to get the automation working. Thanks for pointing me in the right direction.
For anyone else trying to work with Insteon scenes I am finding that it is much easier to trigger the scenes in node-red. For some reason I thought the HA automation set up was a prerequisite to using the scenes in node-red.
I am sure many people prefer to use the automations.yaml but for a noob like me setting it up to use was much easier in node-red and then -
call service: service: insteon.scene_on and entering the group in the payload.
I rebuilt all insteon scenes using HA groups. Although the performance is a built slower, Insteon scenes are a pain
I have many multi button insteon controllers I have had to essentially throw away because they “remember” what they controlled before and never take new programming.
If you still stick with Insteon to create and manage groups, be sure to use iOS and the Insteon app. The Android app does not fully update switches. I went through the process of removing/changing ramp rates recently and nothing I did would take. Eventually after reading all the Insteon forums did I find this out.
I had to redo everything with iOS and magically it worked.
Domain: switch
Service: turn_off or turn_on
Entity Id: switch.scene_1 (pick your scene here)
Assuming you are integrating with the Insteon controller-
call service: service: insteon.scene_on and entering the group in the payload.
super easy this way
edit- I believe this changed since my first post a year ago but is working the way I described. Just confirmed in nodered. To the user above- factory resetting Insteon devices fixes all of those problems. I would not use groups at all. Insteon scenes are native and function without a controller and instantaneously.
I have 180 Insteon devices and have been using them for 15 years. Use the native functionality and if you have any number of devices do not use the Insteon app. Properly control them with an ISY + PLM integrated with HA.
To clarify, I am using the 2245 HUB, and have many device to device links, but I have a few Insteon scenes set up via the android app for testing with HASS. I am trying to find a way to get Home assistance to treat the Insteon scenes as an entity, so I can use one switch in lovelace to turn the insteon scenes on and off. I.E. so all keypad linc buttons and 3 ways switches reflect the proper state of the load being controlled.
My HA skills are less than my ISY and nodered skills so I am sure there is a more elegant way to do it in HA the what follows.
Just using HA you could create a binary sensor based on the scene. You could use a Template Switch - Home Assistant that reflects the status of the scene.
Then follow this to have a switch in lovelace that shows the status:
Would you be willing to buy a used ISY on ebay? The ISY natively out of the box presents scenes as switches in HA. Probably $100. If you have many insteon devices the ISY will blow you away compared to the insteon hub.
Are you able to run nodered? You could have a flow where the scene creates a switch entity. You could have that switch entity in lovelace. That switch would then toggle the automation (scene).
I’m lazy and would go the ISY route for all of its other benefits.
Certainly you can execute the scene, but it likely will not update in a two way fashion the status of your scene controllers. That should be expected though. Say I have a 6 button and use it to turn on three lights. If I go to those switches individually and turn them on, the scene button is out of sync and does not light. Pushing it will light the button an send the on, but they are already on. Introducing a third way to control them is not going to change that.
To the poster above me- I tested this and it does work. The behavior you describe means the devices are not cross-linked with each other. You can have any light in any scene control the keypad button or the entire scene.
This may not be worth it to you but this works for me. I use an ISY which can but purchased on ebay with a PLM serial modem (~$100). You may not be willing to do that but it works.
In HA my Insteon scenes are switch entities. I can control the scene off and on. If I control the scene in HA, the keypad button reflects the change. If I control it at the keypad, HA shows the correct status.
I doubt you can do this with the Insteon hub. If you use the ISY this will work. It directly integrates in HA.
That could be true. I use to have an ISY but it went bad and I did not want to shell out money for another. That said, I use HA most exclusively now. No desire to try and make them all play together and rarely touch 6 button controllers.
Sorry to revive this moderately zombie thread, but wanted to see how folks get the Scene ID number. I found an unanswered reddit question, but did find any answers. The insteon iOS app seems to allow you to find the Device ids by navigating to advanced settings of the device, but no such advanced setting seems to exist for Scenes.
Do you have access to an Android device? The old app shows the group number. If you don’t you could create a temporary login and use someone else’s device. I would do it if you want.
I could not find the group number in the “new” app.
Yes! That totally worked. I installed the Android app on an old tablet (I think it was an old version as I got a warning to update it) and it showed the scene id under “edit this” on the scenes tab. Thanks so much
Well I guess I celebrated too early. I was able to get the scene IDs. But calling it from the developer tools Service call or adding to an automation doesn’t trigger the scene. The latest UI has this nice interface where you just put the slider on the group number, so I don’t imagine it’s a syntax error. Here’s the Automation yaml entry
id: ‘1606013374243’
alias: Turn On Lights at Dusk
description: ‘’
trigger:
platform: sun
event: sunset
offset: -01:00:00
condition: []
action:
service: insteon.scene_on
data:
group: 20
mode: single
Any ideas how to debug this? The scene triggers both via the app and via Alexa.