Create a links table without devices powered?

[Banichi]

I'm pretty sure that the answer is no but is there a way to build a links table of devices that aren't installed yet. I have a large installation and would love to build it so that I don't have to manually add each device at the site. Trying to make it less time consuming at the job site. I know that I can manually add a device in the admin console via the address which is what I'll have to do anyway but it won't add without the devices visible on the network since it can't determine the insteon engine.

Again I'm pretty sure that I have to do these one at a time at the site but just checking.

[Brian H]

No you can't.

Maybe you could make a test power cord and power them up on a test setup.

Add them and mark them where you intend to install them at the site.

[larryllix]

Backup up your own ISY

 

Delete everything. (factory reset and reset a few parameters?)

 

Install and link all your remote location devices.

 

Backup your ISY to the carry-with-you backup file

 

Restore your original file 

 

Take the carry-with-you file to the new location with all your linked devices.

 

Restore at the remote site.

Edited October 19, 2016 by larryllix

[Chris Jahn]

Hi Banichi,

 

I'm going to add this as a feature request.  Although it will take a bit of work, it should be reasonable to do using our new node framework.  This likely will not be part of our first 5.0.x production release, but we will look to implement it after that.

 

This of course will only be useful for protocols (such as Insteon) that do not require a manual linking process. 

[Banichi]

Thanks for all of the suggestions. Chris I think that it would be nice to have in a future release as an option.

 

Unfortunately I didn't think about powering and creating a file with my own ISY 8 months ago when most of these were handed off to the electrician so most of the in-lines are already buried. Not that we can't pull them out if necessary but it'll be a pain now. But for future I will totally do that. I suppose I can just do a regular restore PLM with the PLM at the site and it will update the PLM links in the devices just fine.

[Brian H]

Few tips many of us do.

Write down the model number, six digit Insteon ID, where located. So you don't have to dig module out of hard to access areas if you need the information later.

I also write down the date code and reported firmware version from the Administrative Console list of modules.

 

Also do a Factory Reset on all new module being installed. Some module have been received with QC test links in them that where not cleared out before being sold.

Older firmware modules  that also could do optional X10 addresses. Have been seen with X10 addresses in them also from the factory.

Edited October 20, 2016 by Brian H

[mwester]

Expanding on Brian's excellent advice -- I use that same list to keep track of each unexpected event for each device, for example, each time I was forced to do a hardware reset on the device, or was forced to reload the links table to restore the device to operation.  That's helped me identify with certainty a failing or troubled device (most useful for locations such as my kitchen, where I have multiple 3-gang switchplates full of Insteon devices, making it very difficult to remember exactly if the KPL that needs to be reset is the same one that needed resetting last spring, etc.)

[Banichi]

Thanks for the help guys. I do keep a list of the devices and the insteon addresses. I like the date code and firmware version. I'll add that to my spreadsheets. With large numbers of in-line units I usually hand them off to the electrician and he installs them as needed during rough-in and then notes the address and the circuit that it is wired to on the box. I then note that on my spreadsheet. I'll need to find a good way to get him to note which specific fixture it is in as well so that if it needs to ever be replaced I don't have to go looking for it in every can of the 8-can circuit. Maybe a cell phone shot.

Nathan