LeeG

That If (besides being syntactically incorrect, always best to post the actual Program) requires KPL button A to be On at 6:30 AM. Turning the button On after 6:30 AM does not trigger the Then clause. An If Status "kplbuttonA" is On is the correct way of checking if a button is On. If that does not work run Tools | Diagnostics | Event Viewer at LEVEL 3 to see if an event is traced when KPL button A is turned On. Also the button Current State column should cycle from Off to On to Off as the button is turned On/Off.

The Query Relay reports the status of all relays. The value in cmd2 (0x86) is a bit map which shows all relays starting with Relay 1 in the right most bit. In this response Relay 2,3 and 8 are On. Thu 03/13/2014 05:00:30 PM : [iNST-TX-I1 ] 02 62 23 8D 7C 0F 4F 02 Thu 03/13/2014 05:00:30 PM : [iNST-ACK ] 02 62 23.8D.7C 0F 4F 02 06 IOCTL (QUERY) Thu 03/13/2014 05:00:30 PM : [iNST-SRX ] 02 50 23.8D.7C 24.1B.FE 2B 4F 86 IOCTL (86) Thu 03/13/2014 05:00:30 PM : [std-Direct Ack] 23.8D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Thu 03/13/2014 05:00:30 PM : [ 23 8D 7C 1] ST 0 EDIT: a KeypadLinc works the same. The ISY sends a Query command for the first node only. The response from the KeypadLinc is a bit map reflecting the state of all the KPL buttons.

Post the Program. Right click on Program name, select Copy to Clipboard, paste to forum post. An If Control 'door Opened' is switched On should work. Make sure the Program is Enabled and not in a Folder that is False.

There needs to be more Adjust Scene statements. The two existing Adjust Scene statements affect what happens if the Basement Playroom Lights Scene is used in a Program where the PLM is the Controller. Several more Adjust Scene statements are needed to adjust what happens when either of the two SwitchLincs are the Controller. Also the On Level and Ramp Rate that should take effect at 10 PM has to be set where the ?? are now. Then In Scene 'switchlinc1' Set 'switchlinc1' 40% (On Level) In Scene 'switchlinc1 'Set 'switchlinc1' 4.5 Sec (Ramp Rate) In Scene 'switchlinc1' Set 'Basement Play Light Relay' 40% (On Level) In Scene 'switchlinc1' Set 'Basement Play Light Relay' 4.5 Sec (Ramp Rate) In Scene 'switchlinc2' Set 'switchlinc1' 40% (On Level) In Scene 'switchlinc2 'Set 'switchlinc1' 4.5 Sec (Ramp Rate) In Scene 'switchlinc2' Set 'Basement Play Light Relay' 40% (On Level) In Scene 'switchlinc2' Set 'Basement Play Light Relay' 4.5 Sec (Ramp Rate) Else In Scene 'switchlinc1' Set 'switchlinc1' ??% (On Level) In Scene 'switchlinc1 'Set 'switchlinc1' ?? Sec (Ramp Rate) In Scene 'switchlinc1' Set 'Basement Play Light Relay' ??% (On Level) In Scene 'switchlinc1' Set 'Basement Play Light Relay' ?? Sec (Ramp Rate) In Scene 'switchlinc2' Set 'switchlinc1' ??% (On Level) In Scene 'switchlinc2 'Set 'switchlinc1' ?? Sec (Ramp Rate) In Scene 'switchlinc2' Set 'Basement Play Light Relay' ??% (On Level) In Scene 'switchlinc2' Set 'Basement Play Light Relay' ?? Sec (Ramp Rate)

A Set Scene xxxxx On sends one command that is not device specific. There are no ACKs and no retries. Each device in the Scene has a single chance to react to the Scene On. Any noise, any signal reduction can interfere with a device(s) receiving that single message. With the SwitchLinc turning On the PLM to garage path sounds good. The path between the PLM and the KPLs sounds problematic. Perhaps the KPLs are on the opposite 120v leg and phase coupling has an issue or something on the circuit that is powering the KPLs. A Set Scene will often be the failure seen when there are marginal problems getting to one or more devices.

