LeeG

Yes, the 2457D2 i have signals a state change with both the manual buttons on the side of the LampLinc and manually turning the Lamp On/Off with its own manual switch.

Start Linking did not produce the expected results. The Start Linking process should result in the PLM and the Load Controller creating a Set button link outside of the ISY. This apparently was not accomplished as the Query Insteon Engine command was still rejected. That should not have happened if the PLM and Load Controller had exchanged messages with Set button press on the Load Controller. The rest of the sequence is as before since the Query Insteon Engine was rejected. This is the first reported problem with the NO Load Controller so it may be a problem with that specific device. Hard to draw a good conclusion from a single device.

The result is slightly different this time. The Load Controller rejected the attempt to write the End Of List link record this time. It accepted this same request in the first trace. However, all else after that point is the same. All commands are rejected as though the authorizing link record has been lost. The only thing I can think to try would be to use Start Linking rather than New INSTEON Device. I don't think that will change the link records the ISY will write so I would expect the same result. The commands will be in a different sequence in the beginning which might have an effect. This is all about how the Load Control firmware is responding so it is all really guess work. I will order a new NO Load Controller to see if all the new NO Load Controllers are doing the same thing. I have a NC Load Controller but the link record sequence is different for the NC variant and mine is pre I2CS. If you do decide to try Start Linking please have the event viewer running and post that trace as well.

I read where the Load Controller was factory reset but I suggest doing it once more in this sequence. Delete the Load Controller from the ISY Factory reset the Load Controller Run the event viewer as was done before Add the Load Controller again and post the new trace The Load Controller is not accepting commands from the ISY PLM after the second link record (End Of List record) is written to the Load Controller. It appears the writing of the End Of List record wiped out the first link record which I2CS devices require to accept commands from a PLM. Once the PLM is no longer authorized to communicate with the Load Controller nothing will work after that. This appears to be a device firmware issue but would like to analyze another trace after a fresh Factory Reset.

All commands sent to 08.84.70 fail to get any response from device. Six commands were sent, all timed out. Look for unswitched power going to the InLineLinc. An outside flood would have been on a switch. Perhaps the switch is Off or the wiring was not changed correctly to supply 120v at all times. Could be a coupling problem where the PLM is on one 120v leg and the InLineLinc is on the other. Check to see if the manual On Off buttons on the InLineLinc work. That will give an indication of power being at the device. When the problem is resolved the INST-ACK 02 62 messages will be followed by INST-SRX 02 50 messages from the device. Also note the ISY is not at 3.2.6. If this is a new InLineLinc Relay it is an I2CS device which requires 3.2.6. That is not the immediate issue as the device is not responding at all but will be once the communication problem is resolved if this is a new InLineLinc Relay. EDIT: Brians suggestion to check the Insteon address is very good. Eights and Bs are easy to misread. Double check the Insteon address label to be sure one of the 8's is really not a B.

Some LampLincs can be added to a Scene as a Controller but that will not satisfy the requirement as stated. Another device turning the LampLinc On/Off will not cause the LampLinc to turn On/Off other devices that are linked to the LampLinc. Insteon does not propagate controller actions that way. Device A as a Controller turns On LampLinc as a Responder. The LampLinc DOES NOT then go from Responder to Controller turning On any devices that are linked to the LampLinc as Responders. Again, Insteon does not propagate or chain Controller actions. Device A turning On LampLinc must also turn On the KeypadLinc button to keep the KeypadLinc button LED and LampLinc in sync. To add the LampLinc as a Controller, add the LampLinc to the Scene and click the Controller/Responder button to change from the default Responder to Controller. A single ISY Scene can be defined with the KeypadLinc button, LampLinc and "other device" all as Controllers. The ISY assumes a Controller is also a Responder so the ISY will cross link all three devices such that they will all stay in sync.

someguy Ignore those instructions as the devices will interact with each other. Any update attempts to the RF devices will fail because they are asleep. The ISY will queue the updates for each RF device. When the Restore Modem (PLM) is complete, any RF device that has a pending update (Icon to left of node) should be put into linking mode followed by a right mouse click and select Write updates to device. Do the RF devices one at a time. There may not be any pending activity at the end of the Restore Modem (PLM).

someguy Was the PLM reset during the upgrade process? That would account for every device if the PLM link database was cleared. A File | Restore Modem (PLM) will rebuild the PLM link database.

ds10 My old eyes must be playing tricks as I cannot find anywhere I said a surge suppressor needed a FilterLinc. It may be that the collection of devices plugged into the surge suppressor would need a FilterLinc but that is two very different things. I also cannot find where I said anything about removing a whole house lightening protection. I guess you are frustrated with your environment and decided to take out your frustrations at my expense. I really do not like to be misquoted or given attribution for something I did not say. What I said was UPS devices should be on a FilterLinc. Any assumptions beyond that point simply reflect a lack of knowledge on how surge suppressors and lighting arrestors work.

So long as the UI (Admin Console) is 3.2.6 and the ISY is 2.8.16 no need to run any tests. The last trace did not work any better than any of the other attempts with the same mismatch. Since forum assistance is not making any progress I suggest opening a ticket with UDI so they can remote into you system and clean it up.

