LeeG

The basic logic of the Program is correct. First check if a Save is pending for the Program. The Program Icon will have a Green arrow on top of it at 4.0.5 if a Save is pending. Was the Copy to clipboard function used to copy the Program to the forum. Second check the Current State column for the I/O Linc Sensor node. Does it show On when the garage door is open and Off when the garage door is closed.

"If the if statment begins "if status" the ISY looks for the status command." The explanation by Xathros is spot on as usual for the If Control. If Status is not looking for a Status command. If Status is checking the value that is displayed in the Current State column which is the Status of the device as the ISY knows it. If Status triggers the Program each time the Current State value changes (unlike If Control which triggers only on the specific command) which means an If Status will run the Then clause when the IF is True and the Else clause when the IF is False. Again, the Current State value must change for If Status to trigger the Program.

If no Insteon traffic was received during the Show PLM Links Table display the only explanation I have for the varying numbers is a defective PLM. However, it only takes a single message from a thermostat for example to affect the Show display. If you can trace a Show PLM Links Table and send the trace file to lwgwork@embarqmail.com I'll take at the trace. I'm inclined to think Insteon traffic is affecting the Show results. The PLM can be Factory Reset (NOT the ISY) which will physically reset the link database to zeros. Then a Restore Modem (PLM) to rebuild the link database. Run Help | About and verify the UI line indicates 4.0.5.

Any device that is not I2CS (except the MorningLinc which has special security from the beginning) can be controlled from the outside given enough time. Keep in mind Insteon RF range is limited. Could just plug into an outside outlet and have direct powerline access. The I2CS rollout started April 2012 taking several months before all device types had the new I2CS firmware. There have been some folks who put the I/O Linc on an ApplianceLinc so power can be removed from the I/O Linc. RF garage door openers have the same exposure although much less now that most remotes use rolling security codes. An I2CS device must be linked with the PLM before that specific device can be controlled from that PLM. An I2CS device rejects control commands from a PLM that is not known to the device.

The ISY does not support a PLM (USB or Serial) as an independent device. That is why the message when attempting to add it to the ISY as a device. The PLM should rebroadcast powerline traffic to RF and vise versa without adding it to the ISY. Also no need to link the PLM to device. The link would be necessary only for the PLM to pass out Insteon traffic to an application. Yes, a neighbor could do as you suggest until I2CS devices started shipping in March 2012. The I2CS protocol will not allow a PLM to control a device where the PLM is unknown to the device.

LTMCON(xx) is Light Manual Change On LTMCOFF(xx) is Light Manual Change Off These occur when a button/paddle is pressed, held, then released to Dim or Brighten a load. The LTMCON occurs when the paddle/button is pressed. The LTMCOFF occurs when the paddle/button is released. Thu 08/15/2013 11:31:48 PM : [iNST-SRX ] 02 50 1D.38.00 00.00.01 C3 17 01 LTMCON (UP) Thu 08/15/2013 11:31:51 PM : [iNST-SRX ] 02 50 1D.38.00 00.00.01 CB 18 00 LTMCOFF(00) LTOFFRR(xx) is Light Off Response LTONRR(xx) is Light On Response Thu 08/15/2013 11:26:27 PM : [iNST-ACK ] 02 62 13.08.1B 0F 11 FF 06 LTONRR (FF) Thu 08/15/2013 11:26:27 PM : [iNST-SRX ] 02 50 13.08.1B 22.80.0B 2B 11 FE LTONRR (FE) The first trace entry is the PLM Echo 02 62 of the On command The second trace entry is the 02 50 device ACK to the On command

As TJF1960 has said this has nothing to do with the I/O Linc Relay mode (latching versus momentary) as you are not using the Relay part of the I/O Linc nor any of the other I/O Linc options. For the I/O Linc to be sending repetitive Sensor On commands the photo sensor is cycling its power to the I/O Linc Sensor input such that the I/O Linc Sensor is turning On and Off. Watch the Green LED on the I/O Linc where the wire connections are made. What photo sensor is being used? Manufacturer, model, how is the photo sensor connected to the I/O Linc Sensor input and how is the photo sensor powered? The problem is with the photo sensor chosen or how it is connected to the I/O Linc Sensor input.

One of three possibilities The PLM is full because of duplicates and out dated links Solution is a Restore Modem (PLM) The PLM is full of active valid links which requires Scene management to reduce the number of active valid link records. A Show PLM Links Table followed by a Count will show how many link records exist in the PLM. The Show processing is valid only when NO Insteon traffic reaches the PLM while the Show is running. Otherwise the displayed link records will be falsely high or low. This can be differentiated from the first possibility by doing a Restore Modem (PLM) and not having the link count drop below 992 which is the max count for a 2413 PLM. The Show PLM Links Table and Count should be done 3-4 times to insure the same Show and Count results. The PLM is defective and will not accept new link records.