It would if that is all that was happening. The Variables are being changed such that the Program is triggered twice. The test you ran confirms a Notify sends one email. The only way for two emails to be sent is to trigger the Program twice. That means that the Variables are both set to 1 two times.

If looking to do something at Sunset if the device is Off .... If Time is Sunset And Status 'SwitchLinc Dimmer' is Off Then Set 'SwitchLinc Dimmer DB' On Else - No Actions - (To add one, press 'Action')

See this Wiki link for process of resetting userid/password http://wiki.universal-devices.com/index ... d/Password

Look at the other Programs that are setting the Variables. The Variable combination must be set to the state that drives the Then clause twice to get two emails.

It is not a question of overload. Some CFLs generate enough interference when powered that an Off command is not functional. Insert incandescent bulbs as a test.

QueryAll If Time is 3:00:00AM Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action') The Scene name in this QueryAll Program is My Lighting as this system was generated from an old 99i backup. I think the Scene under Network on a 994i built from scratch would be Set Scene 'ISY' Query

A device that will consistently turn On and consistently has issues turning Off is often related to the load the device is controlling. The load generates noise/attenuation that interfers with receiving the Off command. I believe all the Insteon devices have nolde .1 Many have more than that single node but they all have node .1

There is another possibility, the EZIO8SA has lost a link record. The Query commands are showing good communication between the PLM and the EZIO8SA. If the EZIO8SA did not know it should respond to Scene 00.00.1F because the link record was missing there would be no errors since there is no ACK. The PLM has the link for Scene 00.00.1F, otherwise the Scene On would have been rejected. Could try a Scene Test for that Scene. The PLM issues different commands for a Scene Test which do require ACKs. If the EZIO8SA fails to react the Scene Test will show a failure for that device.

A Scene On/Off in the ISY is a single command that is not ACKed by the Responders. Much like an X10 command goes out on Insteon network without any ACKs. The 00.00.1F Scene On appears 8-9 times in the event trace and it never actually causes the Relay to turn On. None of the Query Relay responses shows Relay 5 On anywhere in the trace. Fri 03/14/2014 02:46:28 PM : [iNST-TX-I1 ] 02 62 23 8D 7C 0F 4F 02 Fri 03/14/2014 02:46:28 PM : [iNST-ACK ] 02 62 23.8D.7C 0F 4F 02 06 IOCTL (QUERY) Fri 03/14/2014 02:46:28 PM : [iNST-SRX ] 02 50 23.8D.7C 24.1B.FE 2B 4F 01 IOCTL (01) Only Relay 1 shows as On. Hard to know if the flood of Query commands is the issue or Scenes are not working well going to the EZIO8SA. Could put a Wait of a few seconds in the Repeat loop to see if Relay 5 every shows On in the Query Relay response. Search the event trace for 00.00.1F which is the Scene to turn On Relay 5. Then look at the Query Relay response (example above) and see that only Relay 1 ever shows as On.

It looks like the Scene which is turning on Relay 5 does not actually turn On the Relay. There are a number of places where this Scene is used but the Relay never actually turns On. The Red line marks the ISY Status of Relay 5 as On but the Query done immediately after shows the Scene did not work as Relay 5 is Off from the Query results. Same thing happens in other areas in the trace. Fri 03/14/2014 02:44:42 PM : [iNST-TX-I1 ] 02 62 00 00 1F CF 11 00 Fri 03/14/2014 02:44:42 PM : [iNST-ACK ] 02 62 00.00.1F CF 11 00 06 LTONRR (00) Fri 03/14/2014 02:44:42 PM : [ 23 8D 7C 5] ST 255 Fri 03/14/2014 02:44:42 PM : [iNST-TX-I1 ] 02 62 23 8D 7C 0F 4F 02 Fri 03/14/2014 02:44:42 PM : [iNST-ACK ] 02 62 23.8D.7C 0F 4F 02 06 IOCTL (QUERY) Fri 03/14/2014 02:44:43 PM : [iNST-SRX ] 02 50 23.8D.7C 24.1B.FE 2B 4F 01 IOCTL (01) Fri 03/14/2014 02:44:43 PM : [std-Direct Ack] 23.8D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 03/14/2014 02:44:43 PM : [iNST-TX-I1 ] 02 62 23 8D 7C 0F 49 00 Fri 03/14/2014 02:44:43 PM : [iNST-ACK ] 02 62 23.8D.7C 0F 49 00 06 RINPUT (00) Fri 03/14/2014 02:44:44 PM : [iNST-SRX ] 02 50 23.8D.7C 24.1B.FE 2B 49 30 RINPUT (30) Fri 03/14/2014 02:44:44 PM : [std-Direct Ack] 23.8D.7C-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 03/14/2014 02:44:44 PM : [ 23 8D 7C 5] ST 0