GregE What level ISY firmware is being used? OutletLinc Relays are I2CS devices which require 3.2.6.

I have not seen an answer. Did you upgrade the ISY to 3.2.6 or are you trying run 2.8.16 with a compatible Admin Console.

Make sure the Admin Console and all browser sessions are closed. Then clear the Java cache. Open a browser session and enter http://192.168.2.5/admin substituting your ISY LAN address. Run Help | About to confirm result.

Xathros You can search on "partial list i2cs". Go to page 1 of that topic, about 2nd post down has a list of devices that have been found to be i2cs. I've been updating it as additional device types are discovered. It looks like they are updating the relay type devices first so any relay device after march 2012 is a potential I2CS candidate. Other users have found the TriggerLinc Relay is I2CS. The event trace will confirm once it is working. Smartlabs dropped the I1 Peek/Poke commands so any link management activity at the 2.8.16 level will fail if an I2CS device. The ISY uses Peek/Poke for everything back then except for RF devices like motion sensor and triggerlinc. The Peek/Poke commands are not rejected, just come back with data that matches the address being accessed.

Ditto the recommendation for updating to 3.2.6. I'm pretty sure the issue with the event trace and perhaps other symptoms are the result of running an Admin Console (UI 3.2.6) against an ISY level (2.8.16) that is two official releases out of sync. The suggested URL by Xathros will get you back to running an Admin Console that was designed to run with the ISY firmware in use. This should be verified with another Help About. Once that is done repeat the activity to update the ToggleLinc with Tools | Diagnostics | Event Viewer with Level 3 selected. Hopefully the event trace will work correctly, tracing the commands to the ToggleLinc so we can see what that problem is. Note that if the ToggleLinc is a Relay device and purchased after March 2012 it is likely an I2CS device which requires 3.2.6

Are there FilterLincs on the UPS devices. They are common sources of powerline signal attenuation. Each UPS should be on a FilterLinc.

What is device 13.04.56 and what was being done to it? A link record was being deleted from that device but no commands were traced. What ISY firmware is being used? Click Help | About. What is displayed for Firmware and UI level?

I don't understand the rational of using a configuration that is known to have a potential conflict. Okay, it works 80% of the time. That must not be satisfactory because it continues to be discussed yet there is no wellness to adjust the configuration. This may have nothing to do with the problem. Since Michel indicated a trace before showed a conflict at boot up would it not be prudent to fix the configuration to eliminate the possibility. The fact that a conflict does not exist hours or days later does not insure there was not a conflict at initial boot up. I’m not a network expert so maybe I just don’t understand. But if there is even a remote possibility this is caused by a conflict associated with the speed of router/modem/ISY boot up following a power failure is it not prudent to eliminate that possibility.

If nothing else the If is wrong regardless of Status or Control .... If From Sunset To Sunrise (same day) And Status 'garage door sensor' is On The To Sunrise must be (next day). The way it is written To time is before From time.

You might get away with defining it as a LampLinc. Assume it will take a future beta release before it can be used. If it happens to work as a LampLinc great but the plan must be that it cannot be used until a later beta.

Unfortunately Level 3 was not selected so the event trace is not helpful. If you plan to do it again please also include the device addresses I asked for along with setting Level 3.

Admin Console shows v.0A. Device reports I2CS. A change in mode is reported as well as Group 1 and 2 On/Off as the tstat calls for and turns Off heat and cool requests.

The other RemoteLinc would fail as it is not in linking mode. Not a good idea to put multiple RF devices into linking mode at the same time. Once the RemoteLinc that is currently being worked with is finished, put the other RemoteLinc into linking mode (Dim/Bright), right click and select Write updates to device. That should clear the other RemoteLinc. The ToggleLinc sounds like a powerline issue unless not running 3.2.6 and the ToggleLinc is a new Relay device making it I2CS. An event viewer trace with Level 3 selected, right click ToggleLinc and select Write Updates to device. The error log is not useful when analyzing Insteon device communications.

Post the event viewer trace (Level 3 selected), note the RemoteLinc address and any other device involved. If there are queued/pending updates the error might be related to a different device.

I am getting status reports from my 2441TH. I put the tstat between my two hands to create a humidity and temperature change. I think the 6F commands are reporting humidity change and the 6E is reporting a temperature change. The tstat is currently in Heat mode. I did manually add Controller links for Groups 2,3,4. Tue 06/19/2012 04:13:09 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 2F (2F) Tue 06/19/2012 04:13:09 PM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 06/19/2012 04:13:13 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 2C (2C) Tue 06/19/2012 04:13:13 PM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 06/19/2012 04:13:23 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 2E (2E) Tue 06/19/2012 04:13:23 PM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 06/19/2012 04:13:27 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6E A5 (A5) Tue 06/19/2012 04:13:27 PM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 06/19/2012 04:13:28 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 33 (33) Tue 06/19/2012 04:13:28 PM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 06/19/2012 04:13:35 PM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 34 (34)