LeeG

Never issue a Delete Modem (PLM). Pick a SwitchLinc device that should be in a Scene. Right click on device entry, select Diagnostics | Show Device Links Table. Post the displayed popup along with new PLM Insteon address.

The PLM is new to the Insteon/ISY installation. Need a File | Restore Modem (PLM) to rebuild all the devices link databases with the new PLM Insteon address. Leave the battery powered devices alone so they will fail the Restore Modem (PLM). After all other devices have been rebuilt put one battery device into linking mode and select Write Updates to Device. When that battery device is complete take it out of linking mode . Put the next battery device into linking mode and repeat Write Update for that device.

The issue has not been resolved. Because the PLM firmware comes from SmartLabs and cannot be updated in the field the problem has to have a firm solution first.

There is a known issue with PLMs where the power supply fails (bad capacitors) with the loss of the PLM link database table. How old is the PLM? A Restore Modem (PLM) does not update individual devices unless the PLM is being replaced. If electronically skilled there is information in the forum posted by some users who have repaired replaced the failing capacitors. The PLM could have failed because of power line problems but I would be concerned that this is the first of what can be a failing PLM that either needs repair or be replaced.

If you want the Off Keypad button press to move the door the Relay has to react to an Off command. Does not matter that the button is set for non toggle On mode. When the button is turned Off, which normally does not happen with a non toggle On mode button, it changes the command sent when button is pressed. When the button is turned Off the Keypad will send an Off command when pressed.

All my KeypadLincs/Keypad Dimmer buttons are dimly lite when Off and brighter when On. The Backlight level (which applies to all buttons) can be adjusted if you have devices that do not have that combination. Suggest reading the device Owner's Manual about the device capability. The Backlight level can be set with the device or with the ISY.

The All On is not issued by the ISY. There is some overlap of Insteon messages on the Insteon network that results in a malformed Insteon message that looks like an All On message. It does not appear in the Event Viewer trace as either an inbound or outbound message. It can be generated by triggering a Program with a message from an RF only device and have the Program send a Scene On message as the initial or near initial Insteon message. The RF only device sends multiple messages so the theory is the outbound message for the Scene On overlaps the additional inbound from the the RF device, forming the All On message. Does not happen every time but generally will happen eventually. I avoid the issue by coding a Wait of 1 or 2 seconds as the first Program action if the Program is going to send a Scene On. This is not the only scenario where the overlap can happen. The latest PLMs eliminated the ability to request an All On/Off so it is not requested by the ISY. I have never seen an All On situation even running various RF only devices and two ISYs. Many folks have not. Others see the All On enough to be an issue.

As Cormacs indicted the Options popup applies to the IO Linc as a device. Some options apply to the Sensor such a Trigger Reverse and Send X10, some options apply to the Relay such as Latching, Momentary A/B/C and Momentary hold time, some apply to both such as Program lock.

It can be done with a Scene if the magnetic switch is changed. Otherwise the Sensor On when door is closed requires a program.

The momentary hold time applies to the Relay only. Use Momentary B. If Control IOLinc Senor is switched On Then Set Scene 'xxxx' Off Else where Scene xxxx has Keypad button as Responder. As door reaches closed position the Sensor turns On triggering the Program to turn Keypad button Off EDIT: added missing Control keyword to If

The pending update for the door sensor could have been there for days or weeks. Put the Door Sensor into linking mode and select Write Updates to Device.

I do not have two hold time fields. Can you post the Options display. I have never seen an I/O Linc with a Sensor timeout value.

I simply answered your question for changing the Sensor state. You can always Program to the current situation. There is a Trigger Reverse option that changes the command sent. It does not change the actual Sensor. The problem with using Trigger Reverse is the 3AM Query changes the Sensor state to its actual value, not the Trigger Reverse value.

The best way is to use a NO or dual switch (SECO-LARM SM-226L-3). The SM-226L-3 was shipped with the I/O Linc in the beginning before changing to the NC switch.

If used in a Scene the Sensor must be a Controller (cannot be assigned as a Responder). If used in a Scene the Relay must be a Responder (cannot be assigned as a Controller).

The Timeout value applies to the Relay when in one of the momentary modes. There is no timeout for the Sensor. The Sensor is based on the magnetic switch state.

blueman2 Your assumption this is a problem that applies generally would not be accurate. I've never seen an All On after years of running an ISY (actually two most of the time). RF devices send redundant commands without any knowledge of what may already be on the Insteon network. Knowing this I always add a delay in a Program triggered by RF device before issuing an Action that produces an Insteon message. Hard to prove a negative so no way to "prove" this is why I have never seen an All On.

blueman2 If not happy with disabling Programs or not able to correct the conflicts, unplug the ISY. Leave the PLM connected. Be sure to take/have a current ISY Backup before unplugging ISY. A Delete Modem (PLM) prevents using the ISY for device/Scene management.

The Program that is triggered by the change of state of the Sensor and sets the Variable value and Variable Init value should not be triggered until the Hidden Door Sensor actually sends either an On or Off message. Any Program that does something based on the state of the Sensor should check the variable value rather than the Sensor state.

The Variable is never Null. The Variable is set to the Init value when the ISY boots up. The Variable may not be accurate if the door is moved while the ISY is down but the value is never Null.

Yes. If Status triggers the Program whenever Status changes so the If will be reevaluated when still in the Wait. A Status of Off will give a False evaluation running the Else clause.

The KPL has much more RF range (150' versus 50'). However the KPL is limited by needing a power cord. I use a Mini Remote by my favorite chair where power is not available but it has Dual Band devices near by.

Michaelco What was not mentioned in this situation is that the If condition has not changed. An "If Control ..... is switched On" has no negative/False side. The Sensor turning Off does not affect the "If Control is switched On". You mentioned the posted example is not what was the running code but a simplified version. I suspect that was running version has more in the If than what has been posted. Suggest posting the real If as i think you have created an If with different conditions. EDIT: the only way to stop the posted Wait from completing with the if Control is to have it turn On again before the Wait completes.

If inside a metal box it is a waste of time. They make plastic (not actual plastic) boxes, I have been using one for more than 10 years. Much too far from house for any RF Insteon device. The non-metal box might work.

erniekraut I do not think there is an issue with the RemoteLinc as a particular device. Being that it is an older generation device it uses the older 1 byte commands. This means that some 250+ Insteon messages must flow successfully to add the RemoteLinc. There are many Insteon networks that cannot handle that volume of load. In addition the RemoteLinc is RF only so that means more than 250 Insteon RF messages must flow successfully. That requires a good Insteon network. I've added my RemoteLinc to the ISY several times using 4.2.23 with no problems. I have a good Insteon network because I have worked hard to achieve that. There are some folks who do not appreciate the amount of Insteon work that is needed to both add a RemoteLinc and define Scenes using the RemoteLinc buttons. They blame the RemoteLinc or the ISY for what is an Insteon network issue. The event trace will show the nature of the problem.