LeeG

The jack plug may be disconnecting the normal Sensor input. The fact the Green Sensor LED turns On/Off as GND is applied and removed from S (with jack plug removed) the I/O Linc Sensor is working. The I/O Linc Sensor node is following the same On/Off status as the Green LED when using the wire jumper. “I believe the sensor was not activated when I connected it.†Was this describing the use of the low voltage probe? “Should the LED status remain on when the alarm is sounding?†That is a question for Smarthome. No experience with the low voltage probe. Does the event viewer show a command from the I/O Linc Sensor when the alarm is tripped? With the plug removed what does a continuity check between the two plug connections show, both when no alarm and when alarm.

There is no option that instructs the EZX10RF to ignore multiple X10 commands. The EZX10RF does have an optional Timer on each X10 defined code that automatically sends an Off command after .5 minutes or longer in .5 minute increments. If this was used and the 30 second delay was acceptable then the Program could go back to using If Status. However, the ISY does not have support for setting the Timer. You would need another PLM for powerline communication and the Simplehomenet Utility Suite (free XP utility) to set the Timer. I would recommend compensating with ISY Program logic.

Post the event log where two commands are seen. It may just be a second group cleanup which is not triggering programs. Could be houselink sends multiple X10 commands to compensate for X10 reliability. I am not seeing to two complete inbound messages from the credit card remote. Also is the variable being used a State variable or Integer variable?

There is no need to have an intervening Off. Two X10 On commands in a row should produce two EZX10RF node On messages. If the Programs are triggered with "If Status" the status does have to change. The Program should be triggered with "If Control" so that each On command is recognized. Regarding the commands they should be identified by annotation. Post some of the event log. I can interpret.

Try Disable all Programs and turn on Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. That might show what the activity is. It’s pretty clear from the various symptoms the ISY is busy trying to handle something. I think opening a Ticket for UDI tech support would also be a good idea. Not sure what the coverage is on a weekend.

For the benefit of others who may Factory Reset a MorningLinc, the only recovery is to delete the MorningLinc from the ISY and add it back using the documented process of using Start Linking to register the device. This is due to the unique security requirements of the MorningLinc.

Not really. The fan control is on another Group which requires an additional node definition.

Check that PLM is connected Tools | Diagnostics | PLM Info. For all devices failing to communicate suggests a PLM problem or something near the PLM that is interfering with all Insteon traffic. PLM is plugged directly into an outlet, no new UPS, PC equipment. A simple test is to plug PLM into extension cord and plug extension cord in another room.

No PLM works on 220V AC. The 2412S PLM provides 12V DC. A small pluggable power supply that runs on 220V and provides 12V DC (as PLM does) will work. Very few Insteon devices are available for 220V.

The Link Management | Add Sensor to EZSnsRF option is used to add individual Dakota Alert codes and define them as nodes under the EZSnsRF. The process is described in the UDI Wiki under Devices.

I don't know what "per setup" means. Is the EZSnsRF linked to the 2456S3 with an ISY Scene or the Set button? The ISY will not see the 2456S3 turn On if the link was done with the Set button.

How was the EZSnsRF linked to the Monkey light?

There is a section toward the bottom of this forum main page dedicated to developer information. The 3.1.17 announcement has links to the latest developer information.

If done with an ISY Scene delete the ISY Scene. That will remove the link record in the RemoteLinc and the 2411T. Remember to put the RemoteLinc into linking mode by pressing the Dim/Bright buttons until the RemoteLinc LED is blinking. About 3-5 seconds. If done outside the ISY then Brian has the answer. Conceptually the RemoteLinc, as the Controller, goes into Unlinking mode first. Then the Responder, the 2411T is activated by selecting the IR code or the Set button is used, maybe both. The User Guide for both devices will have the exact details for Unlinking both devices. The User Guide for both devices can be accessed from the Smarthome sales page for each device.

easytim The Start Linking process was initiated where the PLM and ISY is listening for devices to identify themselves and the Finish button on the Start Linkiing popup was not clicked to complete the process. Reboot the ISY. If the Start Linking poipup did not display to begin with check the Current State column. This column displays the current on/Off state of devices. If this column is completely blank something is blocking the data being pushed from the ISY to the Admin Console. When the Admin Console is started and thie column is completely blank the Start Linking popup does not appear. No function in the Admin Console should be initiated when the Current State column is blank for all devices. Exit the Admin Console and start it again. Normally the Current State column will be populated the next time. Lee

In the first screen capture the Landon’s Room Controller is selected. The only slider presented is the (applied locally) value for that Controller as that is the only value that can be changed. Landon’s Room -3 is a Secondary KeypadLinc button which does not have a Ramp Rate and the On Level cannot be changed so the On Level slider for Landon’s Room -3 is not presented either. You can adjust backlight levels from a Program but it applies to all buttons on the KeypadLinc, not a single button. KeypadLinc firmware does not support setting an individual button backlight level. The Adjust Scene can be used to set a Responder On Level and/or Ramp Rate value. The Adjust Scene can be used to set the On Level (applied locally) and/or Ramp Rate (applied locally). These are the values that can be set and Adjust Scene is the mechanism the ISY has chosen to set them. The ISY could have invented some new Action statement to do the above but it would have to look like an Adjust Scene where both the Controller and Responder are identified as well as what value is being changed. The simple Set Insteon xxxx On has not means of containing a Ramp Rate value. The structure of the Standard Insteon message has existed since 2005/2006. There is no room to add a Ramp Rate value. And to the last question, that is exactly right. That single ISY Scene effectively defines three Insteon Scenes each with its own Controller, ISY PLM, Controller 1, Controller 2, and Responders. The ISY PLM Scene has both Controllers as Responders because the ISY assumes a Controller is also a Responder. Each Controller, Controller 1 and Controller 2 have one Responder.