Here is what my Help | About shows for my Zigbee ISY The Icon(s) were deleted when the Java cache was cleared. Need to reestablish it/them by invoking the appropriate URL in the 4.1.2 announcement.

If running 3.3.10 I think you have to send the UUID of the 99i to sales@....... and reference this topic. I don't think they list modules for the 99i since it was discontinued about a year ago.

There are various topics on Scene Status. Here is one, there are others .... viewtopic.php?f=51&t=11201 The most important fact is that Insteon has no concept of Scene Status and never has. Ask 6 people what Scene Status should be and you'll get more than 6 ideas.

Battery powered devices have to be added using New INSTEON Device. Battery devices go to sleep very quickly to save battery life so Start Linking does not work. Manually put the Door Sensor into linking mode using its Set button. Within 4 minutes use New INSTEON Device. Be sure the Door Sensor is near enough the PLM as it is the only RF device available. xx.xx.xx is the device address. The Door Sensor is probably fine since battery devices cannot use Start Linking.

The base Program would look something like this ... If Control 'MotionSensor2-Sensor' is switched On Or Control 'Motion Sensor I2VS v22-Sensor' is switched On And ( From 10:00:00PM To Sunrise (next day) ) Then Set 'LampLinc DB' On Else - No Actions - (To add one, press 'Action')

Scenes (links) have been used all along. When a device is added to the ISY a Scene (link) is created between the device and the PLM. This is necessary for the PLM to be aware of a manual device button/paddle press. Scenes are useful when multiple devices are being controlled by the same event. Also when one device is controlling another. Press a KeypadLinc button that turns On/Off one or more devices. It is better to do this with a Scene where the KeypadLinc button is the Controller and the other device(s) is a responder. This happens faster than triggering a Program to control a device directly.

A Scene is made up of link records. The link records for the Scene would be in all the devices that are part of the Scene.

Run File | Restore Modem (PLM). DO NOT RUN Delete Modem (PLM). The Restore Modem (PLM) will rebuild the PLM link database. After running the Restore display the PLM link table to confirm it has been restored.

The motion sensor sensitivity can be reduced by installing Jumper 1. If the cat is walking on the floor the motion sensor can be pointed up a little. Jumper 1 cannot be changed with programming.

The Query Input response is 0x30. It is a bit map just like the Query Relay response. Inputs 5&6 On (wired On), all other Inputs Off. When that value is falsely evaluated as Relay Status, Relays 5&6 are marked On, all other Relays Off. The Relays were marked accordingly to the Input response 0x30. Relays 2&4 were On (and are still On) and are now incorrectly marked Off. Relays 5&6 are marked On because Input 5&6 are wired On. The Query Relay taken just before the Query Input shows the correct Relay Status, Relays 2&4 On, all others Off. Why this happens is unknown by me. Why there is a 4 second delay in either the EZIO8SA sending or the PLM passing the Relay response message on to the ISY is unknown. Perhaps the EZIO8SA was handling changes to the Inputs, perhaps the ISY was busy doing something that prevented it from reading the PLM serial port for 4 seconds. Since the delay happened twice back to back it was something that happened over several seconds to affect two Relay Query responses.