LeeG

What is the ISY firmware level? What is the Java level? When the Scene name is selected the responders with their sliders for On Level and Ramp Rate are displayed, yes no?. The sliders do or do not move? If the slider moves is there a progress bar? Are there green Icons to the left of any of the nodes indicating writes pending?

How was the Scene created? Are the Scenes listed at the bottom of the My Lighting tree?

CTBigman Each Controller of a Scene has a unique set of Responder On Level and Ramp Rate values. Click on the Scene name or one of the Controllers listed below the Scene name. All the Responders for that Controller are listed. Set the desired values for each Responder based on the Controller selected. Lee

See your post under 3.1.14.

The Admin Console is not designed to be a long running task. I think something expires in the connection which means the ISY is not able to push data out to the Admin Console. Anytime the Current State information is missing for all the devices restart the Admin Console. There are situations where AV like Avast will block all data from the ISY but this would be a solid situation, not what you are seeing.

Use the forum Search facility and look for avast. There are a number of posts with various work arounds which apparently do not work with the latest AVAST update. One of the posts indicates there is a forum for avast. Perhaps that forum has an answer. One user just went to Norton to avoid the problem.

Normally when the Current State column is blank for all devices the ISY is being blocked from pushing data out to the Admin Console by router/AV. What AV is being used? AVAST has been a common problem of late. Also when changing ISY images be sure to clear the Java cache. The Help | About display now shows both the ISY firmware level (Firmware) and the Admin Console level (UI). Be sure both of these indicate 3.1.13. Did not understand the comment about the ISY's web site showing Current State information. Please elaborate.

"How do you create variables?" Under the Programs | Variables tab select type of Variable, Integer or State, enter Name Init - numeric value - 0 is valid Value - numeric value - 0 is valid click Add Integer and State variables contain numeric values. The word False would not be valid. State variables will trigger Programs when the value changes. Integer variables do not trigger Programs when the value changes. This link will take you to the discussion of Variables - viewforum.php?f=68

Sorry for the untested advice. Did as I suggested and get the same error you do, invalid /. Looks like a bug.

Do not change the Dusk/Dawn suffix. Change only the prefix.

matapan Is the objective to determine if state device has been turned Off and not been turned back On during that 1 minute before turning Off the target device? Or simply wait 1 minute before turning Off the target device if the state device is Off after 1 minute? Lee

apostolakisl The IO Linc Relay is like an ApplianceLinc and OutletLinc, they do not report locally initiated state changes. I agree about the usefulness of the IO Linc Relay Status. It does not say anything about the state of the door nor dictate commands usage based on whether the Relay Status is On or Off. Some folks like to see the correct Status in the Admin Console and on mobile devices but it really does not mean anything. Lee

apostolakisl Of course you are right about the Query not being executed. However, it is useful if it had been because the IO Linc Relay Momentary mode will turn the Relay off in a few seconds. The Io Linc Relay is a Responder Only so it does not notify the PLM of the On to Off state change resulting from Momentary mode. matapan The standard solution to the reevaluation and no Query is to put the current Then statements in a second Program, changing the current Program Then to a Run second Program. Lee

When the Program Then clause turns the I/O Linc Relay On the door moves changing the Status of the I/O Linc Sensor. That change of Status causes the Program to be reevaluated at the Wait. Now the If is False so the Else clause is run.

The False Status normally indicates it ran the Else path after running the Then path. Can you post the Program.

There is a Tools | Diagnostics | Show PLM Links Table that displays all the link records in the PLM. Once complete there is a Count button that gives a total of link records read. If that number would drop then something has happened. The only problem though is that inbound Insteon traffic to the PLM during the Show execution can give false high and low counts. Really need to run the Show followed by Count a few times and see if the number repeats.

Glad it is working. The loss of link records in the PLM could indicate the PLM is near failure. I've seen a PLM lose records and run fine after the restore but it is a concern.

Same thing happens with multiple motion sensors. Leave the RF devices alone or if you have an ISY Pro use the top right most Icon to queue all RF updates. Either way the ISY will not write to the RF devices and will queue the activity. Once the main Restore processing is complete put each TriggerLinc into linking mode individually and write the updates to the devices one at a time.

The events that are being registered in the event viewer are from Insteon Direct commands which do not use link records. With so many devices not reporting status to the ISY PLM I think the PLM has lost most of its link records rather than being a device issue. I suggest doing a File | Restore Modem (PLM) to rewrite the PLM link database. Best to eliminate any other Insteon traffic while the Restore Modem (PLM) is running.

I reread the post about a second device not presenting events either. This does raise the possibility that there could be a phase coupling problem. It would be good to know whether other devices on the opposite 120v phase to the ISY PLM show events in the event viewer. Although I don't believe a v35 SwitchLinc would not show any events, v35 SwitchLincs are an issue with general reliability of Scenes. I suggest replacing any v35 SwitchLinc.

That SwitchLinc has lost its link to the ISY PLM. This link is established when the SwitchLinc was originally added to the ISY. The device can be controlled from the Admin Console because Insteon Direct commands are used which do not use link records. Suggest doing a Restore Device against the SwitchLinc by right clicking on the device node In the My Lighting tree and select Restore Device . If that does not resolve the problem then Delete the device from the ISY and add it back. This should restore the required link records.

swbrains Look at Programs | Summary under the Activity column, check for Not Saved. Also look for Last Run Time and Status. Some devices can be difficult to generate a Fast On button/paddle/toggle press, particularly a ToggleLinc. Run Tools | Diagnostics | Event Viewer with Level: Device communications events selected and do a double tap at switch. You are looking for an event entry that indicates LTON-F which is Fast On. Wed 12/14/2011 05:32:04 PM : [iNST-SRX ] 02 50 15.9A.F9 19.70.15 41 12 06 LTON-F (06) Lee

Correct. The Program you posted is using Insteon Direct commands to control the InLineLinc. Also the buttons at the bottom of an individual device display under the Admin Console use Insteon Direct commands. Using an ISY Scene name in a Program or pressing a button/paddle on a device uses Insteon Scene (Group) commands. It is these Scene (Group) commands that are not working.

This will be an update to the ISY firmware. All images as they become available are posted under the Forum category Current Releases, Betas, and Bug Reports. The announcement for each new image includes information on fixes and enhancements as well as a link to the new image for download and install procedures. The ISY Help | Manually Upgrade My Lighting function loads the new image.

Harry That is a known problem with the newest Dual Band InLine Linc Relay. It will not respond to a Scene. The device firmware is expecting something new in the link record. The issue will be resolved in a future ISY image. Until then the work around using Direct commands is the solution. Lee