Here is a Scene A definition with two Controllers, SwitchLinc Dimmer and KeypadLinc 8 Dimmer Button-2. There are two sets of sliders for Responder On Level and Responder Ramp Rate for each Responder. Controllers are considered Responder. There is no On Level (applied locally) or Ramp Rate (applied locally) fields when Scene A is selected. Can you post a screen capture when the Scene name is selected.

Using the example from the other topic ... Scene A definition Controller SwitchLinc 1 Dimmer Controller KeypadLinc 1 Dimmer Scene A as Controller (actually ISY PLM is Controller) Responder SwitchLinc 1 Dimmer On Level 100% Ramp Rate 0.1 sec Responder KeypadLinc 1 Dimmer On Level 80% Ramp Rate 0.2 sec SwitchLinc 1 Dimmer as Controller Responder KeypadLinc 1 Dimmer On Level 50% Ramp Rate 4.0 sec KeypadLinc 1 Dimmer as Controller Responder SwitchLinc 1 Dimmer On Level 30% Ramp Rate 2 minutes I take SwitchLinc 1 Dimmer is the device controlling the load that should ramp over 6 minutes. The Adjust Scene Action uses the Scene name "A" as the first parameter (Controller) and SwitchLinc 1 Dimmer as the second parameter (Responder) and set the Ramp Rate to 6 minutes. Issue a Set Scene A On. The SwitchLinc will turn On to 100% with a Ramp Rate of 6 minutes. The On Level (applied locally) and Ramp Rate (applied locally) values are not changed. These values can be changed by specifying the first parameter as SwitchLinc 1 Dimmer (Controller) and the second parameter as SwitchLinc 1 Dimmer. This combination changes whatever value is specified to the appropriate (applied locally) field.

You can. The ISY PLM is the Controller when the Scene name is turned On in a Program. The Adjust Scene Action can set any of the individual Responder On Level and Ramp Rates for when the Scene Name is turned On by a Program. Use the Scene Name as the Controller and whatever Responder to set as the second parameter. It might be simpler to stick with a single topic rather than having to repeat the same answer in three places.

That is the function of the device. It is considered a feature. Tap the On paddle/button and it goes to the defined On Level at the defined Ramp Rate. Hold the On paddle/button and it ramps to full bright. Hold the Off paddle/button and it Ramps to full Off. This allows the device to be preprogrammed to some On Level but overridden by the switch operator.

There are Start Manual Change Dim/Bright commands which correspond to pressing and holding a paddle/button and a Stop Manual Change command which stops the Dim/Bright ramp which corresponds to releasing the paddle/button. The Adjust Scene can adjust a Scene Controller/Responder combination. One way would be to use Adjust Scene Action to set the Responder Ramp Rate to the 6 minute Ramp Rate when the Controller is the ISY PLM (Scene name). Then turn the Scene On to 100% which will occur over a 6 minute period. The various On Level and Ramp rate combinations are spelled out in my earlier post.

The Insteon Direct (for direct device control) On command has a placeholder for On Level, there is no placeholder for Ramp Rate. EDIT: when a device paddle/button is pressed the device always issues a Scene (Group) command. A device never issues a Direct command as a result of pressing a paddle/button On/Off. Much of Insteon is built around Scenes as that is all that can be done without automation.

There is no concept of Scene On Level or Scene Ramp Rate. For each separate Controller in a Scene all the Scene Responders can have unique On Level and Ramp Rate values. Scene A definition Controller SwitchLinc 1 Dimmer Controller KeypadLinc 1 Dimmer Scene A as Controller (actually ISY PLM is Controller) Responder SwitchLinc 1 Dimmer On Level 100% Ramp Rate 0.1 sec Responder KeypadLinc 1 Dimmer On Level 80% Ramp Rate 0.2 sec SwitchLinc 1 Dimmer as Controller Responder KeypadLinc 1 Dimmer On Level 50% Ramp Rate 4.0 sec KeypadLinc 1 Dimmer as Controller Responder SwitchLinc 1 Dimmer On Level 30% Ramp Rate 2 minutes The reaction of any given Responder is based on which device (ISY PLM, KeypadLinc, SwitchLinc) is the Controller. Define your Scene in terms of which devices are Controllers versus Responders (if any) using actual node names. The Adjust Scene is setting a specific Responder On Level or Ramp Rate for the selected Controller.

The name change has been reported in this topic viewtopic.php?f=25&t=7695 All buttons are affected by change from Toggle to Non-Toggle mode, per RemoteLinc2 User Guide.

Unfortunately nothing you initiated from the Admin Console means anything. The ISY knows what command it issued and sets the Current Status column accordingly. Plus the commands used are Insteon Direct commands. Insteon Direct commands do not use link records. As I have stated before. What I needed to know is how many devices show a state change when you push the load control button/paddle on the device itself. This action uses Insteon Group commands which are totally dependent on link records both in the device and in the PLM. It really was relevant. Oh, by the way, a SwitchLinc is a single paddle device which requires one link record in the device and one link record in the PLM. A KeypadLinc is a multi-button device which requires from 5 to 8 link records in the device and the same number in the PLM. It would have been easier to look for link records when only one needs to be found. It will be important to provide the next person who tries to help with accurate information to the questions they ask. You do not have the Insteon knowledge or experience to substitute your knowledge for theirs. Sorry I was not able to find the root cause. Good luck.