LeeG

The Zone changed state before the 5 minutes elapsed.

That switch is designed to handle the very situation you have. Remember that the 2-wire SwitchLinc is an RF only device. It must be in range of a Dual Band device for two way communication with the 2-wire SwitchLinc.

This situation can be verified easily by putting the new ToggleLinc on an Appliance cord, plugging the cord into the PLM plug point. I would expect the ToggleLinc to add when powered from the PLM location.

The I2CS Extended response to the link management command is not reaching the PLM. Without that response the ISY cannot determine where the device link database resides. Likely the other ToggleLinc is not an I2CS device where the location of the link database is assumed. This can be verified by right clicking the older ToggleLinc node, select Diagnostics | Query Insteon Engine with the Event Viewer running at Level 3. The Insteon Engine command is likely returning an 01 from the older ToggleLinc rather than the 02 (I2CS) the new ToggleLinc is returning Tue 10/30/2012 03:36:31 PM : [iNST-TX-I1 ] 02 62 1D 06 BE 0F 0D 00 Tue 10/30/2012 03:36:31 PM : [iNST-ACK ] 02 62 1D.06.BE 0F 0D 00 06 (00) Tue 10/30/2012 03:36:32 PM : [iNST-SRX ] 02 50 1D.06.BE 18.D0.D8 27 0D 02 (02) That aside how to get the Extended response back to the ISY PLM depends on the existing Insteon inventory. Perhaps adding a Dual Band device to the circuit the new ToggleLinc is on will help. I had a similar problem after adding an I2CS KeypadLinc Dimmer at the end of a circuit that had a collection of older I1 devices that do not repeat I2 Extended commands. Had to add a Dual Band SwitchLinc along side the I2CS KeypadLinc before I could build the link database. If an outlet can be found on the same circuit (may be difficult because lighting and outlets are often on different circuits) an Access Point can be plugged in to provide the Dual Band capability.

no clue Your conclusions about the wiring matches the standard wiring technique where the power feed goes to the fixture. The uncapped Black wire is Line (120v power - verify with a meter) The White capped wire in the same pair is Neutral (verify with a meter) The capped Black wire is the switched load as indicated by the white marking on the Black wire (standard way of marking the Black switched load coming from the mechanical switch). The White wire from the switch is normally connected to the Black Line. The Black wire with the White marking indicates it is switching the Load. The simple solution is to use a SwitchLinc 2474D 2-wire dimmer. It steals power through the Load so the light has to be incandescent or dimmable LED. The SwitchLinc requirements are spelled out on the sales page for the 2474D.

brentrosales Right click the node, select Diagnostics | Query Insteon Engine. The 3.3.3 Beta has more device variations to support and is dependent on the Insteon Engine information being correct. If that does not resolve what is the device type and firmware level show in the right pane. Run Tools | Diagnostics | Event Viewer at Level 3. Change the LED Brightness level and post the event trace.

I don't think the ISY has the actual X10 specific information as it was not used to establish the actual X10 information. The X10 codes were received by the EZX10RF itself, stored in its internal memory and then the ISY established the link records to support the new node. The previous Event Viewer trace, although shown as being at Level 3, has no Insteon commands issued so I do not know what the communication error the ISY is presenting. That will have to be addressed by UDI as based on the event viewer no commands were sent to the EZX10RF. It may be irrelevant at this point if the EZX10RF was reset. That would have wiped out the X10 information which I don’t think the ISY can put back.

I use KeypadLinc buttons to control lighting and bay door movement. The ISY/PLM was used to link the KeypadLinc with the various Insteon devices in the garage for lighting and door control. I could use the ISY/PLM but at this point find the KeypadLinc all I need. Of course the ISY Admin Console does show lighting and door status

Had wanted to post this yesterday There are four things that must exist for the ISY to be aware of a KPL button press. 1 KPL must have Controller link records for each button = Show Device Links Table shows these 2 PLM must have Responder link records for each button – verified visually 3 KPL must send a message when button is pressed 4 Insteon mesh network must get message to the PLM 1 & 2 have been verified. To verify 3 define a Scene with a KPL button as Controller and some other device a Responder. Does the KPL button control that device? If yes the Insteon network to the PLM is in question. If the KPL button does not control the responder either the KPL is defective or the Insteon network is in question. To verify 4 put the KPL on an Appliance cord and plug the KPL into PLM circuit.

Add a Repeat before the Notification statement and a Wait 10 minutes after the Notification statement. Repeat for as long as you want the emails to be repeated every 10 minutes. To get a different text bump a State variable by 1 each time the Wait completes. Trigger another Program when Variable reaches 3 (30 minutes) and have it send an email with a different text. It can have a similar Repeat and Wait 30 minutes. Have the first Program reset the State Variable to 0 when the Status changes to Off.

I have no problem controlling lights, monitoring and controlling bay doors in a detached garage that is 300+ wire feet from main house. There is no absolute answer to your question. Too many variables to say for sure either way. Sounds like the SmartLinc is installed at or near the gate connected your LAN with catx cable. That leaves open several questions. Are there Access Points installed for phase coupling. What else is powered from the circuit the PLM will be plugged into? If UPS and other electronic equipment on the same circuit are they isolated with a FilterLinc. That are just a few of the more obvious unknowns. Bottom line, set up the ISY with PLM and test.

