LeeG

Multiple things seem to be wrong. The device responded to the query of Insteon Engine indicating it is an I2CS device. In all cases I have seen before this when the device is factory reset the link records are cleared so the TriggerLinc should have responded with a NAK and a FF instead of the 02 because the PLM is unknown. Wed 04/24/2013 08:43:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 08:43:03 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Second the TriggerLinc continues to fail to respond with its device type message. Wed 04/24/2013 08:43:04 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:04 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:13 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:13 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:13 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:13 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Wed 04/24/2013 08:43:22 : [iNST-TX-I1 ] 02 62 21 64 13 0F 10 00 Wed 04/24/2013 08:43:22 : [iNST-ACK ] 02 62 21.64.13 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 08:43:23 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 10 00 ID-REQ (00) Wed 04/24/2013 08:43:23 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 The message in Blue from my system adding a TriggerLinc is what is missing on your system. Wed 04/24/2013 02:01:27 PM : [iNST-TX-I1 ] 02 62 11 B8 2D 0F 10 00 Wed 04/24/2013 02:01:27 PM : [iNST-ACK ] 02 62 11.B8.2D 0F 10 00 06 ID-REQ (00) Wed 04/24/2013 02:01:27 PM : [iNST-SRX ] 02 50 11.B8.2D 22.80.0B 2B 10 00 ID-REQ (00) Wed 04/24/2013 02:01:27 PM : [std-Direct Ack] 11.B8.2D-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 04/24/2013 02:01:27 PM : [iNST-SRX ] 02 50 11.B8.2D 10.02.28 8B 02 01 (01) Wed 04/24/2013 02:01:27 PM : [std-Broadcast] 11.B8.2D-->10.02.28, Max Hops=3, Hops Left=2

Delete the device, Factory Reset, repeat the add with the event trace at LEVEL 3 with the TriggerLinc near the PLM. The device that was used to produce the last trace did not respond at all which could be defective device. Would prefer not to have to analyze multiple devices and problems with the Insteon Mesh network at the same time.

It is worse now. It will not indicate what Insteon Engine the device contains. This command worked in the previous location. After three failed attempts the ISY stops the add. Wed 04/24/2013 09:58:23 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:23 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:32 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:32 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) Wed 04/24/2013 09:58:41 : [iNST-TX-I1 ] 02 62 21 64 19 0F 0D 00 Wed 04/24/2013 09:58:41 : [iNST-ACK ] 02 62 21.64.19 0F 0D 00 06 (00) This is the same command from the first trace. The device responded (02 50) message which is missing in most recent trace. Almost looks like it was not in linking mode (asleep) so it could not respond. Wed 04/24/2013 08:43:03 : [iNST-TX-I1 ] 02 62 21 64 13 0F 0D 00 Wed 04/24/2013 08:43:03 : [iNST-ACK ] 02 62 21.64.13 0F 0D 00 06 (00) Wed 04/24/2013 08:43:04 : [iNST-SRX ] 02 50 21.64.13 12.9C.44 27 0D 02 (02) Wed 04/24/2013 08:43:04 : [std-Direct Ack] 21.64.13-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Just realized this is a different device address between the two traces. Perhaps staying with one device to keep the number of variables to a minimum would be useful.

The traced Open/Close Sensor is an I2CS device that failed to identify itself as to type of device after three attempts. Suggest a Deleting device, Factory Reset and repeat add. Try moving the Open/Close Sensor closer to the PLM if Dual Band or an Access Point if a 2412 PLM

Not at this time. There is discussion about introducing some basic Scene Status but none exists today. Insteon has no concept of Scene Status so it has to be developed by the ISY if introduced.

rlebel Click Help | About, verify what Firmware and UI Lines indicate. I added an Open/Close Sensor to 4.0.3 using New INSTEON Device, both using default Auto Discover and selecting the (2843-222) Open/Close Sensor. Both options added two nodes, Opened and Closed. I'm wondering if the UI is at the correct level?

I don't use the ELK but thought I read somewhere RP and the Admin Console cannot be running at the same time?

I all previous cases that have been traced the error stems from actual Insteon message flow. Until the actual situation is traced one cannot be 100% sure but it is hard to see how a LAN problem would be interpreted as an Insteon device error.

Assuming the KeypadLinc button is a Secondary button, Secondary KeypadLinc buttons cannot be turned On/Off with Direct commands. Define an ISY Scene with the Secondary KeypadLinc button as a Responder. When the Program completes its logic have it issue Set Scene 'xxxxx' Off where xxxxx is the Scene with the Secondary KeypadLinc as Responder.

Send the UUID of the old and new ISY and the list of modules to sales@...... They will activate the modules

This Insteon message issued when Scene Test ran indicates the PLM had no record of the Scene in question. Deleting and redefining the Scene fixed this specific issue but does not answer the more troublesome question of what happened to the link records in the PLM. If you see issues with the devices not showing the correct state or not showing state changes at all then the PLM should be examined. Run Tools | Diagnostics | Show PLM Links Table followed by clicking the Count button when the display completes. How many link records are counted? The Show PLM Links Table under the ISY is not very good as any Insteon messages that reach the PLM during the display process will result in false high/low record counts. The Show PLM Links Table and Count should be run 3-4 times to insure the same link record count is obtained. Sat 04/20/2013 12:00:30 PM : [GRP-RX ] 02 61 1B 13 00 15 Problems with the PLM link database may be resolved by doing a Restore Modem (PLM).

