LeeG

Is the problem the KeypadLinc is not changing to 8 button mode or the ISY is not recognizing the change. If the later it is not automatic. The KeypadLinc has to be Deleted and added again to pick up the additional nodes. If the KeypadLinc is not changing, cycle the Main button after making the change with Main and H held On. What ISY firmware is being used. I changed a KeypadLinc from 6 to 8 button which the ISY recognized when I added it back at 3.2.6.

Doing a Restore Device will rewrite all the link records the ISY believes should be in the KeypadLinc. If that includes links to the dead switch those will be restored. It may be necessary to Delete the KeypadLinc, Factory reset and add it back. This will require the KeypadLinc buttons be added back to Scenes.

Did you use the ISY Replace With .... function to replace the dead switch? That function will fix the links in other devices that are known to be pointing to the dead/replaced switch.

Go to Program | Summary, right click, select Find/Replace. Select Scene and the Scene Name to search for.

There were issues with the initial Java 7. Perhaps installing the latest Java 7 update resolved the early issues. I stayed on java 6 when the problems with the initial Java 7 update started to surface. Glad it is working now.

It sounds like an AV issue blocking the push of data from the ISY to the Admin Console. Avast and Kaspersky are known to block the data push. Run Tools | Diagnostics | Event Viewer with Level 3-Device communications selected. Using the Admin Console turn an individual switch On and Off. I suspect the activity will not show in the Event Viewer. Until this is resolved no sense trying anything else as you have no visual indicators as to what is happening.

The unwanted link(s) are in the IRLinc. The 6F is the correct command if it were a PLM issue. There is no means of directing the ISY to replace its information with that currently in the PLM. The Restore Modem (PLM) goes the other way and would defeat the effect of the 6F. Anyway, the problem is with the IRLinc link database.

No buffering. The PLM will reject the next command if it is busy with the current one.

Question for SmartLabs. The ISY cannot run faster than the PLM capability. With the powerline as the functional interface to Insteon devices I doubt a faster interface between the ISY and the PLM would be of much use.

1 - What frequency does the Insteon RF use? 900 MHz band The DECT 6 frequencies are not in the 900 MHz band. Is that correct? Yes. 2 - Is an Ethernet cable between the 2413S and the ISY-99i port Port A correct? Yes. 3 - Is there a way to increase the speed of the link between the 2413S and the ISY-99i? No.

That should be the difference between an IRLinc R and an IRLinc T. The IRLinc R receives IR signals and controls Insteon devices in response. This makes the link records in the IRLinc R Controller (E2) link records to be able to control other devices. The IRLinc T receives Insteon commands from other devices making the IRLinc T a Responder which requires Responder (A2) link records.

wrj0 Did/do you have the Event Viewer set for Level 3? I think your messages are information about the variables WCLinc is pulling from the ISY that are produced when the Event Viewer is set to Level 3.

Operation of any individual Responder device would not affect the other Responders. Turning the ISY Scene On/Off with an ISY Program or through the Admin Console will control all Responders. Correct. That includes Controllers that also function as Responders. A Scene with all devices that can function only as Controllers (ControLinc, RemoteLinc, RemoteLinc2 as examples) would serve no purpose I can think of. However, many Insteon devices are Controllers and Responders. When adding these devices to a Scene as a Controller they also function as Responders. So a Scene with all devices as Controllers where the devices function as both Controllers and Responders (KeypadLincs, SwitchLincs, ToggleLincs, as examples) is a common ISY Scene definition. Because the ISY assumes a Controller is also a Responder (if device has that capability) adding these devices as Controllers results in all the devices being cross-linked such that they all control the load and the status LEDs stay in sync.

remedy1234 Glad to hear the problem was resolved. Thanks for posting the results. So often it gets resolved and folks following the topic do not know what solved the problem.

The Zone connections are made with small screw terminals, very similar to the I/O Linc connections. The EZFlora also has an RJ45 jack just behind the screw terminal block that can be used to connect a rain sensor and pulse water meter. The small breakout connector as well as a rain sensor are sold by Simplehomenet (manufacturer of the EZFlora). The breakout connector has an RJ45 jack to screw terminal connector which allows a standard RJ45 cable between the EZFlora RJ45 jack and the breakout connector jack. Then the rain sensor and pulse water meter (both optional) can be connected to the breakout connector screw terminals, just like the Zone connections. I have used an EZFlora for several years with no problems. If you do decide to go with the EZFlora I recommend purchasing it from Simplehomenet directly. This insures the latest EZFlora firmware and direct manufacturer warranty. Smarthome should have the latest EZFlora as it has not changed in more than a year but I still recommend the Simplehomenet web site for purchase of any Simplehomenet device. Here is link to EZBreakout connector http://www.simplehomenet.com/proddetail ... tConnector

biredale The door sensor (TriggerLinc?) would be a Controller as that is all that device type can be. What type of device is physically controlling the "light". It could be a Responder, may be appropriate to define it as a Controller which also functions as a Responder. Depends on the Insteon device type. There is no concept of "Scene Status". When the Scene is selected the devices are listed with their respective status.

uffy Do you mean the device type is not recognized? Make sure that Help | About shows 3.2.6 for Firmware and UI lines. If not clear Java cache and use the URL for accessing the 3.2.6 Admin Console.

Since the router does not support it is there an option to turn uPnP off in the DVR.

bocarob If you would please, rerun the Event Trace with Level 3-Device communications events selected. The posted trace does not show actual commands coming from motion sensor

"the save option must be only for ISY programmers??" The Save/Load buttons work with the XMLfiles.

Did you have to register the camera IP addresses with the DVR? It sounds like the DVR is checking the network for whatever cameras it can find.

This subject has been discussed before. UDI position is the XML file is not intended for human use. The decimal values can be converted to hex if you have a calculator that handles hex. I have done it a few times, concluding it was not a useful analytical/debug tool because of the time/effort it takes to do the manual conversion. REST is not helpful as none of the commands return the data in the format of the Show screen display.

It should not be necessary to do anything but replace the battery. The configuration information and link database are in non-volatile memory.

Circuit 1 is a 3-way with device A and device B. Use ISY Scene A, adding device A and device B as Controllers. Circuit 2 is a 3-way with device C and device D Use ISY Scene B, adding device C and device D as Controllers. Circuit 3 is a 4-way with device E, device F and device G Use ISY Scene C, adding device E. device F and device G as Controllers The device names and ISY Scene names are arbitrary.

No. A single MorningLinc cannot "independently" control multiple locksets. A single MorningLinc can control multiple locksets at the same time but not independently. I believe the advertised count is 15 separate locksets. I do not know if each MorningLinc has a separate code when it identifies itself to the lockset which is necessary if another MorningLinc can control another lockset independently. I believe each MorningLinc uses a different code. Otherwise once one MorningLinc was registered any MorningLinc could control the lockset. However, believing is not the same as knowing for sure. I suggest calling the Insteon Gold Line. The answer is not in the MorningLinc User Guide. I know that multiple MorningLincs can control the same lockset (I do that). I have only one lockset so cannot verify a second MorningLinc can independently control a second lockset. For sure one MorningLinc cannot as there is no means of relating a specific Insteon link to a specific lockset.