LeeG

Insteon Direct commands CANNOT turn Secondary KPL buttons On/Off because Insteon Direct commands have no means of identifying which KPL button. When a KPL receives a Direct On/Off command it assumes the Primary Load Control button is being acted upon. Move the Set Scene 'xxxx' Off after the statement that turns the Fan Motor Off. Also add a 2 second Wait before the Set Scene 'xxxx' Off. I suspect the KPL is still processing the button press when the Scene Off is issued.

Post the Program and describe the ISY Scene that has the KPL button as a Responder. After a Factory Reset a Restore Device on the KPL must be done to rebuild the link database.

If Status 'node name' is checking "Current State" of the node. If Program 'program name' is checking True/False "Status" of the named Program. When the If evaluates as True the Then clause runs and the Program "Status" is True When the If evaluates as False the Else clause runs and the Program "Status" is False

Variables have not changed the way Programs work as far as Then/Else and True/False. Before Variables Programs were often used as binary flags (True versus False). That is no longer necessary with Variables but is not precluded. There would have been a significant impact to existing Programs if Variables altered the way Programs have worked for years.

It does not matter as far as the Scene turning the button LED On. It will affect what your Programs are looking for as far as a Trigger condition but does not matter as far as turning the button LED on. You could set the button to non-toggle On mode so the button LED will be On as a result of pressing the button. Then the Program that turns the Fan Motor Off would turn the button Scene Off to turn the button LED Off.

Define an ISY Scene with KPL button E as Responder. In the Programs that are cycling through the Fan Motor speeds, for all but the Program that turns the Fan Motor Off, turn the Scene On that has button E as Responder. That will turn the KPL button LED On. The Program that turns the Fan Motor Off should turn the Scene Off to insure the button LED is Off when the Fan Motor is Off.

No better than the standard outlet did. Maybe not as long with the electronics due to the high moisture level that must exist so close to the ground. I have had an Icon switch installed in a water tight enclosure with a foam sealed hinged cover for many years. However, it is mounted a good 6' above water level (mounted on a dock) with good air circulation around the entire box.

"if a switch that ISY had previously recognized as responding (no red exclamation point next to it) fails to respond to a scene command generated by another switch, ISY will assume it did respond." Yes. The Responder normally sends an ACK but only back to the Controller device (different when PLM is Controller of Scene). The Controller device would know that all the retries were unsuccessful (some devices blink when a responder fails to ACK) but none of that information is passed on to the PLM. The Insteon protocol makes no allowance for notifying other Responders (the PLM is a Responder to the Scene) that one of the Scene Responders failed to ACK. The ISY sees the Controller turn On/Off, that it is a Controller of Scene xxxx so the ISY marks the Scene xxxx Responders as though the Scene was successful.

In Insteon when a Controller other than the PLM turns a device On/Off as a Responder the ISY has no direct information that the Responder actually reacted. The ISY normally assumes it did based on the Scene definition and marks the Responder accordingly but once the Responder has been marked as not Responding the ISY needs a positive indication the device is working.

Switching the Neutral would be against code. Would not be done by professional electrician.

Find any of the many posts done by Michel. At the bottom is a link to open a ticket.

The first event trace when the firmware was displayed as v.00 shows the command was not accepted because the device is expecting an extended command when a standard command was issued. I took this to be an issue with the ISY not knowing the firmware level but it could be the Admin Console does not yet support an I2CS Mini Remote. Suggest opening a ticket with UDI tech support to get a definitive answer.

Click Help | About and verify the Firmware and UI lines both indicate 4.0.5.

