TheRydad

Thanks, @DennisC & @Techman!

I am going to replace mu ISY994 with a new EISY. I see on the product page that I should be able to use a current ISY994 backup to restore the configuration on my new EISY. I also plan to purchase a new Insteon USB PLM (I currently have a Serial PLM for the ISY994). Is there a documented upgrade path for this? I assume I will do something like this: Backup current ISY994 and power off/decommission the ISY994. Install new EISY and bring it online on my network. Plug new USB PLM into power and then EISY. Restore the backup from step 1 on the new EISY. Perform a PLM "Restore" on the new EISY to reprogram all links with the new PLM Insteon ID. Am I on the right track?

Thanks for everyone's help. It turns out after some digging, I was having some comm problems with my Insteon network. I need to do a little more testing, but it appears to be from a dimmer module I added last weekend. I was also not setting up the automation correctly, but once I realized that the even scene and KPL button status change weren't even being seen by the ISY, I realized the problem was further upstream. I then realized the ISY wasn't seeing any traffic not initiated by the PLM. After finding some of @MrBill's replies to some threads related to that, I was able to figure out what was going on. I also got really lucky- as my daughter was going to bed, she mentioned that her reading lamp wasn't turning on. I pulled out the dimmer module last night and this morning when I was removing it from the Insteon network to add a new one for her, I happened to look over at the event viewer window and noticed the ISY was seeing traffic again. @MrBill Thanks for the tip on creating an Insteon scene to use in HA. That seems like it is going to allow me to do a lot more things with the state of the Insteon button used to initiate the automation. Like being able to turn it back off because of a third party action, for example.

Thanks, @MrBill. That makes sense. I had actually played around with creating a scene with just the one device like you mentioned so I could test within ISY, but didn't think about using that scene on the HA side. I'll mess with that later this afternoon. (If anyone cares, I am trying to automate some motorized blinds that are controlled by Somfy MyLink and integrated into HA.)

This might be better suited in the HA forums, but there have been good answers in here before so I figured I'd give it a shot. I am trying to figure out how to trigger an automation in HA with a keypad linc button press. I tried the YAML below, but it isn't firing the automation. "b1g1t8_unassigned" is the sensor name for the button I want to use. Any guidance is much appreciated. platform: event event_type: isy994_control event_data: entity_id: sensor.b1g1t8_unassigned control: "DON" value: 255

Thanks, @MrBill and @lilyoyo1. If you'll indulge me a little further, I have a couple of technical and "style" questions now that I have read up some more. 1. With the exception of the links created between devices and PLM, does creating an ISY scene populate the devices' link tables the same as the manual method of "put device in linking mode, press set button on other device, repeat..."? In other words, are they more or less functionally equivalent? (I am only talking about Insteon here.) This is more of a curiosity than anything. I am trying to make sure I understand what is happening under the hood so I can have a deeper understanding of the technology architecture. 2. My understanding of the "spoken" field for devices and scenes is that this is how I will refer to the device/scene when speaking to Alexa, etc. I assume that I need to make sure that what I put in "spoken" is unique and only applied to 1 device/scene. However, I was able to give the same spoken name to 2 devices and a scene using the admin console, so that uniqueness is apparently not enforced in the UI. When making a 3 way/4-way scene, should I apply the preferred "spoken" name to the scene? Is there a best practice for this? 3. This is more of a style thing, but I am trying to decide how I want to name everything. I think I want to give each device a name based on the load it controls and it's location in the house and on the wall. i.e. Something like "Foyer Chandelier-Entry-B2-S3" would mean the switch is in the entryway, 2nd box down, 3rd switch from left and controls the foyer chandelier. I would then use the "spoken" field referenced above to name it for Alexa purposes-"foyer chandelier" in this case. Any opinion about this approach? It sounds like "device discovery" vs. "key in address" methods of adding devices is a matter of preference. I have already made some progress toward making a spreadsheet of all devices with addresses, locations, controlled load and whether the load is wired to the device or it is a 3/4-way "remote" device, so I will finish that up for documentation. I will factory reset everything and then manually key them in from my desktop using the spreadsheet. There's a bunch of rooms and locations where there isn't a great spot to set a laptop. That is why I was asking about being able to tag or name devices using the mobile app. I really appreciate the time you took to answer my earlier posts. Thank you!

Thanks, @MrBill. That's kind of what I figured. If I manually add a device in ISY and choose the "delete existing links" option, will that erase all links in the device and effectively "reset" it? I feel like that would at least eliminate me having to walk around to every device and factory reset it. I assume that would leave the device with only a link to the PLM in its link table, but I am not certain about that assumption. Is the correct way to create a 3-way/4-way configuration by putting all devices in a scene, and make them all controllers and responders for the scene? I want them to all respond with the correct LED level indicator when touching a physical switch and when calling them from Alexa, etc. Is there some kind of way to tag or name a device in the mobile app? I didn't see a way to do it, but that would allow me to figure out which device is which without having to walk back and forth to my computer or laptop every time. Is there any kind of "local API" that would let me script some of this through SSH or http calls from a desktop machine? I appreciate the guidance as I get more familiar with this product. It will certainly give me a lot of the scheduling and other flexibility I was missing when just using the Hub.

I have about 150 Insteon switches and lamp modules in my house. They are all linked to an Insteon Hub for now, but I want to move everything to my new ISY 994i/Pro. Insteon support says they can send me a list of all of my Insteon devices and the names I have given them in the Insteon app. Is it possible to do some kind of bulk import of devices with names? Is it possible to use the ISY to bulk delete all existing links and then recreate them manually in the admin console*? Is there a command line or scripting engine that can be used to set this stuff up in ISY? Thanks for any help and guidance anyone can provide! -R *- Side note: There are a lot of really weird links that my electrician made. To be fair, he had never installed any Insteon switches before, but he wanted to get the 3-way setups working so I showed him how to do the multi-way manual linking on switches. A lot of bizarre things appear to have happened while he was "learning" how it worked. A bunch of three way switches were only setup in one direction. I also keep finding weird links that must have been accidentally setup. For example, turning on a light in the kitchen also turns on a floodlight in the driveway (but not vice-versa).