Run Show PLM Links Table and look for 8 link records that look like A2 01 1D.99.7F xx xx xx A2 02 1D.99.7F xx xx xx A2 03 1D.99.7F xx xx xx A2 04 1D.99.7F xx xx xx A2 05 1D.99.7F xx xx xx A2 06 1D.99.7F xx xx xx A2 07 1D.99.7F xx xx xx A2 08 1D.99.7F xx xx xx These are the Responder link records that allow the PLM to see the button press messages from the KeypadLinc. Are you certain this is the only device that is not showing status changes?

The posted event viewer image shows no Insteon commands sent to the EZX10RF. Gives the impression the ISY is not aware of X10 codes defined in the EZX10RF. How many EZX10RF nodes exist? Was the X10 code(s) defined using the "Add X10 Device to EZX10RF" function? What level ISY is being used?

Scenes are the only thing that generate link records. Some Scenes are automatically created when a device is added to the ISY. These Scenes are necessary for the ISY to be notified of button/paddle state changes. For example, an 8 button KeypadLinc results in 8 Responder link records being created in the PLM so each button press will be picked up by the PLM. Motion Sensors generate three Responder link records in the PLM so the ISY is aware of motion, dusk/dawn and low battery events. Every node that can send the ISY/PLM a command must have a unique Responder link record in the PLM. These are required by Insteon in general, not specific to the ISY. Other link records are created to support the My Lighting Scene used by the 3 AM QueryAll Program to insure the ISY has the correct device status of all devices. Other link records are created as a result of user generated Scenes. Every device (button/paddle) the Scene controls, Controller or Responder, generates a Controller link record in the PLM. For example, Scene X has 3 Controllers and 6 Responders. There are 9 Controller link records generated in the PLM to support those 9 devices. As with most Insteon things, there are exceptions. Some devices are Controller Only. ControLinc buttons, RemoteLinc buttons, RemoteLinc2 buttons, Motion Sensor nodes, TriggerLinc nodes and others have no Responder function. Adding a RemoteLinc button as a Controller of a Scene does not generate a Controller link record in the PLM as the RemoteLinc button has no Responder function.

I ran tests on some of my 2413 PLMs many months ago and found that 992 was the maximum. Although the total memory can theoretically hold 1024 link records some of the very low memory is reserved for PLM firmware use. The solution is to reduce the number of Scenes. Combine like Scenes, eliminate Scenes that are no longer being used, etc. Once changes have been implemented a Restore Modem (PLM) has to be run to compress out the deleted link records.

Indications point to the PLM link database being full. There is no room for the KeypadLinc Responder link records. Consistent PLM record counts showing actual link record count should confirm this.

Is the PLM a 2412 or 2413? That count is invalid for a 2413. The Show PLM and Count has to be run at least 3-4 times with each producing the same number for the number to be considered accurate. EDIT: sorry, I had missed the PLM post information at the end of page 1.

Would not expect it to.

Agreed. The KeypadLinc link database was correct in the old KeypadLinc and is correct in the new KeypadLinc..

Run the PLM tests in my last post. If this is the 'only' device not reporting status changes there is a problem with the PLM link database. The Show Device Links Table from the previous device has the correct link records. The piece that is now in question is the PLM link database. Actually with a different physical device it is necessary to verify the new KeypadLinc link database with a Show Device Links Table and Compare. If that is correct for the new KeypadLinc run the PLM tests described in my previous post.

You need to add parens as indicated below. The Wiki has some good information on order of precedence which affects what statements are Anded and Ored together. Only the last statement above the Time Range was Anded with the Time Range. The other statements being Ored together operated independent of the Time Range. If ( Control 'Hardware / Family Room Light' is switched On Or Control 'Hardware / Family Room Light Slave' is switched On Or Control 'Hardware / Living Room Lighting' is switched On Or Control 'Hardware / Master Bedroom Switch' is switched On Or Control 'Hardware / Hallway Switch' is switched On Or Control 'Hardware / Kitchen Lighting' is switched On Or Control 'Hardware / Master Bedroom Switch' is switched On ) And On Mon, Tue, Wed, Thu, Fri From 3:00:00PM To 8:00:00PM (same day) Then Send Notification to 'David' content 'Home Active' Else - No Actions - (To add one, press 'Action')

The device has to be a Controller of a Scene for it to appear in the list of candidates for the In Scene parameter. Devices that are not Controllers of a Scene do not appear in the list of candidates.

Yes it can be done and it is done with a Scene. When both parameters of the Adjust Scene (In Scene and Set) are the SwitchLinc node name the Local On Level or Local Ramp Rate is changed. When the Adjust Scene specifies the Scene name or another Controller of the Scene name in the In Scene parameter and the Set parameter has the SwitchLinc name then the Responder On Level or Responder Ramp Rate is changed for the specified Controller.

The Set Options on 3.3.3 can turn the LEDs Off. Click Set Options, Query, uncheck LED backlight. It may be necessary to check the box and then uncheck the box. It does turn my FanLinc LEDs Off.

See answers in the other post with the same questions.