The Insteon network is not working as it should. The response in Red is missing from your trace. Suggest moving the Mini Remote closer to the PLM. Tue 08/20/2013 09:13:48 PM : [iNST-TX-I1 ] 02 62 1C 27 E3 0F 10 00 Tue 08/20/2013 09:13:48 PM : [iNST-ACK ] 02 62 1C.27.E3 0F 10 00 06 ID-REQ (00) Tue 08/20/2013 09:13:48 PM : [iNST-SRX ] 02 50 1C.27.E3 22.80.0B 2B 10 00 ID-REQ (00) Tue 08/20/2013 09:13:48 PM : [std-Direct Ack] 1C.27.E3-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Tue 08/20/2013 09:13:49 PM : [iNST-SRX ] 02 50 1C.27.E3 00.12.36 8B 02 01 (01) Tue 08/20/2013 09:13:49 PM : [std-Broadcast] 1C.27.E3-->00.12.36, Max Hops=3, Hops Left=2

I believe the problem is the ISY does not know the firmware level of the Mini Remote. Delete the Mini Remote from the ISY. Use New INSTEON Device, enter the Insteon Address, Name of choice, and Device Type set to default Auto Discover. Be sure Mini Remote is in linking mode before clicking Ok on New INSTEON Device. That should result in the Mini Remote being added and the ISY will know the firmware level so the appropriate commands are issued.

My Mini Remotes are identified as 2444A2 with v.36 firmware by the Admin Console. What does the Admin Console show for the firmware level of the Mini Remote? Suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Change the LED and Beep check boxes and post the trace. The LED is visually apparent because the Green LED does not blink. The Beep is "very low" in volume and could be easily missed.

I used this Program on 4.0.5 as a test vehicle. I am seeing the Program evaluate True with a Run (If). I don’t like Notify for the result indication. Too many possible issues. X10 statements are good as they do not require the X10 device and they generally have no adverse affect on the network. If Status 'SwitchLinc DB Dimmer v40' is not Responding Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' Issued a Query here with device not powered. Query issued three times. After third failure Program is triggered because of Status change and program evaluates as True (A1/On) Tue 08/20/2013 01:10:30 PM : [iNST-TX-I1 ] 02 62 1D 38 00 0F 19 00 Tue 08/20/2013 01:10:30 PM : [iNST-ACK ] 02 62 1D.38.00 0F 19 00 06 LTSREQ (LIGHT) Tue 08/20/2013 01:10:39 PM : [iNST-TX-I1 ] 02 62 1D 38 00 0F 19 00 Tue 08/20/2013 01:10:39 PM : [iNST-ACK ] 02 62 1D.38.00 0F 19 00 06 LTSREQ (LIGHT) Tue 08/20/2013 01:10:47 PM : [iNST-TX-I1 ] 02 62 1D 38 00 0F 19 00 Tue 08/20/2013 01:10:47 PM : [iNST-ACK ] 02 62 1D.38.00 0F 19 00 06 LTSREQ (LIGHT) Tue 08/20/2013 01:10:54 PM : [ 1D 38 0 1] ERR 1 Tue 08/20/2013 01:10:54 PM : [ X10] A1 Tue 08/20/2013 01:10:54 PM : [X10-RSP ] 02 63 66 00 06 Tue 08/20/2013 01:10:54 PM : [ X10] A1/On (3) Tue 08/20/2013 01:10:55 PM : [X10-RSP ] 02 63 62 80 06 Click Run (If) using Admin Console. Program evaluates to True since device is still Not Responding (A1/On) Tue 08/20/2013 01:11:07 PM : [ Time] 13:11:11 0(0) Tue 08/20/2013 01:11:07 PM : [X10-RSP ] 02 63 66 00 06 Tue 08/20/2013 01:11:07 PM : [ X10] A1 Tue 08/20/2013 01:11:07 PM : [ X10] A1/On (3) Tue 08/20/2013 01:11:08 PM : [X10-RSP ] 02 63 62 80 06 Issued another Query. Still times out because device not powered but this time program is not triggered because no change in device Status. Tue 08/20/2013 01:11:58 PM : [iNST-TX-I1 ] 02 62 1D 38 00 0F 19 00 Tue 08/20/2013 01:11:58 PM : [iNST-ACK ] 02 62 1D.38.00 0F 19 00 06 LTSREQ (LIGHT) Tue 08/20/2013 01:12:07 PM : [iNST-TX-I1 ] 02 62 1D 38 00 0F 19 00 Tue 08/20/2013 01:12:07 PM : [iNST-ACK ] 02 62 1D.38.00 0F 19 00 06 LTSREQ (LIGHT) Tue 08/20/2013 01:12:15 PM : [iNST-TX-I1 ] 02 62 1D 38 00 0F 19 00 Tue 08/20/2013 01:12:15 PM : [iNST-ACK ] 02 62 1D.38.00 0F 19 00 06 LTSREQ (LIGHT)

