LeeG

Has anyone tried the up/down arrows on the I/O Linc Relay Set Options Momentary hold time input field? It displays an initial value of “0†which does not change when using the up/down arrows for the input field. If I type a new value in the input field, say 30, the up/down arrows do change the value. It almost looks like a Java problem but I installed the latest 1.6.0.32_b05 build with the same results. I did clear the Java cache after installing the new Java build. The new Momentary hold time value is saved with the Save button. However, the next time Set Options is invoked the new value is not displayed. A “0†is displayed. This was discussed by another user on an earlier image so this is not 3.2.5 related. Update: the Momentary hold time value not being displayed correctly was resolved by doing a Diagnostics | Query Insteon Engine. This same solution has worked on other devices where configuration data was not being handled correctly. Thanks Michel.

Anytime an If Status is used and the Program has a Wait or Repeat a change in Statue (from On to Off for example) can cause a reevaluation and execution of a new copy of the Program. When the Scene is turned Off and the Status of the device changes from On to Off the Status has changed causing the Program to be triggered. The Then or Else runs depending on whether the If is True or False at the time. As soon as the Set Scene Off is invoked the Program terminates. I suspect the Program is gone before the ISY posts the device Off Status which invokes the Program again. Take a look at the UDI Wiki. It has a good explanation of Wait/Repeat and how they can affect the execution of a Program. A Fast On or Fast Off requires a quick double tap of the paddle/button. The Event Viewer will display the command received with an annotation at the end of the command which indicate On/Off/Fast On/Fast Off. The Event Viewer will show if a Fast xxx is actually being generated by the device. Note that the Program posted will run the Then clause when the light turns On and will not start a Wait.

Any time a Program encounters a Wait or Repeat the If can be reevaluated. This can occur anytime during the Wait period. Only one copy of the Program executes. If the reevaluation causes the Program to be invoked again the current copy is terminated. It is important to know what the If looks like. If Status and If State variable cause a reevaluation anytime the Status or State variable change values (when a Wait or Repeat is encountered). If no Wait or Repeat the IF condition can change with no affect on Program execution. "What happens if, 40 seconds into the wait, the motion sensor is triggered again?" The Program will not be in the Wait more than a few seconds. When the Motion Sensor sends the Off the Program If Status is reevaluated, the condition is now False so the Else runs which does not have any logic so the Program ends. In this case an If Control On is more appropriate. The On causes the Program to trigger and the Then clause runs because it is an On command. The Off command has no affect on an If Control On. Should another On be received before the Wait completes the current Program is terminated and a new copy runs with a new Wait interval. The UDI Wiki has a very good explanation of Wait/Repeat and how they can affect Program execution.

wswartz The Admin Console On button issues an On command to the defined Local On Level, the Program issues a On command to 100% On. The suggestion by Nuttycomputer to change the Set On in the Program to Set 20% is the answer. The first Program is changing the Local On Level and Local Ramp Rate as evidenced by the paddle turning on to 20%.