Right click the Scene name, select Diagnostics | Scene Test. Post the results so the hops count and retries can be determined. When you say the Program does not run, are you looking at the Programs | Summary tab and checking the Last Run Time and Status. If the Summary shows the Program did not trigger then we look at the trigger conditions. If the Summary shows the Program did trigger then we look at communication from the PLM location. Scenes have no device ACKs and no retry so if the PLM communication is marginal Scenes is where the issues will surface first. Is the PLM plugged into an outlet and not a suppressor strip. Are other electronics powered from the same circuit issolated with a FilterLinc.

For that I would use "If Control 'Smoke Bridge - Smoke' is switched On Or Control 'Smoke Bridge - CO' is switched On Then Notify.... Using 'If Control' will get a Notify each time the Smoke Bridge activates either node. Once the Status goes to ON I'm not sure what turns if back to OFF.

It is always helpful to provide more than "I cannot get this to work.". What does not work? ApplianceLinc does not turn On/Off KeypadLinc buttons do not turn On/Off KeypadLinc buttons do not override Program(s) do not trigger Program triggers but only some of the devices respond Details like that, whatever describes in detail the issues. Some basics to check, insure Programs are Enabled and Saved. Each Program triggers only at the specific time in the IF. The programs do not trigger at any other time. Do the Programs work when run manually? Also a good idea to post the actual Programs. Right click on Program name, select Copy to Clipboard, paste into post.

Get the ISY Firmware and the UI to 3.3.10. Not sure if you indicating the ISY is at 3.2.6 or at 3.3.10. If the ISY Firmware is 3.2.6 update the ISY firmware to 3.3.10. If the ISY Firmware is 3.3.10 and the UI is 3.2.6 then clear the Java cache and update the URL invoking the Admin Console (UI). After cleaning up the running environment such that both Firmware and UI indicate 3.3.10 if there are still problems then run event viewer at LEVEL 3, use New INSTEON Device to add the ToggleLinc. Post the event trace.

Explain what type of trouble? Difficult to know what "I'm having all sorts of trouble" means. An event trace at LEVEL 3 using New INSTEON Device should be useful. Could be as simple as the install location has poor/no communication with the PLM. Or the ISY firmware is backlevel and does not support I2CS neither of which requires moving to a 994i. Although it is inevitable that a 994i will be required if any new devices are being installed. What ISY firmware level is being used, both Firmware and UI?

Exactly right. Of course the appropriate detectors are required. Some detect only smoke, some only CO and some cover both. The nodes with the Insteon address can be renamed to Smoke Bridge or something more meaningful than the Insteon address. I prefer using New INSTEON Device because a meaning Name can be assigned when the device is added to the ISY.

The Smoke Bridge does not identify which smoke detector. Each node represents the condition indicated by the node name. CO2 represents CO. Note that the 4.x.x beta has additional nodes. Running a 99i the 4.x.x beta stream cannot be installed so the additional nodes are not important.

In theory yes. Just as the ISY adds link records when a device is added so the ISY can control and know device state, HL does the same thing. Basically the ISY environment is being destroyed. Every device should be factory reset and then have a Restore Device done after playing with HL. Be sure to take a good ISY backup before starting with HL.

I had ideas of using the type of MS that is connected to the security system which as interior mounted units never false. Had planned to connect to something like an EZIO2X4 that has four inputs so I could know which of the four sides of the house tripped externally. Was a nice idea until I realized that deer walk around here all the time. They just love the flowers my neighbors on both sides plant every year. Changed to driveway monitors that are buried Dakota Alert magnetic sensors. Does not cover human traffic walking round but better than all the false trips from the 4 legged creatures. Now the floods just come on and I don't track the activity inside.

Do not have trees, water, street traffic in Motion Sensor field of view. It may be necessary to aim the Motion Sensor lower so that these items are not in the field of view. Motion Sensors on the back of the house (not Insteon motion sensors) trip when wind generates chop on the lake surface. There are security oriented motion sensors which seem to be less sensitive to false trips but they are more expensive and do not directly connect with Insteon network.

"is it fair to assume that subsequent versions of existing Insteon devices and any new devices that come along will not be supported by the ISY?" Not supported by 3.3.10 on 99i. The 4.x.x beta stream already has additional I2CS rework which is not in 3.3.10. If it were not for I2CS one might consider staying with 3.3.10 if no new devices were anticipated. However, staying on 3.3.10 is just not realistic with the continuing I2CS changes that are still being reacted to. There was an update path from 99i to 994i but not sure that offer is still in effect. Suggest sending an email to UDI sales@..... for the latest information on upgrade to 994i.

Jumper 5 should be in place. Use New INSTEON Device, enter Insteon Address, Name of choice, use default Auto Discover. BEFORE clicking Ok put motion sensor into linking mode by pressing MS Set button until Red LED blinks continuously. Now click Ok. Be sure Motion Sensor is in range of a Dual Band device.

You are very welcome. I have looked at the alternatives a few years back and was not satisfied with any of the other options at the time. With more focus on ZigBee and Zwave these days there may be viable options now. Spent some time looking for alternatives to the EZIO2X4 which monitors and controls my detached garage. Have not found a good substitute. I could live without the remote monitor/control but have gotten very use to it over the 5+ years for the garage.

It is a design change. Before there was Off, 1%-99%, On to represent the various states. Now it is Off, 1%-100%