LeeG

jerlands, larryllix The XML to link record display is a very quick, very dirty Java program i wrote months ago because I was tired of converting a very long posted XML file. The ISY Saves the link file display in XML which is fine, had to be in some format that could be written. However, for the human trying to analyze one of the large XML files, it was a pain.

larryllix As far as Insteon devices are concerned only the first byte of a link record being 0x00 is necessary to indicate End of List. With many Insteon devices now in use still using Peek/Poke to update link records (1 byte at a time) it would be a waste to update the other 7 bytes for appearance only. I don't think the "ISY" data actually takes up space for 8 bytes of zeros. The ISY knows how many link records are active (2 in this case) and displays 8 bytes of zeros after the last active link record. See the attachment Compare display which indicates the End of List as [ignore]. The link record at 0FA8 in attachment looks like a mismatch but is Insteon using two bits in first byte for Hops management. Just like the End of List, other link records can appear bad but be fine because Insteon I2CS devices use bits in the first byte that are both temporary and not told to the PLM/ISY. Office / 1A 17 13 1 - from device 0FF8 : A2 00 3B.96.D9 FF 1F 01 0FF0 : A2 13 3B.96.D9 FF 1F 01 0FE8 : 00 00 1B.FD.5A FF 1F 01 Office / 1A 17 13 1 - from ISY data 0FF8 : A2 00 3B.96.D9 FF 1F 01 0FF0 : A2 13 3B.96.D9 FF 1F 01 0FE8 : 00 00 00.00.00 00 00 00 EDIT: sorry, don't know what "code chart" is referring to.

The last link record is logically the same, End of List, Office / 1A 17 13 1 0FF8 : A2 00 3B.96.D9 FF 1F 01 0FF0 : A2 13 3B.96.D9 FF 1F 01 0FE8 : 00 00 1B.FD.5A FF 1F 01 Office / 1A 17 13 1 0FF8 : A2 00 3B.96.D9 FF 1F 01 0FF0 : A2 13 3B.96.D9 FF 1F 01 0FE8 : 00 00 00.00.00 00 00 00 This device has no Controller link record(s) (start with E2) so the ISY will not receive device change messages. It looks like the PLM was Deleted somewhere along the process. The corrective action is to File | Restore ISY from a backup taken before PLM was Deleted, followed by a File | Restore Devices.

" I mean that it will extend the range of all insteon devices hooked up in my home" That is not answerable and likely not true. Nothing SmartLabs produces will receive "all insteon devices" installed in a typical installation. Opposite 120v leg, not in RF range (from your post - the open/close sensor sorta sees the HUB), various reasons "all" insteon devices would not be processed by HUB.

Thanks Stu.

Gee Is the Hub in a plastic or metal case?

Check the Error Log to see if there is any indication of problems around the time of the symptoms.

The combined node/scene limit is 1024. programs 1000. What is scene count? What is program count? What is Firmware level? What is UI (Admin Console) level? (Help | About)

Gee "does this imply that you must choose between either the HUB or the ISY but you can not utilize both ?" If you are an expert with Insteon and the use of multiple Controllers (ISY and Hub) it can be done BUT it takes lots of work, sustained over the life of using two Controllers at the same time. It is not a simple environment and requires expert knowledge.

If restarting the UI did not resolve, exit admin console and unplug ISY for 30 seconds. What does not work appears to be the nth try to bring up Start Linking without it completing.

The initial popup should display when Link Management | Start Linking is clicked. No device interaction is required. Suggest exiting Admin Console and restart. What does Help | About show for Firmware? UI?

jrclark1978 I prefer to use "New INSTEON Device" because a device Name is assigned rather than the Insteon address of device. Also "New INSTEON Device" must be used to add a battery powered device. However, if using "Start Linking" the following popups are expected. StartLinking is the initial popup from clicking Start Linking option. FromSetButton popup displayes when device Set button is pressed for 3-5 seconds. Then click Finish button on StartLinking popup. The device is added using the Insteon address. See DeviceAddComplete image

Yes.

Manually put the Motion Sensor into linking mode (necessary for battery powered device). Click on the Options button. Click the Query button on the popup. An Event Trace at LEVEL 3 will show command activity pulling the displayed information from the Motion Sensor. Changing some value and click Done to save new data. Not necessary to change data before click on Done. Be sure to take the Motion Sensor out of linking mode when finished.