Volume. Number of point and shoot cameras sold versus number of surveillance cameras sold. One can buy PLMs in units of 1000 much cheaper per unit than an individual PLM.

"If the PLM can control an insteon device without a link table in the device authorizing that device to do so isn't that a security problem?" A pre I2CS device does not need a link between the PLM and the device for the PLM to control the device. The I2CS rollout started April 2012 covering several months for the firmware to be updated in the various device types. "I am testing with a motion sensor so maybe I need to wake it up to get a response..." Battery powered devices go to sleep (turn Off the RF circuitry) to conserve battery life. They must be put into linking mode with the Set button before the device can be accessed for configuration or link changes. "But i would have thought the PLM would respond with it's table of links?" The PLM could have been factory reset by accident, lost its link database for some other reason. A Restore Modem (PLM) will rebuild the PLM link database.

oberkc You are absolutey right, i was wrong. Anding two different devices or two different commands for the same device where NOT is not used results in a False evaluation. Thank you for correcting a long held and wrong conclusion.

There is a Show Device Links Table function which can be used to display the link records in a device. When the display completes the Compare button will compare what was retrieved from the device against what the ISY thinks should be in the device. Insteon has two general types of commands, Direct and Scene (Group). Individual devices cannot send Direct commands (except PLM). Leaving the PLM out of the discussion for now a Scene is needed when device A as Controller is controlling device B as a Responder. An application like the ISY can use a PLM to send Direct commands to control a device. Direct commands do not use link records (Scene). When a device is added to the ISY links (Scenes) are established between the device and the PLM so the ISY will be aware of local changes to the device (paddle/button/toggle, sensor, etc) occur. These links are in addition to any user created Scenes. Serial Outbound messages issued by the ISY do not contain the PLM address as the PLM adds its address when the message is sent on the Insteon network. Inbound messages usually do have the PLM address. The exception is a Group Broadcast message which is not sent to any specific device. There is document on insteon.net web site insteondetails.pdf that discusses the details of Insteon which you may find useful

When checking for multiple commands using If Control the logical definition is to Or them together since it is impossible to have more than one command flowing from a device at a time. If Control 'xxxxx' is switched On Or Control 'xxxxx' is switched Fast On Then The following can never be True. If Control 'xxxxx' is switched On And Control 'xxxxx' is switched Fast On Then

There is no functional difference between the two items. SmartLabs started using the xxxx-yyy item number format for RF devices where yyy represents the country (frequency) where they operate.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Put the TriggerLinc into linking mode by pressing the Set button until LED blinks continuously. Use New INSTEON Device, enter Insteon address from label on printed circuit board, Name of choice, Device Type as default Auto Discover. Post the event trace.

"The sensor shows on when closed and off when open. Do I change that with Trigger Reverse?" Using Trigger Reverse does result in the 3 AM problem. If the only issue is the posted Program simply change the check to Off rather than On. Most users prefer On to indicate the door is open. To achieve this the best solution is change the magnetic switch from NC to a NO variant. "I have "LED on tx" checked and "Momentary C ---" selected. Momentary hold time is 2 seconds." The LED on Tx causes the LED on the side of the I/O Linc to blink when there is Insteon traffic. Makes no difference to the functioning of the I/O Linc. Momentary C relates to what Scene commands will operate the I/O Linc Relay. There has not been a discussion about how the I/O Linc Relay is being used to open/close the door so use momentary C if it produces the desired results.