blueman2 The 2475DA1 carries a different cat/subcat value (the number inside the [01.32]. It is not listed on the sales pages yet. When Smarthome lists it as an available item it will have some differentiating feature.

The symptoms are consistent with a communications problem. Move the ApplianceLinc to the PLM plug point and try again. If it fails there run an Event Trace with Level 3 selected and post trace.

I don't think much can be done with active Insteon powerline traffic. Run a few Show PLM Links Table to see if consistent results can be obtained.

Which means it was not written or has not been displayed because of the Insteon traffic. If the link record is not there a state change message from the SwitchLinc will not be processed which is consistent with the symptom. If you have a spare FilterLinc temporarily putting the PLM on the filtered side of a FilterLinc may isolate the PLM enough to process the PLM link database. With the arrival of the Dual Band PLM this has not worked as well because of the RF capability of the PLM. Putting a 2413 PLM inside a metal cabinet should block the RF.

A purchase before March is probably not I2CS. However, the only reason March is being used is Smarthome posted about devices purchased after March 2012. That is not an absolute about earlier purchases. 3.2.5 (RC) was just released so that is what should be installed. It could become the next Official release (RC). If an I2CS device was installed pre 3.2.x it has to be Delete and added under 3.2.5. There are also some issues (non I2CS) with the value the ISY is maintaining for device Engine (is it I1, I2, I2cs). Some cases were solved by issuing the new Diagnostic | Query Insteon Engine function without Deleting and adding the device. A few cases required deleting and adding the device. The symptoms have to do with setting device configuration, Local On Level, KeypadLinc button relationships, etc.

There is a forum Category dedicated to Variables. The first few topics cover Variables in detail. If a Program is not being triggered with a Variable the variable is an Integer rather than a State variable. Both types are identical except State variables trigger Programs, Integer variables do not. This is all covered in the initial topics under the Variables forum category.

The specific number is meaningless because it is not accurate. An accurate number should be under 992. Was the A2 01 1B.C5.E4 xx xx xx found in the list of PLM records?

First, 3.2.5 (RC) is now out which you should move to. Whenever Current State column is blank nothing should be done except to exit the Admin Console and re-invoke. It means the data is not being pushed from the ISY to the Admin Console which means many things may not work right. That is generally caused by AV blocking the ISY push of data.

With that much variation in PLM record count the PLM cannot be restored successfully. All Insteon traffic has to be eliminated while doing a Restore Modem (PLM). The link record in the PLM that is required for the SwitchLinc to show a state change is A2 01 1B.C5.E4 xx xx xx Do a Show PLM Links Table. Look through the displayed link records for the above. I would expect it not to be there.

The new LampLincs are I2CS devices which require 3.2.4. Update to 3.2.4. Clear the Java cache and use the URL for the 3.2.4 Admin Console. After update click Help | About to verify both the Firmware line and UI line indicated 3.2.4. Once confirmed the ISY and Admin Console are on 3.2.4, Delete the LampLinc and add it back under 3.2.4. If the LampLinc was added to any Scenes they must be recreated under 3.2.4.

Do a Show PLM Links Table followed by a Count. Do it at least three times to check the Count. Any Insteon message that reaches the PLM during the Show can result is missing or duplicate link records being displayed. Trust the count only if the same count received multiple times. My concern is the total link records have exceeded the PLM capacity. Have you verified that other devices do show state changes in the Admin Console?

Nothing wrong with that. Lots of folks like the same idea.

The old dryer plug is a passive coupler that can pass the Insteon frequency as well as X10. The fact that the passive coupler fixed it suggests the Access Points are not plugged into outlets on opposite 120v legs or are not within RF range of each other. Suggest running the 4 tap Set button test on the Access Points again in both direction.

The LampLinc must be added to the ISY and the Scene created under 3.2.4.

The new LampLincs are I2CS devices which require ISY 3.2.4. Upgrade to 3.2.4. Be sure to clear the Java cache and use the URL for accessing the 3.2.4 Admin Console. After update go to Help | About and confirm the Firmware and UI lines both indicate 3.2.4. Then Delete the LampLinc and add it back under 3.2.4.

The event trace looks correct. Do a Show Device Links Table against the SwitchLinc and confirm there are two link records that look like this … 0FF8 A2001970C5FF1F01 0FF0 E2011970C5FF1F01 0FE8 0000000000000000 Assuming this is what is displayed the SwitchLinc link records were created successfully. If the SwitchLinc is not showing a state change to the Admin Console (assuming other devices do show state change) when the paddle is pressed the issue is in the PLM link database. The PLM link records were created according to the trace. The last thing to try is to Factory reset the PLM and do a Restore Modem (PLM).

Delete the SwitchLinc from the ISY. Factory reset the SwitchLinc. Verify Help | About is showing 3.2.4 for Firmware and UI. Invoke Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Using New INSTEON Device enter the Insteon address and Name, leaving Device Type set to Auto Discover. Post the event trace from the New INSTEON Device add. Note that if another product like Indigo is creating links in the ISY PLM the results are unpredictable. Indigo could easily wipe out links the ISY has created which would result in device state changes not being registered.

The ISY is changing the displayed SwitchLinc status because it is hearing the Motion Sensor message. It is not hearing the SwitchLinc messages. Let me make the suggestion once more. Put the SwitchLinc on an appliance cord and plug the appliance cord into the PLM plug point. That eliminates communications questions. If it does not work there something did not work adding the SwitchLinc to the ISY under 3.2.4. If it works at the PLM plug point there is a comm. Problem at the SwitchLinc install point.

Those Scenes look exactly right. With each switch/button added as a Controller the ISY cross-links them automatically so that each switch/button controls the load and the status LEDs stay in sync.

htjunkie Your understanding is correct. If Control is looking for a specific command from the device itself from a button/paddle press. The Program loop you mentioned in the first post was likely a mismatch in If to Then command. That is, an On (X10 or Insteon Status) was received and an Off was issued or vice versa.

The ISY manages link records by location in individual devices. That is, the ISY knows what link record is at each link record address in the individual device. This information allows the Show ISY Links Table for a device to display the link records as they should appear in the device. It also supports the Compare function for individual devices. Link Management in the PLM is very different. The ISY does not manage link records in the PLM by address. The PLM is given a command to add or delete a link record. No link record address is provided. The PLM has logic to locate the link record for a delete and find an available slot for an add. The ISY has no information about where any given link record is located so has no information to produce a display for a Show ISY PLM Links Table. The Show PLM Links Table reads the PLM link database sequentially. There is no Compare function for the PLM for the same reason. The ISY has no information as to what link record should be where for a PLM.