"So I set switch 1 to Off and switch 2 to off and performed the link following Insteon instructions. I did not set both switches to On and link again. This works perfectly for me, when switch 1 is turned off, switch 2 turns off, however, when switch 1 is turned on, switch 2 does nothing." This is not possible. Turning switch1 On actually turns switch2 Off because switch2 was linked in the Off position. Turn switch2 On and then turn switch1 On. switch2 will turn Off which is not "switch 2 does nothing".

"1. When Switch 1 is turned off, then turn off Switch 2. 2. When Switch 1 is turn on, then do nothing to Switch 2." #1 is simply linking switch1 as Controller with switch2 as Responder. However, how did you accomplish #2 with linking only. ? EDIT: Once switch1 is a Controller switch2 cannot "ignore" On command. EDIT2: The Responder On Level for switch2 (when switch1 is Controller) can be set to 0% On Level so that switch2 will not turn On. However, the 0% On Level will turn switch2 Off when it receives the On command from switch1 so the On command is not being ignored.

The Motion Sensor is not physically being queried. As you correctly remember battery device cannot be queried. The query request against the Low Bat node simply resets the Status to Off.

"Is there a way to completely reset an INSTEON device i.e. - a factory reset, through ISY programatic control? " No. Note that neither devices themselves nor the ISY create link records on their own initiative. For devices to create link records two devices have to be put into linking mode. The ISY has to receive a command.

Only one battery device can be manually put into linking mode at a time. Trying to do multiple battery devices at the same time will link the battery devices together. Also a battery device times out of manual linking mode in 4 minutes. I'm more concerned why every KPL, SwitchLinc, ToggleLinc, etc would be restored each time.

Scenexxxx SwitchLinc1 - Controller SwitchLinc2 - Controller RemoteLinc2 button x - Controller - SwitchLinc1 Responder 50%, SwitchLinc2 Responder 75% RemoteLinc2 button y - Controller - SwitchLinc1 Responder 100%, SwitchLinc2 Responder 100% RemoteLinc2 button z - Controller - SwitchLinc1 Responder 0%, SwitchKinc2 Responder 0% Click on RemoteLinc2 button x.. SwitchLinc1 and SwitchLinc2 display on the bottom, right side. The On Level and Ramp Rate field values for these "Responders" are displayed as sliders which can be set as desired. These On Level and Ramp Rate values apply when button x is pressed. Each RemoteLinc2 button has its own unique On Level and Ramp Rate values for the button Responders.

If you happen to have some old Insteon equipment as I do a 9 minute ramp rate is still useful. It is always good to read the Specs section on the retail page for a device which indicates what the device actually supports (now 8 minute max ramp rate). Actually the ramp rate field runs from 0x1F (0.1 second rate) to 0x00 (was 9 minutes but now causes a 0.2 second ramp rate). The 9 minute value (0x00) could have come from not setting a ramp rate value which caused diagnostic issues because no one waited for 9 minutes. Years ago SmartLabs solved that problem by having a 0x00 ramp rate field result in a 0.2 second ramp.

Now I am confused, I thought there were three RemoteLinc2 buttons with various Responder settings. Please identify the RemoteLinc2 buttons and what devices they are controlling. It is not difficult to configure once I know what buttons and devices.

Sorry but I don't understand "arguing". Scenexxxx SwitchLinc1 - Controller SwitchLinc2 - Controller RemoteLinc2 button x - Controller - SwitchLinc1 Responder 50%, SwitchLinc2 Responder 75% RemoteLinc2 button y - Controller - SwitchLinc1 Responder 100%, SwitchLinc2 Responder 100% RemoteLinc2 button z - Controller - SwitchLinc1 Responder 0%, SwitchKinc2 Responder 0% The SwitchLincs would have a unique On Level/Ramp Rate for each RemoteLinc2 button, assuming the RemoteLinc2 buttons are controlling the SwitchLincs. If the RemoteLinc2 buttons are controlling something else the buttons would be in a different ISY Scene with the appropriate devices.

The UI should be at 4.3.26. Not sure that is causing a problem but best to have Firmware and UI at 4.3.26. When device A is issued a Restore Device, are the same other devices updated for each new Restore Device.

No problem using three RemoteLinc2 buttons to drive those three Scenes. Each RemoteLinc2 button can drive a different Scene or even drive the same Scene that has different Responder values for each RemoteLinc2 button. Is that what you want to do with the RemoteLinc2 buttons? If not please explain what configuration you would like to have.