Oh, sorry, I though you were talking about a KPL device type but I now see we are talking about a 2477D.
My answer is still the same, however. Sorry for the confusion
I “linked” it again after factory reset. I went to the Insteon Panel and clicked on the plus to add to the “all links” database. I adjusted the brightness of the light and the pressed the set button (not a long press, just single press and got a beep). After maybe a minute, the add dialog said it was ok.
Now when I select the hub and look at the links database, I see the new device is there. It shows an “18” and “Controller” and has the correct address and device type.
But it doesn’t show up in Devices or Entities. Next idea?
… time passes …
I did a “load from device” while looking at the hub device. I sorted the device numbers. I see MULTIPLES for the address of my switch. I think that is not a good thing?
Little off topic (awesome work on the panel teharris1 and congrats on having it merged!) but catching up on some old posts and saw this question. Yes, someone has done RF sniffing and mostly reverse engineered the protocol. ‘evilpete’ did it about 7 years ago and presented a paper on it at DefCon. You can see his paper here:
and here is his code base:
https://github.com/evilpete/insteonrf
I tried to follow his steps and managed to get it sorta working a few years back. I wrote up the steps I took here using a software defined radio:
Looks like rfcat moved to GitHub but it should be enough for someone to go on if they want to run with it. The actual over the air protocol seems to look a lot like the serial PLM communication.
Edit: it also looks like he’s since added Insteon decoding to the rtl_433 project, detailed here:
https://forum.universal-devices.com/topic/31253-rtl_433-now-decodes-insteon-wireless-protocol/
I am LOSING my mind when it comes to these scenes.
- linked everything for my scene on insteon tab
- Added this to a script
- added script to scene(Just like teharris posted)
When I press the button in home assistant it works perfect. Everything turns on simultaneously.
After running a discover in Alexa, to get the new UNIQUE(never before used)scene name to pop up, when ask Alexa to turn on the scene, the lights turn on 1 by 1 popcorn effect
How for the love of GOD is this possible? Moments away from throwing in the towel and ripping all insteon out of my house. Any help would be very appreciated.
For those that may be interested, I can share code I put in Lovelace for adding/removing things in an Insteon group. GUI looks like below. I am sure that the general Insteon Control Panel will grow to include many of these things, but I use this for now.
Top item is an input select populated with the Insteon devices (NOTE: it uses the friendly names to make things a bit easier).
Next item is the selected item in the input select. You can set on/off or drill in and set brightness. You can also do that at the physical switch if you like. Of course you only need to do this if adding to a scene.
Next item is selecting the scene number. Of course it would be great here for many things that are well beyond me, like a list of existing scene numbers with friendly names, or a separate display of all devices in a particular scene. I could get those by parsing the insteon_devices.json but that is a bit beyond me at the moment.
Next item you can add or delete the device from a scene. Of course once selected you need to go to that device and push the link button. Again would be great to display something to show the link is done like it does in the Insteon Control Panel.
Last item is testing … you can execute scene_on and scene_off to make sure everything works for you.
1 Like
I just created my first scene (100) to test this. Followed steps 1 & 2 (not 3) in HOW TO: Trigger an Insteon Scene using Alexa or Google Assistant, modified my smart_home section to include the new scripts, discovered new scenes in Alexa, created 2 routines Living Room On & Living Room Off and when Alexa ran the routines, the devices I linked to scene 100 turned on/off simultaneously without a popcorn effect.
I then tried step #3 to create HA scenes to activate those new scripts but when I run the HA scenes nothing happens…
You are using Nabu Casa? If you go to:
Settings → Home Assistant Cloud → Under Alexa click “Manage Entities”
What do you see? Or more importantly, you go to “Manage Domains” then what is checked?
If you go to your Alexa App, what scenes are listed?
It is likely that you did not discover any newly created scenes you made and somehow it has old ones
He did mention he created a brand new scene name…
I presume you edited the Alexa routine deleting the old scene name and adding the new UNIQUE scene name??
If you look in the Nabu Casa screens you can see it can execute a script, you really do not need a scene I do not believe. Like I have scripts like “Mute Music” which will mute every device. In Nabu Casa I expose scripts to Alexa and say “Alexa, Mute Music” which executes the script directly (no scene) and works perfectly.
That is correct…an HA scene is not required; HA scripts show as scenes in Alexa and work just fine.
2 Likes
Uh, yes please. That looks great.
Yes please!
I tried my hand at it - you need to create an input_select and an input_number helper.
had basically the same behavior… I think I have better luck with devices adding to the hub after a reset using Dev tools > Services > Insteon: Add all link
I’m planning on doing another hub reset (and I think a fresh hass install on a mini pc Ive got (using a Pi 4b right now) and then relinking using this method. I really dont want to factory reset the devices because i have several device-to-device links that function just fine w no hub at all. One of the things that makes me tough it out w insteon.
EDIT: back here to say that i’m having the most consistent result using the “add default links” going to each device one at a time. This was @teharris1 recommendation - and I think I may have added some junk by first trying to link using the + (Add ALDB) or the method above to try to link devices in bulk
so to recap - factory reset the hub, and assuming you still have all your discovered devices in HA like I did… go to each one and click the add default links & that should be good. No need to reset the devices and no need to even press the button on the device to pair!
OK. First question I would have. Do you have the custom “button-card” and “auto-entities” cards installed? If not there is not much sense in me posting things as they rely on these components.
Like this, but how did you get:
{{ input_number.insteon_scene_creator_scene_number }}
To return “71” and not “71.0” … because input_number returns as a state a float which would be “71.0”. And you send 71.0 as the scene number, the code fails.
Perhaps in your script that you do not post?
As in all these:
script.insteon_scene_creator_add_link
I actually finally got it working by using just the script. I created one for all lights on, and created one for all lights off. I couldn’t seem to find a way through one script to ask Alexa to turn it both on and off the way it seamlessly worked with one scene name in the old Insteon app. If I’m missing something please let me know.
So as my work around I created two routines in Alexa called turn on everything and turn off everything and attached the appropriate scripts. And somehow this made everything work simultaneously.
1 Like
Yes, Alexa scenes can only be turned on if they are HA scripts…there is no off. An HA script can only be run hence turned on, you either run it or you do not so you need two scripts/scenes which are run/turned on…one to turn on to execute the on state and another to turn on to execute the off state. Not overly intuitive and a little bit confusing if you are new to it I suppose…
Thank you for confirming.