Sorry, yes calibration is setting the Offset. Excerpt from the user guide Temperature Calibration The top left number (77 in example) is the current reading according to the temperature sensor. The top right number (14 in example) is the current offset (represents 1.4). These numbers can change while this screen is displayed even though the primary temperature does not change. They are floating point calculations.

The thermostat has an Offset for temp and an Offset for Humidity. From the posts of folks who have looked at the Offset values some thermostats are being received with the Offset values set. The assumption is these are from testing before the units are shipped. Just as devices arrive with link records in the link database. Those who have posted back results have indicated once the Offsets were reset or adjusted the temp reading is correct.

The first 4 trace entries are from your last post. Note the 15 on the end which indicates the add of the responder link record to the PLM did not work. Tue 08/13/2013 02:30:37 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 1C 4E C9 00 12 37 15 Tue 08/13/2013 02:30:39 PM : [MNG-LNK-RSP ] 02 6F 41 A2 03 1C 4E C9 00 12 37 15 Tue 08/13/2013 02:30:40 PM : [MNG-LNK-RSP ] 02 6F 41 A2 04 1C 4E C9 00 12 37 15 Tue 08/13/2013 02:30:42 PM : [MNG-LNK-RSP ] 02 6F 41 A2 05 1C 4E C9 00 12 37 15 The next 4 trace entries are from a trace I just ran of adding an 8 Scene RemoteLinc 2 after deleting it from the ISY. Note the 06 on the end which indicate the add of the responder link record to the PLM was successful. Wed 08/14/2013 12:00:48 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 1C 27 E3 00 12 36 06 Wed 08/14/2013 12:00:49 PM : [MNG-LNK-RSP ] 02 6F 41 A2 03 1C 27 E3 00 12 36 06 Wed 08/14/2013 12:00:52 PM : [MNG-LNK-RSP ] 02 6F 41 A2 04 1C 27 E3 00 12 36 06 Wed 08/14/2013 12:00:55 PM : [MNG-LNK-RSP ] 02 6F 41 A2 05 1C 27 E3 00 12 36 06

Is "Catch up schedules at restart" checked in Configuration? (separate from run at startup)

No Insteon traffic must reach the PLM during the Show PLM Links Table execution. Insteon traffic reaching the PLM during the Show process will result in false High or Low counts.

The 1011 Icon indicates the ISY has pending updates for the motion sensor. Each time the Admin Console makes a change it looks through the nodes to see if any others have pending updates. Put the Motion Sensor into linking mode, select Write Updates to Device.

The thermostat User Guide describes the process of calibration of temp and humidity.

This logic is not correct. The If Control xxxx is switched On is looking at the On command coming from the I/O Linc Sensor which occurs when the door is physically moving, either to closed position or opening depending on the type of magnetic switch used and whether Trigger Reverse is used. The Action taken is to turn On the I/O Linc Relay which initiates door movement again. if controle garage-door-sensor is switched on then set garagedoor open-close on (the relay) If Sensor On is door opening then turning the Relay On will stop the door movement as part of the door safety system. Same thing happens if the manual door switch is pressed to initiate door movement and the manual door switch is tapped again. The door stops.

1024 Scenes for Pro

Don't see 4 Programs versus 16 Scenes. Each KPL button (A,B,C,D) in each room would drive a different Program which makes 16 Programs.

If you want to use an Off command that cannot turn Responders On to any level with a Scene.

It can be done with a Scene. Define the ISY Scene with the KeypadLinc button as Controller and whatever devices should be responders. Click on the Red KeypadLinc button node name below the Scene name and set the various Responder On Levels to the desired values.

Program execution speed compared to X10/Insteon traffic speed combined with the same trigger condition happening before a Program completes is rare to the point that it is not normal for a program to disable itself. The capability is there if needed but not normally done.

The “ISY†folder name is what the 994i starts with. If a 99i backup file is restored onto the 994i the “My Lighting†folder exists from the 99i. They are the same. There are never multiple occurrences of the same Program executing. The running variant is terminated when the Program is triggered again (assuming the Program has not disabled itself to prevent being triggered again). The If Program xxx True/False is testing the state of the last If evaluation. Before variables one use of the True/False state of a Program was as a binary flag. It would not be used to test the True/False state of itself.

I suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Delete the Mini Remote, add it back and post the event trace showing both the delete and add. It still sounds like the PLM does not have the responder link records needed for it to receive messages from the Mini Remote.

I deleted and added back a Mini Remote under 4.0.5 on my 994i successfully so it is not a systemic problem with either. Is there anything common about the 994i's?

That is exactly right. Programs that can execute concurrently should not be updating the same resource. It would require an Enqueue/Dequeue function to serialize access to the resource which does not exist in the ISY.