LeeG

MobiLinc will drive a Scene rather than a Direct command if device is in a Scene but that may be limited to the device being a Controller of the Scene. A Direct On from the Admin Console always turns the Relay On. A Scene can be defined with the I/O Linc Relay as a Responder and turn the Scene On/Off with the Admin Console. That same Scene can be controlled from MobiLinc.

A Direct On command to the I/O Linc Relay is required to turn the Relay On. A Direct Off will turn the Relay Off but that is usually not required because any of the Momentary modes turns the Relay Off. Only Scene Relay On/Off commands are managed by which Momentary mode is used.

The requirement that Notify have Subject and Body has been noted by UDI in various topics.

Here is an example of what needs to be coded in program If Control '2B.09.AE.1 - Door Sensor' is switched On And Control '2B.09.AE.1 - Door Sensor' is not switched Off Then Send X10 'A1/On (3)' Wait …. Else Send X10 'A1/Off (11)' When the door is opened the Then clause is driven. It would have Wait and whatever you want to happen if no Off (door closed) is received. When the Off is received the Else clause is driven. Assuming the Off is sent before the Wait completes in the Then nothing past the Wait happens. The X10 messages are a simple way to see which clause is driven. Not needed in actual implementation.

The event trace is of the Heartbeat signal. It would not trigger If Control nor If Status. My error for not catching that sooner. Fri 06/13/2014 15:46:06 : [iNST-SRX ] 02 50 2B.01.E7 00.00.04 C7 13 04 LTOFFRR(04)

Is the event trace of the door opening or closing? Is the Hidden Door Sensor set for 1 or 2 node operation (has no affect on how many nodes the ISY defines when adding to the ISY)?

What type of device is monitoring the door? The trace shows it issued an Off command ]Fri 06/13/2014 15:46:06 : [iNST-SRX ] 02 50 2B.01.E7 00.00.04 C7 13 04 LTOFFRR(04) which would not trigger the Program when using If Control and would drive the Else clause if using If Status (assuming the device was originally On)

The suggested NO/NC magnetic switch mounts at the top or bottom, your choice. I have mine mounted at the top of both doors. Turn On Trigger Reverse I/O Linc option and do whatever you want to when the 3AM Query changes the Open/Close state of the garage door.

From the ISy User Guide If both the MEM and ERR LEDs are blinking, the ISY is unable to communicate with your Ethernet network. Please check all cable connections, try rebooting your router or switch, and ensure that you have a DHCP server available. Make sure the network and PLM cables are in the correct plugs.

The message means the PLM is not able to talk to the LampLinc. There are various possibilities in a new Insteon install. Some areas to look at .... No Access Points to couple the 2 120v legs. PLM is plugged into a surge/noise power strip Other electronics powered from the same outlet as PLM and not isolated with a FilterLinc

The old KPL is the device where the 'Replace xxxx with' command is selected. The new KPL is then chosen. If the new KPL definition remains and the old KPL was deleted it sounds like the 'Replace' command was applied to the new KPL rather than the old one. The only solution is to restore an ISY Backup and repeat the 'Replace' command but against the old KPL. Note that the ISY never physically accesses the old KPL because it is assumed to be defective and not operational. In fact the new KPL may have physically replaced the old KPL.

If Time is Sunset And Status 'kpl vacation button' is On Then Set 'living room light' 50% Else If Time is Sunset And Status 'kpl vacation button' is Off Then Set 'living room light' 100% Else Cannot be done with single Program using Else as switching the kpl button drives the Else when not sunset.

The "Ramp Rate (applied locally)" for an individual device applies when that individual device is turned On/Off with a Direct command or operated manually. For this Scene Scene1 Switchlinc1 - Controller Switchlinc2 - Controller Switchlinc3 - Controller there are 4 sets of Ramp Rate values that can be assigned which are independent of each other. That is, each Controller in an Insteon Scene has a unique set of Responder Ramp Rate values. For Scene1 the Controller is the PLM. When Scene1 is turned On/Off with a Program for example each Switchlinc as a Responder has a unique Ramp Rate. Scene1 - PLM is Controller Switchlinc1 as Responder to PLM (Controller) can have a unique Ramp Rate - Ramp Rate 0.2 seconds Switchlinc2 as Responder to PLM (Controller) can have a unique Ramp Rate - Ramp Rate 1 minute Switchlinc3 as Responder to PLM (Controller) can have a unique Ramp Rate - Ramp Rate 2 minutes When Switchlinc1 is the Controller Switchlinc2 and Switchlinc3 have a different set of Ramp Rate values Switchlinc1 - Controller Switchlinc2 as Responder to Switchlinc1 can have a unique Ramp Rate - Ramp Rate 0.4 seconds Switchlinc3 as Responder to Switchlinc1 can have a unique Ramp Rate - Ramp Rate 0.8 seconds When Switchlinc2 is the Controller Switchlinc1 and Switchlinc3 have a different set of Ramp Rate values Switchlinc2 - Controller Switchlinc1 as Responder to Switchlinc2 can have a unique Ramp Rate - Ramp Rate 3 seconds Switchlinc3 as Responder to Switchlinc2 can have a unique Ramp Rate - Ramp Rate 4 seconds

The If Time is Sunset is True for only 1 second of time, exactly Sunset. To cover a range of time, say from Sunset to Sunrise then use If From Sunset To Sunrise (next day) And the violation condition ....... or If From Sunset For 2 hours And the violation condition .......

The difference is you indicated the 99i is using a static IP. The 994i is using DHCP. Once the router assigns an IP address from the DHCP pool so that the 994i can be accessed another different static IP can be assigned to the 994i. The MEM and ERR LEDs will indicate when the 994i has been able to access the router.

The MEM and ERR LEDs blinking indicates the 994i cannot communicate with the router. Cannot login to the 994i without access to the network. Check cables and the router for DHCP. DHCP is not working as thought.

Great news. Thanks for taking the time to post back the results.

rob2k77 Is the PLM a 2413S or the old no longer sold 2412S PLM?

That option cannot be set under the ISY. Also I think that blinks the Set button, not the KPL button. If it is in non-toggle On mode and does not turn On after blinking twice something in your implementation is turning it Off. What is determining whether the button is On or Off as non-toggle On should leave the button On.

Use Link Management | New INSTEON Device. Enter the Insteon address of a hidden door sensor, Name of your choice, and use Auto Discover. BEFORE clicking Ok put the door sensor into linking mode, then click Ok. Insure the door sensor is near the Dual Band PLM.

Since the 994i is expecting DHCP set up the router to allocate an IP address to the DHCP request.

Blinking twice and turning Off indicates the button is in non-toggle Off mode. What turns the button LED On?

Not clear from the Log why the devices are changing state. For the ISY to mark the change the device signaled the change or a Scene was run that changes the devices.

Can you post a few dozen Log entries immediately before 16:20:39

The Secondary KPL buttons can be used to brighten/dim the SwitchLincs just like Main A. Simply press and hold the respective button until level achieved.